new PyPI release (9.4.0) #4
Comments
|
i requested access in this ticket, we'll see where it goes: https://sourceforge.net/p/pypi/support-requests/709/ considering how many requests are piled up in there, i'm not holding my breath... :/ |
|
Suggestion: let's register If PyPI admins ever decide to give us access to the original |
|
sounds good. |
|
FWIW, I see these kinds of requests on their Github tracker as well. |
|
While not ideal, continuing to cut releases on GH will prompt some distributions to package newer code. I realize this means that we would be in the weird situation where pypi was behind other forms of distribution, but at least we would be able to push the code out. |
|
note that the new Warehouse deployment on PyPI.org may have different rules that could work around the issues we have with abandoned software. see: https://pypi.org/help/#project-name-claim there's PEP-0541 under way to fix this, apparently. |
|
HEADS UP: i'll look at making a release, including on PyPI, later tomorrow or next week. thanks to @fuzzy76 I've also tried my luck at transfering PyPI ownership in pypi/legacy#725 - if that fails, I'll just use the i've also asked the folks behind the linkchecker orga on github to see if they could transfer ownership as well, not sure how i missed that, see https://github.com/linkchecker/linkchecker.github.io/issues/2 |
|
Sounds good. |
|
yep - and it sure looks like this is what will happen - no answer from the linkchecker orga or the pypa people yet, so I guess we're on our own for that next release... i'll give it another week. |
|
@anarcat is there any update on this issue? Thanks! |
|
On 2017-12-12 17:49:54, legrostdg wrote:
@anarcat is there any update on this issue? Thanks!
unfortunately, i'm swamped with work and i am unlikely to do a release
before the new year.
apologies for those who wanted a new release for the holidays season. :)
|
|
if there is problem with pypi namespace you could temporarily just hint people to install using |
|
Would it be possible to at least update the Debian package to use this repo? |
|
(with a new release) |
|
sure. if i had time. which i don't right now, as you might have noticed. :) sorry - i can barely keep up with the PRs that are coming in here... dealing with administrative annoyances such as this is not so exciting, so it gets lower priority... |
|
i poked the pypa people, again. sigh... |
|
oh god, this unblocked! we have ownership! i logged in pypi (had to use chrome because firefox 2FA fail) and i see the project! all of a sudden, we should make a release!!! do we want to push things out as they are now? or just push 9.4? or what do we do! so exciting! |
|
Let's |
|
I ran It's probably fine. I'd maybe like to download a 9.3.0 sdist from PyPI and see what files it contains and what files it omits. |
|
Installing 9.4.0 on ubuntu 18.04 did not work for me: |
9.4.0 (and current Git master) do not work on Python 3. I haven't tried a pip install but from the log provided it appears to have been installed for Python 3 which would be expected to fail. |
|
I never did any twine uploads. https://pypi.org/project/LinkChecker/ doesn't have 9.4. I would love it if you would twine upload a 9.4.0 sdist. |
|
If I understood correctly, @anarcat could push a new release, which would be the first one since 9.3 from 2014 on pypi? Or is there anything one could help with? Thanks a lot for your work on such a useful project! ❤️ |
correct. i'm just too swamped to coordinate that work right now, sorry. :( |
|
@linkchecker/developers - it seems i'm the bottleneck here, and don't have time to followup. can i grant one of you folks access? just give me a pypi username and i can add you to the group. that said, it seems @mgedmin is already an owner on the repo, so i'm not sure i'm the only one that can do this. :) |
|
Yeah, I have pypi rights, but I also have burnout and a middling sense of responsibility. I care enough that I don't want to do a bad job in making the release, but I don't care enough to invest enough effort to do a good job. (For projects I maintain I have invested enough upfront effort that I can type If anyone wants to be my conscience and tell me that I ought to do the following:
then I will do it. I'm a bit worried that I'm also slightly worried that But maybe releasing a slightly broken 9.4 sdist to pypi is less bad than the current state of affairs (totally broken 9.3 that doesn't like new requests versions due to a busted version check)? And at least 9.4.0 is tagged and released elsewhere, if not to PyPI. So, please tell me to do it and I'll do it. (I did all the steps except the twine upload, fwiw.) |
|
FWIW Gentoo has been using the v9.4.0 tagged archive https://github.com/linkchecker/linkchecker/archive/v9.4.0.tar.gz for over a year now with no customisation (save the bash completion) and a standard disutils based install with no bugs raised. |
|
Yeah, but the github tarball will contain all the files that are missing from the sdist due to lack of MANIFEST.in rules. |
|
I would say you are right to be cautious. I created an sdist tarball from the tag and adapted the Gentoo ebuild, installation failed with: |
|
My mistake -- that was the Gentoo ebuild selecting development.mdwn. Once I remove that Gentoo instruction it finished installation, I can't actually install it on my machine because I have got rid of all the Python 2 versions of the supporting packages. |
|
I compared the files in the 9.3 tarball on PyPI with what I get in the 9.4 tarball produced from the git tag. The 9.4 is missing
I think it's fine to release it as is. |
|
I've uploaded https://pypi.org/project/LinkChecker/9.4.0/. |
|
9.4.0 release is not working for me, after doing : also during installation, my requests is downgraded: |
|
9.4.0 does not support Python 3; for that you need the current git master. |
|
(I am surprised and dismayed that the installation didn't fail...) |
before anyone else jumps this issue with problems they find in 9.4.0: don't report them here! :) open a new issue and document it properly, otherwise it makes our lives needlessly hard to triage... |
so a key issue that is missing is a PyPI release.
i have pushed the 9.3.1 tag, but that's mostly cosmetic - the release hasn't been pushed to PyPI because we don't have access. i've reviewed the process documented here:
http://code.activestate.com/lists/python-distutils-sig/24089/
and it seems we can ask for access on ... ahem... sourceforge. so i've requested a password reset and will do that there. :)
The text was updated successfully, but these errors were encountered: