-
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Release new version to pypi #2
Comments
You can follow the discussion with pypi admins here : https://sourceforge.net/p/pypi/support-requests/507/ |
Let's wait some weeks before changing the name of the project. |
I quite liked the current package name. It's short and meaningful (like the implementation!) and has thousands (maybe more?) of users. Maybe worth mentioning on the sourceforge ticket - it's been actively developed and has a bunch of users. Changing the project name would be |
I agree with you but in my opinion it's very important to have a pypi access.... So let's wait and see what pypi admin say :-) |
The name is short, but it's far from semantic - it's impossible to know what it does just by looking at it. I'd be in favor of changing it. (might be moot anyway due to the pypi situation). |
If we can keep it, I will be in favor of that because What's the opinion of the others? |
Well I never knew any arabic but I found it cool that it was a nice short On 18 June 2015 at 20:34, Hadrien Mary notifications@github.com wrote:
|
you can see here that they haven’t closed a support request since may… |
Yeah I actually contacted the main maintenance dev who responded with apologetic expletives, with a promise to attend to things over the weekend... This was over a month ago. I don't know if/when anything will be updated. |
They are very slow. I remember sometime ago I contacted them via sourceforge for the same kind of request and it took 2-3 months before they take care of it... Pypi support is not well maintened but I guess it is because it's done only by volunteers... and there is a lot of requests. My idea was to wait until the end of the summer and wait until september-october. If we still don't have answer, then we switch name. Are you ok with this ? |
I am ok because the project should be released anyway to PyPi. But I still hope for them to answer the request... |
Still no answer from PyPi developers... except if someone here know how to reach PyPi admins I think we gonna have to make a choice here... What do you think guys ? |
I agree, we should change the name of the project. I don't expect the PyPi admins to answer anymore, since the big holidays ended since more than a month, and there's still no even a hint of a reply from them (in addition, I tried to look for a mailing list, and it seems that it's not in use since 2013, so that's really not a good sign). |
If you want to still keep a relationship with tqdm, then we can just make up a name with tqdm + something, this way, google searches on tqdm will still probably be able to reach this project. |
👍 for something like |
pbar for progressbar? Then why not just call it "progressbar-tqdm" ? This would be even better for search engines and more evocative for potential users |
I think the best way to do it is keep this repo, empty it and put a message in the README saying that the project has been moved to another repo. If others agree, this is the way I think we should do it :
|
I don't like xxx-tqdm, I think we should not worry to much about SEO. People will end up here and then follow our message saying we have moved. |
I really like a short name such as |
Please see #30. |
We should release a new version to Pypi once some features are added.
We also need to ask a Pypi administrator the permissions to upload the package to https://pypi.python.org/pypi/tqdm
The text was updated successfully, but these errors were encountered: