-
-
Notifications
You must be signed in to change notification settings - Fork 25
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
Rename package #54
Comments
It has always been I suggest sticking to the current |
Not necessarily. We can add an "alias" package. |
Ok! I'm not sure which is better:
Option B is better for users I guess. Sinces I'm looking at this more from the dev standpoint I tend to favour option A. If there is a conda policy to keep names congruent with PyPI, perhaps to avoid package conflicts when using |
@msarahan are there any fancy tricks with multiple outputs that we can use here to create both |
sure, just make a metapackage that depends on the "real" one. We do that in our boost recipe to adapt to conda-forge's names: https://github.com/AnacondaRecipes/boost-feedstock/blob/master/recipe/meta.yaml#L174 |
Awesome! Thanks!! |
Looks like the package was renamed to
tables
in PyPI and this is creating some confusion for some users. Should we rename it here too? See https://pypi.org/project/tables/#filesThe text was updated successfully, but these errors were encountered: