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.

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

Expand scope of archive timestamping #1960

Merged
merged 1 commit into from
Feb 25, 2024
Merged

Expand scope of archive timestamping #1960

merged 1 commit into from
Feb 25, 2024

Conversation

charliermarsh
Copy link
Member

Summary

Instead of looking at either pyproject.toml or setup.py, we should just be conservative and take the most-recent timestamp out of pyproject.toml, setup.py, and setup.cfg. That will help prevent staleness issues like those described in #1913 (comment).

@charliermarsh charliermarsh added the bug Something isn't working label Feb 25, 2024
@charliermarsh charliermarsh marked this pull request as ready for review February 25, 2024 00:28
@charliermarsh charliermarsh enabled auto-merge (squash) February 25, 2024 00:28
@charliermarsh charliermarsh merged commit f449bd4 into main Feb 25, 2024
7 checks passed
@charliermarsh charliermarsh deleted the charlie/setup branch February 25, 2024 00:36
yasufumy pushed a commit to yasufumy/uv that referenced this pull request Feb 25, 2024
## Summary

Instead of looking at _either_ `pyproject.toml` or `setup.py`, we should
just be conservative and take the most-recent timestamp out of
`pyproject.toml`, `setup.py`, and `setup.cfg`. That will help prevent
staleness issues like those described in
astral-sh#1913 (comment).
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant