this is causing too many weird conflicts to merge next into master. Also,
requirements file was deprecated in next branch in lieu of
pyproject.toml
This reverts commit 68f9b2859d45a60e699839f87b1b9558cd36a329.
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.
While trying to upload release 0.4.11 to pypi I got a few errors due to
the rst syntax of the readme. This commit fixes the errors but not the
warnings (mostly undeclared long format description type in setup.py)
This commit essentially adds back tests to our CI pipeline. They were
previously dropped due to Travis pricing policy change.
This workflow utilizes a few interesting projects to make this action
easier to maintain such as the codecov github action
and the tox-gh-actions project
(https://github.com/ymyzk/tox-gh-actions)
This commit uses codecov instead of coveralls because using coveralls
directly inside GH-actions is buggy and the official coveralls action
only supports lcov reports which we can't seem to be able to generate at
the moment. For more information see the pull request that introduced
this commit
Review dog is an incredible project that makes linting and formatting
review a breeze by commenting inline what is wrong in a pull request.
This makes the review process easier for the maintainer and also
provides a clearer feedback to the contributor
Since travis changed its pricing policy it has become more limited in
what we can accomplish with it. It now uses a limited credit model for
open source projects which besides being cumbersome puts the project in
a precarious position where we may be unable to run tests if we dont
have anymore credits.
For this reason we will be moving to github actions since they seem to
be the best alternative at the moment
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.
