headers
Yannick Gingras | 2 Nov 2007 00:21
Favicon

Deprecation warnings on PyPI


Greetings Catalogers, 
  I'm the maintainer of a setuptools plugin for git called gitlsfiles.
After the urge to push my first release out of the door had subsided,
I could not help but to realize that it was a really silly name that I
had chosen for this plugin.  So I engaged the other setuptools plugin
maintainers for advice and we all agreed that it would be best for
everyone if our plugins were called setuptools_<rcs>.

I'm about to push setuptools_git 0.3 out of the door but I want people
to stop using gitlsfiles.  I understand, thanks to Barry Warsaw's
investigation, that PyPI has currently no support for automatic
redirection for deprecated packages.

How should we proceed to indicate that the old package are deprecated?
Upload a newer PKG-INFO with a big deprecation warning and no files?
Any other suggestions?

--

-- 
Yannick Gingras
Permalink | Reply | 4 comments |
headers
Martin v. Löwis | 2 Nov 2007 01:18
Picon
Gravatar

Re: Deprecation warnings on PyPI

> How should we proceed to indicate that the old package are deprecated?
> Upload a newer PKG-INFO with a big deprecation warning and no files?
> Any other suggestions?

Depends on what you want to achieve. If you want people to stop using
the old package, you could completely remove it from PyPI.

Regards,
Martin
Permalink | Reply | 2 comments |
headers
Yannick Gingras | 2 Nov 2007 01:25
Favicon

Re: Deprecation warnings on PyPI

"Martin v. Löwis" <martin <at> v.loewis.de> writes:

>> How should we proceed to indicate that the old package are deprecated?
>> Upload a newer PKG-INFO with a big deprecation warning and no files?
>> Any other suggestions?
>
> Depends on what you want to achieve. If you want people to stop using
> the old package, you could completely remove it from PyPI.

That would work but I'd rather have someone searching for gitlsfiles
on PyPI be told that it's deprecated than to let him try new keywords
until he gives up and decides to try the other git plugin for
setuptools.

--

-- 
Yannick Gingras
_______________________________________________
Catalog-SIG mailing list
Catalog-SIG <at> python.org
http://mail.python.org/mailman/listinfo/catalog-sig
Permalink | Reply | 1 comment |
headers
Phillip J. Eby | 2 Nov 2007 01:48
Gravatar

Re: Deprecation warnings on PyPI

At 07:21 PM 11/1/2007 -0400, Yannick Gingras wrote:

>Greetings Catalogers,
>   I'm the maintainer of a setuptools plugin for git called gitlsfiles.
>After the urge to push my first release out of the door had subsided,
>I could not help but to realize that it was a really silly name that I
>had chosen for this plugin.  So I engaged the other setuptools plugin
>maintainers for advice and we all agreed that it would be best for
>everyone if our plugins were called setuptools_<rcs>.
>
>I'm about to push setuptools_git 0.3 out of the door but I want people
>to stop using gitlsfiles.  I understand, thanks to Barry Warsaw's
>investigation, that PyPI has currently no support for automatic
>redirection for deprecated packages.
>
>How should we proceed to indicate that the old package are deprecated?
>Upload a newer PKG-INFO with a big deprecation warning and no files?
>Any other suggestions?

Release a new "version" whose sole purpose is to let people know the 
package no longer exists, e.g.:  http://pypi.python.org/pypi/ObjectRoles/

Now, in my case, I included files that actually wrap the replacement 
package, so dependencies still work.  But for your use case, you 
could just omit the distribution files.
Permalink | Reply | 0 comments |
headers
skip | 2 Nov 2007 02:10
Picon
Favicon

Defunct lockfile package - how to get it removed?


I started working on a lockfile module and wanted to toss it up on PyPI.
Alas, there is a lockfile module already.  Doubly alastic, the one that's in
PyPI seems to be all but empty.  I submitted a request at SF:

    http://sourceforge.net/tracker/index.php?func=detail&aid=1822234&group_id=66150&atid=513504

and sent mail to the author's listed email address.  It seems defunct to me.
The home page and download urls are fairly vague.  I can't find a lockfile
recipe in the Python Cookbook (and can't figure out how to actually search,
so my "searching" was pretty much limited to browsing in a couple categories
and trying a Google search).  Is it possible to remove it from PyPI?

Thanks,

--

-- 
Skip Montanaro - skip <at> pobox.com - http://www.webfast.com/~skip/
Permalink | Reply | 0 comments |
headers
Martin v. Löwis | 2 Nov 2007 07:24
Picon
Gravatar

Re: Deprecation warnings on PyPI

> That would work but I'd rather have someone searching for gitlsfiles
> on PyPI be told that it's deprecated than to let him try new keywords
> until he gives up and decides to try the other git plugin for
> setuptools.

In that case, it would probably best if the new plugin mentions that
it is a replacement for gitlsfiles. Then searching for gitlsfiles would
directly bring up the new plugin.

Regards,
Martin
Permalink | Reply | 0 comments |
headers
Yannick Gingras | 6 Nov 2007 19:18
Favicon

New Trove Classifiers


Greetings Catalogers, 
  I'm about to release setuptools_git and as you know, it obsoletes
gitlsfiles.  I will also put up an empty release of gitlsfiles with
the classifier

  Development Status :: 7 - Inactive

But as Maris Fogels pointed out,

  Development Status :: 8 - Renamed

or

  Development Status :: 8 - Deprecated

might be more appropriate.  A future release of easy_install could
even, in the case of "Renamed", infer the new name from meta-data and
install that instead.  Is this the kind of classifiers you would add?

Also, I notice that there are many "Framework ::" classifiers but two
major Python web frameworks are missing:

  Framework :: Django
  Framework :: Pylons

Best regards, 

--

-- 
Yannick Gingras
(Continue reading)

Permalink | Reply | 1 comment |
headers
Richard Jones | 6 Nov 2007 21:29
Picon

Re: New Trove Classifiers

On Wed, 7 Nov 2007, Yannick Gingras wrote:
> Also, I notice that there are many "Framework ::" classifiers but two
> major Python web frameworks are missing:
>
>   Framework :: Django
>   Framework :: Pylons

That is because they have not been requested. See 
http://wiki.python.org/moin/CheeseShopTutorial

    Richard
Permalink | Reply | 0 comments |

Gmane