releasing the Weave package name on PyPI
Hi all, We got approached about releasing the "weave" name on PyPI, by a company that has developed a new open source project with the Weave name. They're attached to that name, and want to explore what can be done to name it as such and have it installable from PyPI as `weave`. After a chat with them on how to make this a win-win situation, we came to the conclusion that that would be possible - by donating to SciPy, so it's able to execute more projects like the two ~$10,000 ones that we have done in the past 1.5 years. Those were (1) Meson build support and (2) scipy.interpolate cleanup, both quite impactful. After discussion in the core team, the outcome was that this would be very welcome, and we'd like to go ahead with releasing the `weave` name. For some context, we deprecated `scipy.weave` a very long time ago, and then split it off as a separate `weave` package 9 years ago. There are three releases at https://pypi.org/project/weave/#history, matching the SciPy 0.15.0 - 0.17.0 releases. We haven't made significant changes in 8 years (just a couple of smaller tweaks) - and `scipy.weave` was already in really bad shape then. It also never made the transition to Python 3, and Python 2.7 is quite far beyond end-of-life now. So it really will be at most a few handfuls of users I believe. There's still ~10 downloads/day ( https://pypistats.org/packages/weave), but those are highly likely to be folks trying to install `weaveio` or something else like that. Indication: most downloads are Python 3, and `weave` doesn't support that. Unless there is a blocking issue that we overlooked during this discussion, we'd like to go ahead with this plan by December 1st. The plan for that is: - Rename to `scipy-weave`, updating https://github.com/scipy/weave/ for that change (README, metadata). - Create a new `scipy-weave` package on PyPI - Migrate old releases on PyPI - Do a new release (0.17.1, no code changes) - Transfer control of the `weave` package on PyPI; ensuring there's at least a 10 day window in which no breaking changes are made to the `weave` package yet, in case there are still any users who see this announcement and would like to switch over. If there's an issue here or if something seems missing from the above plan, please speak up. Cheers, Ralf
On 23/11/22 19:41, Ralf Gommers wrote:
The plan for that is:
Sounds like a win-win, congrats. One nit: perhaps the new package could start with a higher version number (0.20 for instance, or a CalVer scheme) so that there would be no conflict with old packages. Matti
Versions numbers have an explicit epoch that can be helpful: https://peps.python.org/pep-0440/#version-epochs -- M On Wed, 23 Nov 2022 at 19:33, Matti Picus <matti.picus@gmail.com> wrote:
On 23/11/22 19:41, Ralf Gommers wrote:
The plan for that is:
Sounds like a win-win, congrats. One nit: perhaps the new package could start with a higher version number (0.20 for instance, or a CalVer scheme) so that there would be no conflict with old packages.
Matti
_______________________________________________ SciPy-Dev mailing list -- scipy-dev@python.org To unsubscribe send an email to scipy-dev-leave@python.org https://mail.python.org/mailman3/lists/scipy-dev.python.org/ Member address: bussonniermatthias@gmail.com
Thanks for the feedback Matti and Matthias. I'll see if that version number idea is feasible. The donation mentioned in my initial email is now publicly visible in our finances: https://opencollective.com/scipy/transactions. A big thank you to Weights & Biases for supporting SciPy with a $10,000 donation. I'm sure we can find a way to put this to good use! Cheers, Ralf On Wed, Nov 23, 2022 at 6:41 PM Ralf Gommers <ralf.gommers@gmail.com> wrote:
Hi all,
We got approached about releasing the "weave" name on PyPI, by a company that has developed a new open source project with the Weave name. They're attached to that name, and want to explore what can be done to name it as such and have it installable from PyPI as `weave`. After a chat with them on how to make this a win-win situation, we came to the conclusion that that would be possible - by donating to SciPy, so it's able to execute more projects like the two ~$10,000 ones that we have done in the past 1.5 years. Those were (1) Meson build support and (2) scipy.interpolate cleanup, both quite impactful. After discussion in the core team, the outcome was that this would be very welcome, and we'd like to go ahead with releasing the `weave` name.
For some context, we deprecated `scipy.weave` a very long time ago, and then split it off as a separate `weave` package 9 years ago. There are three releases at https://pypi.org/project/weave/#history, matching the SciPy 0.15.0 - 0.17.0 releases. We haven't made significant changes in 8 years (just a couple of smaller tweaks) - and `scipy.weave` was already in really bad shape then. It also never made the transition to Python 3, and Python 2.7 is quite far beyond end-of-life now. So it really will be at most a few handfuls of users I believe. There's still ~10 downloads/day ( https://pypistats.org/packages/weave), but those are highly likely to be folks trying to install `weaveio` or something else like that. Indication: most downloads are Python 3, and `weave` doesn't support that.
Unless there is a blocking issue that we overlooked during this discussion, we'd like to go ahead with this plan by December 1st. The plan for that is:
- Rename to `scipy-weave`, updating https://github.com/scipy/weave/ for that change (README, metadata). - Create a new `scipy-weave` package on PyPI - Migrate old releases on PyPI - Do a new release (0.17.1, no code changes) - Transfer control of the `weave` package on PyPI; ensuring there's at least a 10 day window in which no breaking changes are made to the `weave` package yet, in case there are still any users who see this announcement and would like to switch over.
If there's an issue here or if something seems missing from the above plan, please speak up.
Cheers, Ralf
https://pypi.org/project/scipy-weave/ is now up. I transferred all the old releases, and for bonus points I cut two new releases: - 0.18.0 with Python 2.6-2.7 support (equivalent to 0.17.0, with some tweaks to README) - 0.19.0 with Python 3.4-3.9 support (new, there was an old PR for that that was still in pretty good shape) `pip install scipy-weave` will now do the right thing for Python 2 and Python 3. Finally, there are also wheels now, in order to be a good PyPI citizen. Cheers, Ralf On Tue, Nov 29, 2022 at 10:35 PM Ralf Gommers <ralf.gommers@gmail.com> wrote:
Thanks for the feedback Matti and Matthias. I'll see if that version number idea is feasible.
The donation mentioned in my initial email is now publicly visible in our finances: https://opencollective.com/scipy/transactions. A big thank you to Weights & Biases for supporting SciPy with a $10,000 donation. I'm sure we can find a way to put this to good use!
Cheers, Ralf
On Wed, Nov 23, 2022 at 6:41 PM Ralf Gommers <ralf.gommers@gmail.com> wrote:
Hi all,
We got approached about releasing the "weave" name on PyPI, by a company that has developed a new open source project with the Weave name. They're attached to that name, and want to explore what can be done to name it as such and have it installable from PyPI as `weave`. After a chat with them on how to make this a win-win situation, we came to the conclusion that that would be possible - by donating to SciPy, so it's able to execute more projects like the two ~$10,000 ones that we have done in the past 1.5 years. Those were (1) Meson build support and (2) scipy.interpolate cleanup, both quite impactful. After discussion in the core team, the outcome was that this would be very welcome, and we'd like to go ahead with releasing the `weave` name.
For some context, we deprecated `scipy.weave` a very long time ago, and then split it off as a separate `weave` package 9 years ago. There are three releases at https://pypi.org/project/weave/#history, matching the SciPy 0.15.0 - 0.17.0 releases. We haven't made significant changes in 8 years (just a couple of smaller tweaks) - and `scipy.weave` was already in really bad shape then. It also never made the transition to Python 3, and Python 2.7 is quite far beyond end-of-life now. So it really will be at most a few handfuls of users I believe. There's still ~10 downloads/day ( https://pypistats.org/packages/weave), but those are highly likely to be folks trying to install `weaveio` or something else like that. Indication: most downloads are Python 3, and `weave` doesn't support that.
Unless there is a blocking issue that we overlooked during this discussion, we'd like to go ahead with this plan by December 1st. The plan for that is:
- Rename to `scipy-weave`, updating https://github.com/scipy/weave/ for that change (README, metadata). - Create a new `scipy-weave` package on PyPI - Migrate old releases on PyPI - Do a new release (0.17.1, no code changes) - Transfer control of the `weave` package on PyPI; ensuring there's at least a 10 day window in which no breaking changes are made to the `weave` package yet, in case there are still any users who see this announcement and would like to switch over.
If there's an issue here or if something seems missing from the above plan, please speak up.
Cheers, Ralf
participants (4)
-
einstein.edison＠gmail.com -
Matthias Bussonnier -
Matti Picus -
Ralf Gommers