Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Release 0.5.0 #8419

Draft
wants to merge 8 commits into
base: main
Choose a base branch
from
Draft

Release 0.5.0 #8419

wants to merge 8 commits into from
+650 −87

Conversation

zanieb
Copy link
Member

@zanieb zanieb commented Oct 21, 2024 •
edited
Loading

@zanieb zanieb added the tracking A "meta" issue that tracks completion of a bigger task via a list of smaller scoped issues. label Oct 21, 2024
@zanieb zanieb added this to the v0.5.0 milestone Oct 21, 2024
This was referenced Oct 22, 2024
Open
Open
zanieb and others added 7 commits October 24, 2024 11:22
@zanieb
Use 3.13 in CI (#8014)
aa85aa0
@Aditya-PS-05 @zanieb
Improve interactions between color environment variables and CLI opti…
d67c802 
…ons (#8215)

closes #8173
@Czaki @konstin
@cthoyt @charliermarsh @zanieb
do not imply pre-release when != operator is used (#7974)
24f9d6f 
closes #6640

Could you suggest how I should test it?

(already tested locally)

---------

Co-authored-by: konstin <[email protected]>
Co-authored-by: Charles Tapley Hoyt <[email protected]>
Co-authored-by: Charlie Marsh <[email protected]>
@zanieb
Eliminate dependencies on directores and dirs-sys (#8048)
d9d55b7 
Migrate all directory related logic to `etcetera`, eliminated two
dependecies.
@zanieb
Treat the base Conda environment as a system environment (#7691)
248e9f7 
Closes #7124
Closes #7137
@edugzlez @charliermarsh @zanieb
Add support for .env and custom env files in uv run (#8263)
c00e6e6 
I have been reading discussion #1384 about .env and how to include it in
the `uv run` command.

I have always wanted to include this possibility in `uv`, so I was
interested in the latest changes. Following @charliermarsh's [advice
](#1384 (comment)) I
have tried to respect the philosophy that `uv run` uses the default
`.env` and this can be discarded or changed via terminal or environment
variables.

The behaviour is as follows:
- `uv run file.py` executes file.py using the `.env` (if it exists).
- `uv run --env-file .env.development file.py` uses the
`.env.development` file to load the variables and then runs file.py. In
this case the program fails if the file does not exist.
- `uv run --no-env-file file.py` skips reading the `.env` file.

Equivalently, I have included the `UV_ENV_FILE` and `UV_NO_ENV_FILE`
environment variables.

I haven't got into including automated tests, I would need help with
this.

I have tried the above commands, with a python script that prints
environment variables.

---------

Co-authored-by: Charlie Marsh <[email protected]>
@charliermarsh @zanieb
Accept multiple .env files in --env-file (#8463)
703ad66 
Closes #8457.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
tracking A "meta" issue that tracks completion of a bigger task via a list of smaller scoped issues.
Projects
None yet
Milestone
v0.5.0
Development

Successfully merging this pull request may close these issues.
5 participants
@zanieb @charliermarsh @Aditya-PS-05 @Czaki @edugzlez