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

Add support for new slice objects in python3.14a1 and other small fixes #43

Merged
merged 6 commits into from
Oct 18, 2024

Conversation

keszybz
Copy link
Owner

@keszybz keszybz commented Oct 18, 2024

No description provided.

The "content hash" is for the _source_ file, so it doesn't change if we
rewrite the pyc file. The TODO entry was completely bogus.

But as a follow-up, it'd be nice if we could notice the cases where we're
working on a file that doesn't actually work for the size and/or mtime of the
pyc file. This could help to diagnose the cases where the py file mtime was
changed after the pyc file was written.
This codepath didn't get exercised before, so the error message was
not very readable. It's much easier if we know that it's ':' that is not
implemented.
Added in c6127af8685c2a9b416207e46089cee79d028b85 for Python 3.14.

Closes #42.
The files are taken from python3.14-3.14.0~a1-1.fc42.x86_64 scratch build and
.pyc.fixed were generated with freshly built add-det. As previously, those are
under license Python-2.0.1.

Add just a handful of files, incl. a few with the new slice serialization.
We end up rewriting the pyc files as serialization changes, increasing the
size of the repo. We don't really gain much from having a full hundred of
files writte by the same Python version.
@keszybz keszybz merged commit bd33eed into main Oct 18, 2024
8 checks passed
@keszybz keszybz deleted the python-3.14 branch October 18, 2024 14:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant