Comments (8)
Thank you for your comments/suggestions @jaimergp and @ocefpaf. Just to be clear, I don't have a stake in this and I am not even involved with the development of scipy-weave
in the first place β I only had a personal use case for it and needed it to be on conda-forge
, so I created the recipe and maintained it. I am happy with any solution really, and I wouldn't feel particularly sorry for Weight & Biases if they cannot claim the weave
name on conda-forge
. I am just CC'ing @rgommers here, since he's maintaining scipy-weave
(and was involved in the negotiations around releasing the pypi name).
Just to give a quick summary, it seems there are two solutions:
- Archive
weave-feedstock
and go through the usual route for a newscipy-weave-feedstock
- Turn
weave-feedstock
into a multi-output recipe, creating bothscipy-weave
andweave
packages.
I'm happy with either solution, really, the first would be a bit easier for me, but slightly less convenient for existing users of weave
. Although I am not sure whether this is really much of an issue: the conda-forge weave
package is still Python2-only and the new scipy-weave
package is obviously now Python3-only.
from admin-requests.
Thanks @rgommers ! Ok, from my side then the preferred solution would be to close down the current weave-feedstock
(i.e., archive it), and I will go through the usual staged recipes process for scipy-weave
. If Weights&Biases will show up some day to get the "new weave" onto conda-forge, I'll let them figure that out with conda-forge admins. Thanks everyone for your help!
PS: I don't think there's anything I can do myself to close down/archive weave-feedstock
?
from admin-requests.
After having had a closer look at scipy/weave, I finally decided to not go ahead with submitting a new conda-forge package for scipy-weave
. As @rgommers explained earlier, the package is not developed any further, and it will not be installable on up-to-date systems very soon. As it is, it is not installable with Pythonβ₯3.11, and its test suite does not work with numpy β₯ 1.25. Again, as @rgommers said, nowadays there are better alternatives, so it is unlikely that someone will invest the time for a major update. If someone does, by all means get in touch with me if you want me to maintain a new conda-forge package π
I have opened a new issue to archive the feedstock (admin-requests/issues/776), and have also opened an issue on the weave-feedstock
to explain the situation to anyone stopping by (conda-forge/weave-feedstock#21).
from admin-requests.
Hey @mstimberg, thanks for the question!
There are two things to note here:
- Renaming feedstocks is not supported, so we'll have to archive the existing one after obtaining a new one through
staged-recipes
. - I think it would be tricky to change what
weave
means. Many problems come to mind like conflicting versioning, existing environments with "the other weave" all of a sudden getting something different, etc. The safest option would be to publish the unrelatedweave
with a different name in conda-forge.
Alternatively, you can keep the weave-feedstock
and change your recipe into a multi-output recipe where you publish scipy-weave
and weave
simply aliases to it. I think that's the less confusing story here. The Weight & Biases team can choose to publish their weave
with a different name if required (e.g. wandb-weave
or something).
from admin-requests.
Alternatively, you can keep the
weave-feedstock
and change your recipe into a multi-output recipe where you publishscipy-weave
andweave
simply aliases to it.
If we want to keep the namespace weave
for scipy-weave
, this is the best solution. If we don't care about that we must archive weave-feedstock
to prevent it from becoming the "new weave," which is a different package that clobbers this namespace.
Namespaces in conda-forge are first come first served. So, the name weave
, belongs to "scipy-weave" in my view, to archive it, or keep it with multiple outputs along side scipy-weave
. It is your choice @conda-forge/weave team.
from admin-requests.
Hey all. For context: the SciPy team decided to hand over the weave
name on PyPI to Weights & Biases (and W&B supported SciPy development with a significant donation, so it was a win-win situation). During that rename to scipy-weave
I took care of incorporating open PRs and making some maintenance updates for the package, most importantly Python 3.x support. That was a one-off effort, the package is effectively stagnant since there are much better alternatives now (Cython, Pythran, Numba - take your pick).
I'd be happy with whatever solution is easiest here, and also with repurposing the existing weave
name for W&B if they would like to have it at some point. The download count for the last weave release is very small, this won't affect many users and we've had no complaints about the rename on PyPI.
from admin-requests.
PS: I don't think there's anything I can do myself to close down/archive
weave-feedstock
?
You need to open a PR in admin-requests
(here) to request the archival. Create an issue in the feedstock too (maybe pointing to this discussion) to have a reference on why it was archived. Thanks!
from admin-requests.
Here's the PR to archive the weave-feedstock
: #778
from admin-requests.
Related Issues (20)
- Is it possible to overwrite a version tag? HOT 3
- Using GHA's `concurrency` syntax
- Deleting a single release on anaconda.org for https://anaconda.org/conda-forge/interpret HOT 9
- Orphaned Feedstock
- New feedstocks not finishing migration due to expired token HOT 3
- R-forge token reset not fully successful HOT 4
- Adding access control to CI providers and other resources
- Archive weave-feedstock HOT 1
- Broken `token_reset` pipeline HOT 2
- Update CI tokens for `jupyterlab-github-feedstock` HOT 3
- BUG mixup between .conda and .tar.bz2
- Package built with wrong package name
- Add option to require extras in bot `update-grayskull` HOT 2
- Trouble updating environment variables on Travis CI (token reset) HOT 3
- Scheduled runs are failing HOT 4
- Add ability to turn maintenance branches into tags (and back)
- YAML file instead of txt files in folders HOT 3
- Use organization level STAGING_BINSTAR_TOKEN in github actions
- Should mislabeled `noarch` packages be marked as `broken`? HOT 1
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
π Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. πππ
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google β€οΈ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from admin-requests.