You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
JUBE is a well established benchmarking environment at Juelich Supercomputing Centre, Germany. It is routinely used by multiple organizations within and outside of JSC. We want to publish this package under the name jube on pypi so that all our users have easier method to install the package. However, we are unable to do so with the following error:
dist/jube-0.0.1.tar.gz ... failed
Error uploading to repository: https://upload.pypi.org/legacy/ - Client error '400 The name 'jube' isn't allowed. See https://pypi.org/help/#project-name for more information.' for url 'https://upload.pypi.org/legacy/'
For more information check: https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/400
We are not sure what the error is with this package name, but we assume it might be because someone else has a package but with no releases. Hence, we are opening this issue.
Project to be claimed
jube
: https://pypi.org/project/jubeYour PyPI username
jbadwaik
: https://pypi.org/user/jbadwaikReasons for the request
JUBE is a well established benchmarking environment at Juelich Supercomputing Centre, Germany. It is routinely used by multiple organizations within and outside of JSC. We want to publish this package under the name
jube
onpypi
so that all our users have easier method to install the package. However, we are unable to do so with the following error:We are not sure what the error is with this package name, but we assume it might be because someone else has a package but with no releases. Hence, we are opening this issue.
Maintenance or replacement?
None
Source code repositories URLs
Project Source Code: https://github.com/FZJ-JSC/jube
Official Website: https://www.fz-juelich.de/en/ias/jsc/services/user-support/software-tools/jube
Contact and additional research
Code of Conduct
The text was updated successfully, but these errors were encountered: