Bug 2276614

Summary: [HEADS UP] python-netpyne buildrequires python3-future which won't work with Python 3.13 (Fedora 41+)
Product: [Fedora] Fedora Reporter: Karolina Surma <ksurma>
Component: python-netpyneAssignee: Ankur Sinha (FranciscoD) <sanjay.ankur>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: rawhideCC: neuro-sig, sanjay.ankur
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: python-netpyne-1.0.6-4.fc41 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2024-05-31 20:53:21 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 2250662    

Description Karolina Surma 2024-04-23 10:29:04 UTC
python-netpyne buildrequires python3-future which won't work with Python 3.13 (Fedora 41+).

future (python3-future) will not be buildable, installable and usable with Python 3.13, which removes lib2to3 and 2to3.
Python 3.13 will be the main Python in Fedora 41.

Please migrate python-netpyne to stop depending on python3-future.

The upstream issues:
https://github.com/suny-downstate-medical-center/netpyne/issues/773

Comment 1 Ankur Sinha (FranciscoD) 2024-04-23 10:42:29 UTC
Thanks, I've requested upstream to increase the priority of the upstream issue. If they don't work on it soon, we'll consider providing them a fix.

Comment 2 Fedora Update System 2024-05-31 20:51:11 UTC
FEDORA-2024-f55ea3ef7f (python-netpyne-1.0.6-4.fc41) has been submitted as an update to Fedora 41.
https://bodhi.fedoraproject.org/updates/FEDORA-2024-f55ea3ef7f

Comment 3 Fedora Update System 2024-05-31 20:53:21 UTC
FEDORA-2024-f55ea3ef7f (python-netpyne-1.0.6-4.fc41) has been pushed to the Fedora 41 stable repository.
If problem still persists, please make note of it in this bug report.