1.0.1 appears to break py2.7 compatibility

Is v1.x supposed to maintain python 2.7 compatibility? It looks like the recent commit from 10 days ago (https://github.com/explosion/catalogue/commit/ef4fd81a122ea43ee0ec958fc86ab6e22291f11d) creates 1.0.1 but introduces changes that require python 3.

This was discovered when trying to install an older compatible spacy package, but pip grabbed 1.0.1 which ends up producing this error:

.../site-packages/catalogue/_importlib_metadata/__init__.py", line 170 def __len__(self) -> int: ^ SyntaxError: invalid syntax

[adrianeboyd]

Sorry about that! There was no great solution here that fixed python 2.7 support, since yanking isn’t supported. I was hoping that relatively few people would have pinned it in the brief period before it was yanked.

v1.0.1 is permanently deleted.

For python 3.6+ you can pin to catalogue==1.0.2. If you need python 2 and python 3 support, you’d need to pin a range instead e.g. as catalogue>=1.0.0,<1.1.0.

[Gerrit-K]

No worries, I was glad there already was a reported issue and it was easy to see what’s going on. Will pin to 1.0.2 then 👍