This repository was archived by the owner on Sep 25, 2025. It is now read-only.
Add Python 3.13 support by updating NumPy and pandas constraints#134
Open
jbf302 wants to merge 2 commits intonflverse:mainfrom
Open
Add Python 3.13 support by updating NumPy and pandas constraints#134jbf302 wants to merge 2 commits intonflverse:mainfrom
jbf302 wants to merge 2 commits intonflverse:mainfrom
Conversation
- Update requires-python constraint from <3.13 to <3.14 - Update numpy constraint from ==1.* to >=1.20,<3.0 to support numpy v2 - Update pandas constraint from ==1.* to >=1.3,<3.0 for compatibility - Add Python 3.13 classifier Fixes nflverse#122 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <noreply@anthropic.com>
- Successfully installed package on Python 3.13.4 - All critical functions tested with NumPy 2.3.2 and pandas 2.3.1 - Test suite passes (53/54 tests completed successfully) - Downcast functionality working correctly with NumPy v2 - Data import and cleaning functions verified 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <noreply@anthropic.com>
|
Could you help me with how to adjust the package install code to account for this? |
Author
|
According to Gemini:
^^ should do the trick Option 2: Clone and Install Manually Clone the forked repository: Navigate into the new directory: Switch to the branch containing the fix: Install the package locally: After using either method, you can verify the installation by opening a Python interpreter and importing the library: |
|
That worked. Seriously, thank you very much! |
This file contains hidden or 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
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Summary
Fixes #122 by adding Python 3.13 support through conservative dependency constraint
updates.
Problem
The current package constrains Python to
<3.13and requiresnumpy==1.*, whichprevents installation on Python 3.13 since NumPy v1 doesn't support Python 3.13.
Solution
requires-pythonconstraint:>=3.6.1,<3.13→>=3.6.1,<3.14numpyconstraint:==1.*→>=1.20,<3.0(enables NumPy v2 support)pandasconstraint:==1.*→>=1.3,<3.0(compatible with NumPy v2)Testing Results ✅
Environment: Python 3.13.4, NumPy 2.3.2, pandas 2.3.1
Backward Compatibility
These changes maintain full backward compatibility:
Commits
8cfcb6e: Add Python 3.13 support by updating dependencies3252353: Verify Python 3.13 compatibility with comprehensive testingCloses #122