Bogus "3.10.0-beta.1" release #207
Comments
See actions/setup-python#207 pytest isn't ready yet: pytest-dev/pytest#8539
See actions/setup-python#207 pytest isn't ready yet: pytest-dev/pytest#8539 (cherry picked from commit 0c1414c)
Referencias: - actions/setup-python#207 - pytest-dev/pytest#8540 (comment) This reverts commit 05e8867.
|
Looks like there's a bogus .tgz on python.org: https://www.python.org/ftp/python/3.10.0/Python-3.10.0b1.tgz |
|
ping 3.10 release manager @pablogsal, should this premature Python-3.10.0b1.tgz be removed? ^ |
Hummm, absolutely. That should not be there :( I don't know what created that tarfile but it should be deleted. I will do it today. Beta is scheduled for next week. |
|
I just removed the bogus tarball. Should be removed from the fpt servers soon. |
|
Could someone revert the changes made in actions/python-versions#92 so we are sure that that artifact won't collide with the beta that we are going to release next week? |
|
Thanks Pablo! @MaksimZhukov will remove the release: actions/python-versions#92 (comment) |
|
I will start an investigation on what process has created such tarball so this doesn't happen again. I checked and there was no other trace of this so my guess is that this has been some kind of automation or human error at some problem in the download server. |
|
Hello everyone! Thanks for the notice! I'm closing this issue. Please let us know if you have any concerns. |
In actions/python-versions#92, it looks like a 3.10.0-beta.1 release was pushed, which also gets used with
python: 3.10-devnow.However, the actual Beta 1 release is planned to happen on May 3rd, thus this tag has nothing to do with the "real" beta 1.
Not sure if that was intended? If it was, it sure seems confusing to me...
The text was updated successfully, but these errors were encountered: