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
The last commit is 6 years old and so is the information's.
Your nice looking readthedocs version of that repo expose a lot of informations about python and packaging that are not only not up to date but very problematic.
Today python itself has a lot of very good resources where you can learn how to package something. There is no need for such a 3rd party documentation anymore. That is why I would say don't upgrade your repo because there is no need for this anymore.
It will save a lot of time if this outdated information's wouldn't exist anymore. I often have people pointing me to your readthedocs and I have to explain them why the advices from there are not up to date anymore.
The text was updated successfully, but these errors were encountered:
Just bumped into exactly this problem. #58 in particular demonstrates the problem.
In kvesteri/sqlalchemy-utils#630 today, a user reported that extremely old sqlalchemy-utils versions had an unmet dependency. Investigation showed that the old releases were using dependency_links in the setup.py file. When I searched for "pip dependency_links", your ReadTheDocs site popped up as the second link. It was helpful for understanding the historical context, but the information has aged out of relevance.
Please move quickly to remove this outdated information from ReadTheDocs. It doesn't reflect the current packaging ecosystem and no longer works.
The last commit is 6 years old and so is the information's.
Your nice looking readthedocs version of that repo expose a lot of informations about python and packaging that are not only not up to date but very problematic.
Today python itself has a lot of very good resources where you can learn how to package something. There is no need for such a 3rd party documentation anymore. That is why I would say don't upgrade your repo because there is no need for this anymore.
It will save a lot of time if this outdated information's wouldn't exist anymore. I often have people pointing me to your readthedocs and I have to explain them why the advices from there are not up to date anymore.
The text was updated successfully, but these errors were encountered: