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
