Hi Toni:

In message <ZiaTKl8lCD0lAl48@laptop-t.office.oeko.net>,
Toni Mueller writes:
>On Mon, Apr 22, 2024 at 04:08:45PM +0000, John Rouillard wrote:
>> John Rouillard added the comment:
>> > It looks like I had a broken file in my pip cache
>> Wow that's annoying. I'm glad it's fixed.
>
>the file was not technically broken, but the code in the file was
>broken. I had just installed it today, although the file in the cache
>was there for a bit longer already - I had played with roundup before.
>
>The __init__.py in my broken archive was empty, while the __init__.py in
>the current archive is several hundred bytes long and has all the
>information. So I presume that someone uploaded a new archive with the
>same version number.

AFAIK you can't overwrite releases on PyPi. You need to generate a new
release with a new version number. (E.G. there are two roundup 2.3.0
beta releases on test.pypi.because of a packaging screwup.) There has
been some discussion about permitting overwriting of releases though.

It sounds like there was a glitch during the download. However since
the tarball is compressed, I would expect the file would be unusable
past the point of corruption so....

The tarball that is built is unpacked and tested. Then that exact same
tarball is uploaded using twine. I don't downloaded the file again
from pypi and compare the gpg signature though. I assume the upload
was successful (and so far it has been).

>On a side note, where can I get 2.4.0?

2.4.0 beta should be released late May with a 2.4.0 to be released in
July.

If you want to work with the current development head release that
will be 2.4.0 (note it doesn't have the web-component class helper
yet, their last day with me is 15 May), you can clone from the
mercurial repo using the directions at:
https://roundup-tracker.org/code.html.

You can also clone from the git repo
https://github.com/roundup-tracker/roundup we use for CI.