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
Claim package name 'dppy' #5307
Comments
Nobody can help? 🆘 |
Hi there, still nobody to help ? 😿 |
According to PEP541, in order to transfer a project name, a project must first be determined to be abandoned:
I could not determine a project home page.
The most recent release was 2018-08-01, which was only six months ago. In a strict interpretation of PEP 541, there are still six months to go before that criteria is met.
I have emailed the owner of the project using the only contact information we have. This contact information does not appear publicly. (Given the above dates, we can only ask politely if the owner is interested in releasing the name.) In the meantime, there are a few other things to be considered:
Given no public contact information, that's a tough one.
As noted, even though releases artifacts exist, both the wheel and sdist contain nothing more than an empty
Can you speak to these last two points? |
Hi @jamadden, thanks you very much for this thorough answer!
I am a Ph.D. student whose topic of research is Determinantal Point Processes with very used acronym DPPs and mostly code with Python, hence the name A companion paper for the toolbox is already written for later submission to a Open Source Software track of a Machine Learning journal surch as JMLR-MLOSS In particular we would very much like to have a
I would argue again that
More and more people are becoming aware of this project and it would be very confusing not to provide a natural We feel the project mature enough to be put on PyPI, however:
We've been testing different names for the project on TestPyPi and removed them. The last one we came up with (yesterday) is DPPyPI but we are still not convinced that this is the best fit to not confuse current and future users 😕
Actually, I've tried to contact the Takayuki Yagi which would fit the most a Machine Learning guy but didn't get any answer
Thank you very much for your consideration! |
Hmm, I forgot about the Invalid Projects part of PEP 541:
The "project is name squatting (package has no functionality or is empty)" clause certainly seems to apply here too. |
Interesting! |
Such cases are extremely rare. The vast majority of the 'PEP541' cases I've looked at which have been resolved have ultimately involved a willing transfer; the ones that are remain open are the cases without a clear-cut answer. I've done some data gathering and put out some hypotheses, but those are just my guesses and ultimately I think some of the more experienced PyPI admins (e.g., @ewdurbin @dstufft @di) would need to have a look and set a course of action. It may take same time. |
Hi guys, Next month, it will be 1 year since the dppy project is on PyPI without any activity. Can we anticipate an action to make sure the name Thanks in advance |
Hi @guilgautier, what's your username on PyPI? |
Hi @di, Thanks for your reply! |
Done. Please note that you won't be able to make releases using versions |
Hi there!
I've spent some time working on DPPy and I now feel ok to reference it on PyPi.
However, the name
dppy
is already taken see dppy, but:What can I do to make my DPPy project as the (or at least not void)
dppy
on PyPi ?Btw, I've started testing the pypi pipeline on https://test.pypi.org/project/dppy-dpps/
The text was updated successfully, but these errors were encountered: