Originally mapped to gevent-socketio, which is outdated and hasn't been updated since 2016. Anyone importing socketio is much more likely to mean python-socketio now.
telegram is a hollow pypi package, so pipreqs will try to install that instead of python-telegram-bot, which have a module named telegram.
I'll ask to approve this change, as I'm blocked with my Pipedream workflow.
Bump tests version and supported versions in setup.py
stdlib: update packages for python 3.9
By utilizing the packages listed in
https://github.com/jackmaney/python-stdlib-list
for python 3.8 and 3.9, we were able to drop all stdlib packages that
existed solely in python 2 and add the missing stdlib python 3 packages
We are dropping support for python 2, so we are dropping the
verification of which python version is currently running and we also stop
checking for python2 specific packages.
We also drop the encoding definition since python3 uses utf-8 as
default.
The helper open_func function is also substituted by open.
This reverts commit 90102acdbb23c09574d27df8bd1f568d34e0cfd3.
Now that we are ready to make a new release we can revert the revert and
hopefuly never have to solve a mess like this again to keep master
synchronized with the latest release
By reverting all commits done since release v0.4.10 we will have the
master branch synchronized with the latest release available in pipy.
All commits done since the latest release will be moved to another
branch called `next` where we will centralize development. Once we are ready
for a new release of pipreqs, the `next` branch will be merged back on to
master and a new release will be made.
This change will make development more organized and will avoid new
issues from users complaining about features only present in master not working
on their installation of pipreqs.
I would also like to thank @pedroteosousa for his help on reverting and
squashing all commits
When trying to generate requirements.txt and file is already existent, the user message produced asks for "Requirements.txt" instead of "requirements.txt".
This may cause some trouble when used in case sensitive env, as well as in automated scripts.
