SpikeInterface / SpikeInterface/spikeinterface
Python deprecation cycle
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 847
- Forks
- 280
- Avg merge
- 3d 9h
- Merged PRs (30d)
- 29
Description
Python 3.8 is coming to its EOL in September.
https://devguide.python.org/versions/
However, I want to make you aware that numpy follows a different cycle and within that python 3.8 already got deprecated
https://numpy.org/neps/nep-0029-deprecation_policy.html#support-table
I wanted to discuss how to handle this. I think given the centrality for this package and neo we should probably follow numpy cycle instead of the longer python one.
What do you think?
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading the Python versions page and NumPy NEP-0029 support table linked in the issue. The issue names no files or tests and asks for a policy decision, so first establish which support cycle the project should follow; done requires an agreed decision and a documented project change.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- release
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100