Mailing List Archive

problem with abandonned lib pyliblo
Hi.

There is a problem with the lib pyliblo, the source code of the lib is here:
https://github.com/dsacre/pyliblo

The problem is that the lib is now incompatible with python3.11 because it
uses inspect.getargspec function which does not exist anymore. This is very
easy to fix, the main problem is that the author Dominic Sacré does not
answer anymore to any message (PR, issues, email), so there is no hope he
will fix the problem.

I am ready to maintain this lib myself, I could simply fork it and rename
the lib to pass it to pip list, but all programs using it will have to
rename the lib in their requirements.

Is there a sort of protocol to do when this happens, in order to replace
the source package with a new version ?

thanks for your help

Mathieu
Re: problem with abandonned lib pyliblo [ In reply to ]
On Tue, 2022-12-20 at 12:31 +0100, Mathieu Picot wrote:
> There is a problem with the lib pyliblo, the source code of the lib is here:
> https://github.com/dsacre/pyliblo
>
> The problem is that the lib is now incompatible with python3.11 because it
> uses inspect.getargspec function which does not exist anymore. This is very
> easy to fix, the main problem is that the author Dominic Sacré does not
> answer anymore to any message (PR, issues, email), so there is no hope he
> will fix the problem.
>
> I am ready to maintain this lib myself, I could simply fork it and rename
> the lib to pass it to pip list, but all programs using it will have to
> rename the lib in their requirements.
>
> Is there a sort of protocol to do when this happens, in order to replace
> the source package with a new version ?

If you mean on pypi, then the process is described here:

https://peps.python.org/pep-0541/#how-to-request-a-name-transfer

However, I should point out that someone forked it already and the fork
seems to be actively maintained:

https://pypi.org/project/pyliblo3/

So it may be worth contacting that person first and figuring out
a common way forward. Having some packages depend on now-reclaimed
"pyliblo" and "pyliblo3" fork would be the worst possible outcome.

--
Best regards,
Micha? Górny

_______________________________________________
Python-Dev mailing list -- python-dev@python.org
To unsubscribe send an email to python-dev-leave@python.org
https://mail.python.org/mailman3/lists/python-dev.python.org/
Message archived at https://mail.python.org/archives/list/python-dev@python.org/message/UQ6JG4AEON4QDC7C2U2V7577WREX4HL6/
Code of Conduct: http://python.org/psf/codeofconduct/