-
-
Notifications
You must be signed in to change notification settings - Fork 13.9k
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
python312Packages.nose: fix build #325968
Merged
+586
−57
Merged
Changes from all commits
Commits
Show all changes
17 commits
Select commit
Hold shift + click to select a range
749f7b3
python312Packages.nose: use pep517 builder
jchv f5a03f4
python312Packages.nose: fix build
jchv bf05070
hydrus: re-enable tests on 3.12
jchv 79e06f0
python312Packages.actdiag: re-enable tests
jchv 8f374ae
python312Packages.biopandas: re-enable tests
jchv 6f95909
python312Packages.blockdiag: re-enable tests
jchv 095a917
python312Packages.hkdf: re-enable tests
jchv 7328dcb
python312Packages.lockfile: re-enable tests
jchv 04332cd
python312Packages.nwdiag: re-enable tests
jchv d65482c
python312Packages.pprintpp: re-enable tests
jchv 9bdacf3
python312Packages.pydy: re-enable tests
jchv b43e2ad
python312Packages.pypass: re-enable tests
jchv 7df95dc
python312Packages.pytimeparse: re-enable tests
jchv cadf0bf
python312Packages.seqdiag: re-enable tests
jchv 6efa41d
python312Packages.sphinx-rtd-dark-mode: re-enable tests
jchv b259261
python312Packages.uvcclient: re-enable tests
jchv 599e471
python312Packages.xlwt: re-enable tests
jchv File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
576 changes: 576 additions & 0 deletions
576
pkgs/development/python-modules/nose/0001-nose-python-3.12-fixes.patch
Large diffs are not rendered by default.
Oops, something went wrong.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I guess when 3.12 leaves Nixpkgs we’ll have to do one of:
2to3
independently of the Python interpreter;nose
code and just vendor the results; ornose
?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah, that's roughly my thoughts. My order of preferences for future actions: (I assume most people are in a similar frame of mind, but just to jot it down in detail.)
Most preferred would be getting rid of nose dependencies upstream. It's unmaintained and most users don't use very much of its functionality, so a migration should be easy. For some packages, I think this will just be a matter of getting the version in Nixpkgs updated. For some simpler stuff,
nose2pytest
may be enough to generate a patch that we can use + submit upstream.Failing that, if Lack of attribution and licence information for code derived from CPython mdmintz/pynose#33 gets resolved then maybe we can consider the pynose licensing issue resolved and resume usage of pynose as a drop-in replacement, pending other's approval. I'm sure there will be some hesitance here though and I'm not going to argue if the thought is we'd rather play it safe.
Failing that, we can continue to try to patch Nose for Python 3.14+. In an earlier version of this PR I did indeed include a 2to3 patch file, but it's rather large, so I think putting it in Nixpkgs preemptively is undesirable.
And failing that, my thought is we can remove
nose
, disable tests on anything that continues to usenose
, and eventually remove packages that depend onnose
which are unmaintained.If you think it is a good idea, I can try to add more context to that comment for the future. Specifically, we could outline the options for handling 2to3.
Regarding packaging
2to3
independently: maybe even better would be packaging the fissix tool by amyreese, as it essentially seems to be an improved 2to3. (Coincidentally, it is also apparently used by thenose2pytest
tool.)There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ideally by 2028 we've fixed the ecosystem enough, that nose is not relevant anymore. I wouldn't worry too much about this today.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I didn’t realize that we kept Python releases for that many years. Agreed that it’s not worth thinking about in that case.