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
I was wondering what the state of the package is like.
I had been working on a proxy broker of mine for python 3.10 (a handful of sources and HTTPS only), since I could not find anything that I liked and felt was easy enough to work with, until I came across your revamp of this 5-year-old package.
after browsing through the issues, I found out that you recently moved to poetry as package manager (which I agree with), but it is not clear to me what is the roadmap ahead in terms of development, documentation and release on PyPI.
the latter seems to be pending until your transition to python 3.10 is complete, am I right?
also, the README seems to be a copy-paste of the old fork, still pointing to the old package release on PyPI and with outdated TODOs.
tl;dr - I don't think it would make much sense for me to keep developing a small package with little maintenance; however, the package was being written for python 3.10, so I should be able to help in transitioning the async code to that version.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
hi @bluet,
I was wondering what the state of the package is like.
I had been working on a proxy broker of mine for python 3.10 (a handful of sources and HTTPS only), since I could not find anything that I liked and felt was easy enough to work with, until I came across your revamp of this 5-year-old package.
after browsing through the issues, I found out that you recently moved to poetry as package manager (which I agree with), but it is not clear to me what is the roadmap ahead in terms of development, documentation and release on PyPI.
the latter seems to be pending until your transition to python 3.10 is complete, am I right?
also, the README seems to be a copy-paste of the old fork, still pointing to the old package release on PyPI and with outdated TODOs.
tl;dr - I don't think it would make much sense for me to keep developing a small package with little maintenance; however, the package was being written for python 3.10, so I should be able to help in transitioning the async code to that version.
All reactions