You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Not saying this to flame the people who worked on it of course, but it puts this package and its dependents in a precarious position. I'm using pdbpp in my daily work and haven't run into issues, so I assume the problematic code paths aren't used, but we should probably think if there is a way to support pyrepl or, if necessary, remove the dependency.
I understand that this might be a hard topic and hope we can find a good solution without explicit of implied shaming
The text was updated successfully, but these errors were encountered:
The pyrepl dependency seems to be not doing so well.
There is rarely any activity and the github and pypi versions have diverged: pypy/pyrepl#36
Additionally, there is python2-only syntax used:
Not saying this to flame the people who worked on it of course, but it puts this package and its dependents in a precarious position. I'm using pdbpp in my daily work and haven't run into issues, so I assume the problematic code paths aren't used, but we should probably think if there is a way to support pyrepl or, if necessary, remove the dependency.
I understand that this might be a hard topic and hope we can find a good solution without explicit of implied shaming
The text was updated successfully, but these errors were encountered: