Replies: 7 comments
-
How about |
Beta Was this translation helpful? Give feedback.
-
|
Beta Was this translation helpful? Give feedback.
-
There's also the related issue: Do we change the name on PyPI and the repository name, or just the readme and the documentation for better searchability? |
Beta Was this translation helpful? Give feedback.
-
Github has very nice support for repository renaming, with automatic forwarding of old links to the new name. I've moved repos around with zero issues. Not sure about the story from PyPI, though. |
Beta Was this translation helpful? Give feedback.
-
I would suggest renaming the PyPI package and repository name. It's a little annoying to migrate but better than having inconsistent names. For renaming xray -> xarray, I uploaded a final release of xray to PyPI with a new README pointing to the new package: https://pypi.org/project/xray/ I also made |
Beta Was this translation helpful? Give feedback.
-
I'm not sure I understand the impetus for renaming. I think It's nice when a foundational package can have short, descriptive name. I don't agree it's hard to search for. It's the second result on google for "python sparse" and third on duck-duck-go at the moment ( Plus the name collision with As an aside, |
Beta Was this translation helpful? Give feedback.
-
Copying here for visibility, I'm open to keeping the name the same, but there will need to be a version 2.0 with TACO-based rewrites, including some possible NaN-related breaks. See #460 (comment). |
Beta Was this translation helpful? Give feedback.
-
The name of this package is "Sparse" according to the docs and readme, that's basically not searchable or usable. I've been referring to it as "PyData Sparse", which is also a weird name for a package.
Can we reconsider this and come up with a name that's consistent and searchable?
Beta Was this translation helpful? Give feedback.
All reactions