-
-
Notifications
You must be signed in to change notification settings - Fork 430
Un-archive weave feedstock
#1711
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
beckermr
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It appears that you'd like to point the same name to a completely different package? We do not allow that on conda-forge.
|
I think in this case it would be reasonable to follow PyPI and allow reuse of |
|
We have not allowed this on conda-forge (except for a few very special instances) since it has the potential to break things in unintuitive ways. |
|
I understand your concern. The pypi package name changed over 2 years ago, and the conda package has not had any updates in almost 6 years. I think we can draw a clean line separating the old vs. new packages by version number -- namely anything |
|
We've had some internal discussions and are moving ahead with a plan on this. More later. |
|
Thank you! |
|
Hi @beckermr , any updates? Is there anything I can do to help? |
|
xref conda-forge/cfep#64 |
|
Hey folks, just wanted to check in here. It seems like the CFEP above is good? Is there anything stopping us from unarchiving this? |
Hi, I'd like to un-archive the
weavefeedstock and make me the new maintainer.The old project called
weavewas archived per #778. The new project, now calledweaveon pypi, would like to start publishing on conda.