Re: [Distutils] How to deprecate a python package

2016-04-05 Thread Alex Grönholm
You can already modify the description and add the "Development Status :: 7 - Inactive" classifier. It would be really nice to filter these out of search results though. 06.04.2016, 02:32, Greg Ewing kirjoitti: Geoffrey Spear wrote: I don't have an answer to your actual question, but I'd not

Re: [Distutils] How to deprecate a python package

2016-04-05 Thread Greg Ewing
Geoffrey Spear wrote: I don't have an answer to your actual question, but I'd not advocate people removing packages; we don't want a npm situation here. :( Perhaps there should be a way of marking a package as deprecated on PyPI, so that it shows a big red warning flag? -- Greg

Re: [Distutils] How to deprecate a python package

2016-04-05 Thread Alexander Walters
Please keep in mind, my suggestion can be done *today* with zero changes to tooling. On 4/5/2016 18:50, Alex Grönholm wrote: Implementing this on Warehouse and pip would have the added benefit of warning users who have a specific version pinned. As for pip letting stderr messages through,

Re: [Distutils] How to deprecate a python package

2016-04-05 Thread Alex Grönholm
Implementing this on Warehouse and pip would have the added benefit of warning users who have a specific version pinned. As for pip letting stderr messages through, that'd be irrelevant if pip had direct support for this. 06.04.2016, 01:47, Alexander Walters kirjoitti: I am not 100% sure if

Re: [Distutils] How to deprecate a python package

2016-04-05 Thread Alexander Walters
I am not 100% sure if pip will let stderr messages though, but i THINK it does. Warnings on import will work regardless. Honestly, I don't care if its marginally easier (and it would only be marginally easier) to mark a package deprecated by flipping a bit on the site - it's the last thing

Re: [Distutils] How to deprecate a python package

2016-04-05 Thread Alex Grönholm
Wouldn't my suggestion or Glyph's be easier for the maintainers? That way they wouldn't even have to make a new release, just modify a setting on the package settings page on PyPI. Also, are you going you see the warning if it's emitted on installation? 06.04.2016, 01:37, Alexander Walters

Re: [Distutils] How to deprecate a python package

2016-04-05 Thread Alexander Walters
On 4/5/2016 18:34, Glyph wrote: Perhaps, before anyone tries to make pip doing something mechanical about deprecations, we should just have the website itself do this sort of redirect? Removing the download would be drastic; giving people an interstitial that says "This package is no longer

Re: [Distutils] How to deprecate a python package

2016-04-05 Thread Glyph
Perhaps, before anyone tries to make pip doing something mechanical about deprecations, we should just have the website itself do this sort of redirect? Removing the download would be drastic; giving people an interstitial that says "This package is no longer maintained, please use $X instead"

Re: [Distutils] How to deprecate a python package

2016-04-05 Thread Alex Grönholm
You make a valid point. This made me recall something -- there is a classifier "Development Status :: 7 - Inactive". As a quick fix, pip could be modified to emit a warning when a distribution containing this classifier is installed. But the problem seems more social than technical. The author

Re: [Distutils] How to deprecate a python package

2016-04-05 Thread Tres Seaver
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 04/05/2016 04:17 PM, Alex Grönholm wrote: > I think an ideal solution would be to add a feature to Warehouse that > would "redirect" any downloads of a library to another. Though I'm not > saying it would be simple. Such a feature would be doing

Re: [Distutils] How to deprecate a python package

2016-04-05 Thread Alexander Walters
The ideal solution is for the maintainer to release one last version of the package with copious use of the warnings module. We really don't want to redirect people blindly - They may be depending on undocumented-but-still-api portions of the original's code that a replacement package might

Re: [Distutils] How to deprecate a python package

2016-04-05 Thread Alex Grönholm
I think an ideal solution would be to add a feature to Warehouse that would "redirect" any downloads of a library to another. Though I'm not saying it would be simple. 05.04.2016, 22:59, Ionel Cristian Mărieș kirjoitti: What's wrong with a new release that just depends on replacement

Re: [Distutils] How to deprecate a python package

2016-04-05 Thread Ionel Cristian Mărieș
What's wrong with a new release that just depends on replacement (assuming there's identical API)? This might be of help: https://pypi.python.org/pypi/pypi-alias If there are API changes or other breakages then maybe a release with a wrapper that emits warnings would be better and generate less

Re: [Distutils] How to deprecate a python package

2016-04-05 Thread Geoffrey Spear
I don't have an answer to your actual question, but I'd not advocate people removing packages; we don't want a npm situation here. :( On Tue, Apr 5, 2016 at 2:46 PM, Thomas Güttler wrote: > I wasted some time because I used a deprecated python package. > > I asked