python-trio / python-trio/trio
Please switch to v1.0 and start using semantic version numbers
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 7.3k
- Forks
- 431
- Avg merge
- 2d 17h
- Merged PRs (30d)
- 6
Description
The last change to Trio (dropping MultiError) caused some compatibility mayhem, most recently here.
I'd thus like to ask for a release tagged 1.0, followed by semantic version numbers. That will allow other packages that depend on Trio to use a dependency like ~1.0, thus telling pip-or-whatever that upgrading Trio from say 1.9 to 2.1 is not going to work.
IMHO Trio is sufficiently stable (and widely used) that zero-dot-anything version numbers are no longer a good idea.
Contributor guide
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
Review the requested 1.0 release and the compatibility concern described in moat-mqtt#18. Done means the maintainers agree on the versioning policy, publish a 1.0 tag, and use semantic version numbers for later releases.
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
- Mostly clear
- Newbie friendliness
- 25/100