From kent37 at tds.net  Thu Dec  6 16:08:15 2007
From: kent37 at tds.net (Kent Johnson)
Date: Thu, 06 Dec 2007 10:08:15 -0500
Subject: [Catalog-sig] Cheeseshop classifier for Django
Message-ID: <4758105F.8040302@tds.net>

Hi,

I suggest that a Cheeseshop classifier be added for Django components, e.g.
Framework :: Django

There are several Django-related items already:
http://pypi.python.org/pypi?%3Aaction=search&term=django&submit=search

Thanks,
Kent

From richardjones at optushome.com.au  Fri Dec 14 10:59:25 2007
From: richardjones at optushome.com.au (Richard Jones)
Date: Fri, 14 Dec 2007 20:59:25 +1100
Subject: [Catalog-sig] Cheeseshop classifier for Django
In-Reply-To: <4758105F.8040302@tds.net>
References: <4758105F.8040302@tds.net>
Message-ID: <200712142059.25209.richardjones@optushome.com.au>

On Fri, 7 Dec 2007, Kent Johnson wrote:
> I suggest that a Cheeseshop classifier be added for Django components, e.g.
> Framework :: Django

Added, sorry for the delay.


    Richard

From ddreese at ir.qatarairways.com  Wed Dec 19 21:22:17 2007
From: ddreese at ir.qatarairways.com (Roe Dorothy)
Date: Wed, 19 Dec 2007 20:22:17 +0000
Subject: [Catalog-sig] Will Solaris ZFS work with the Solaris Cluster
	software?
Message-ID: <47697D79.3020105@camelot.vrn.ru>

An HTML attachment was scrubbed...
URL: http://mail.python.org/pipermail/catalog-sig/attachments/20071219/e5786c7b/attachment.htm 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: foist.gif
Type: image/gif
Size: 12149 bytes
Desc: not available
Url : http://mail.python.org/pipermail/catalog-sig/attachments/20071219/e5786c7b/attachment.gif 

From ziade.tarek at gmail.com  Thu Dec 20 12:39:49 2007
From: ziade.tarek at gmail.com (=?UTF-8?Q?Tarek_Ziad=C3=A9?=)
Date: Thu, 20 Dec 2007 03:39:49 -0800 (PST)
Subject: [Catalog-sig]  Distribution of Pypi
Message-ID: <14434880.post@talk.nabble.com>


Hi,

I would like to run my own cheeseshop for some project managment, is there
any public release of the pypi package i can use, or trunk is my friend
(https://svn.python.org/packages/trunk) ?

What is its licence by the way ? Can't find it in the svn

Regards

Tarek
-- 
View this message in context: http://www.nabble.com/Distribution-of-Pypi-tp14434880p14434880.html
Sent from the Python - catalog-sig mailing list archive at Nabble.com.


From fdrake at gmail.com  Thu Dec 20 14:58:27 2007
From: fdrake at gmail.com (Fred Drake)
Date: Thu, 20 Dec 2007 08:58:27 -0500
Subject: [Catalog-sig] Removing oneself from a project
Message-ID: <9cee7ab80712200558k4cc10a3n11d61ca0075c988a@mail.gmail.com>

A couple of months ago, someone (probably meaning well) added me to a
large number of Zope-related projects on PyPI with "Owner"
priviledges.  Many of them I'm not even remotely familiar with.

I'd like to to remove myself from those projects, but am thwarted on
every attempt.  After logging in to PyPI, I navigate to the role
management form for the project I'm trying to remove myself from.
After filling in the form and clicking "Remove Role", my browser pops
up another basic-auth authentication dialog.  After entering my
credentials, the dialog is simply repeated.  The presence or absence
of a "/" after "/pypi" in the URL makes no difference.

I'm guessing this is a bug, but I'm willing to be enlightened.

Adding unsuspecting PyPI users to a package on PyPI seems a rather bad
way to advocate a project; I'm suspicious spammers will catch on to
this.  :-/  (Mostly 'cause I know how much they hate us all.)


  -Fred

-- 
Fred L. Drake, Jr.    <fdrake at gmail.com>
"Chaos is the score upon which reality is written." --Henry Miller

From martin at v.loewis.de  Fri Dec 21 07:13:18 2007
From: martin at v.loewis.de (=?ISO-8859-1?Q?=22Martin_v=2E_L=F6wis=22?=)
Date: Fri, 21 Dec 2007 07:13:18 +0100
Subject: [Catalog-sig] Removing oneself from a project
In-Reply-To: <9cee7ab80712200558k4cc10a3n11d61ca0075c988a@mail.gmail.com>
References: <9cee7ab80712200558k4cc10a3n11d61ca0075c988a@mail.gmail.com>
Message-ID: <476B597E.7000300@v.loewis.de>

> I'm guessing this is a bug, but I'm willing to be enlightened.

It's best to report bugs at sf.net/projects/pypi.

Regards,
Martin

From fdrake at gmail.com  Fri Dec 21 07:22:37 2007
From: fdrake at gmail.com (Fred Drake)
Date: Fri, 21 Dec 2007 01:22:37 -0500
Subject: [Catalog-sig] Removing oneself from a project
In-Reply-To: <476B597E.7000300@v.loewis.de>
References: <9cee7ab80712200558k4cc10a3n11d61ca0075c988a@mail.gmail.com>
	<476B597E.7000300@v.loewis.de>
Message-ID: <9cee7ab80712202222n50080728p15edd74195682f06@mail.gmail.com>

On Dec 21, 2007 1:13 AM, "Martin v. L?wis" <martin at v.loewis.de> wrote:
> It's best to report bugs at sf.net/projects/pypi.

Thanks!  And done:

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


  -Fred

-- 
Fred L. Drake, Jr.    <fdrake at gmail.com>
"Chaos is the score upon which reality is written." --Henry Miller

From ziade.tarek at gmail.com  Wed Dec 26 18:43:53 2007
From: ziade.tarek at gmail.com (=?UTF-8?Q?Tarek_Ziad=C3=A9?=)
Date: Wed, 26 Dec 2007 09:43:53 -0800 (PST)
Subject: [Catalog-sig]  permissive trove classification
Message-ID: <14504481.post@talk.nabble.com>


Hello,


I am implementing a PyPI-like server, to allow people using it as a
cheeseshop alternative. It may have its own trove classification though,
that differs from PyPI. This is intended because the server provide a
"package center" that has its own domain-specific categories.

To make `file_upload` work on both Pypi and my implementation, it has to be
permissive on the classifiers passed in the metadata.

In other words, if the classifier is not found in the server, it doesn't use
it. This would allow a distribution of eggs on several servers and a
decentralized way to manage troves.

I've tried to upload a file with a classifier that doesn't exists on Pypi
and it fails silently. The result was the lost of all metadata on the
package.

I would like to suggest a "permissive trove classification" on servers that
implement a package index.

I can work on a more formal document (some kind of PEP?) to explain the
changes needed in the current
PyPI implementation and on a formal definition of a PyPI (server side) api
(a bit like the DB API). I am also willing to spend the time needed to code
it.

Regards

Tarek

-- 
View this message in context: http://www.nabble.com/permissive-trove-classification-tp14504481p14504481.html
Sent from the Python - catalog-sig mailing list archive at Nabble.com.


From doug at hellfly.net  Wed Dec 26 19:07:21 2007
From: doug at hellfly.net (Doug Hellmann)
Date: Wed, 26 Dec 2007 13:07:21 -0500
Subject: [Catalog-sig] permissive trove classification
In-Reply-To: <14504481.post@talk.nabble.com>
References: <14504481.post@talk.nabble.com>
Message-ID: <B1B7D499-D2F0-4C3B-9F0A-E9CBAF785B89@hellfly.net>

As a package owner/maintainer, I would much rather have a warning or  
error message from the server when I upload something with an unknown  
category. That way I can correct any typographical mistakes.  If the  
server completely ignores the bad data, I don't have an easy way to  
realize something is wrong.

Doug

On Dec 26, 2007, at 12:43 PM, Tarek Ziad? wrote:

>
> Hello,
>
>
> I am implementing a PyPI-like server, to allow people using it as a
> cheeseshop alternative. It may have its own trove classification  
> though,
> that differs from PyPI. This is intended because the server provide a
> "package center" that has its own domain-specific categories.
>
> To make `file_upload` work on both Pypi and my implementation, it  
> has to be
> permissive on the classifiers passed in the metadata.
>
> In other words, if the classifier is not found in the server, it  
> doesn't use
> it. This would allow a distribution of eggs on several servers and a
> decentralized way to manage troves.
>
> I've tried to upload a file with a classifier that doesn't exists  
> on Pypi
> and it fails silently. The result was the lost of all metadata on the
> package.
>
> I would like to suggest a "permissive trove classification" on  
> servers that
> implement a package index.
>
> I can work on a more formal document (some kind of PEP?) to explain  
> the
> changes needed in the current
> PyPI implementation and on a formal definition of a PyPI (server  
> side) api
> (a bit like the DB API). I am also willing to spend the time needed  
> to code
> it.
>
> Regards
>
> Tarek
>
> -- 
> View this message in context: http://www.nabble.com/permissive- 
> trove-classification-tp14504481p14504481.html
> Sent from the Python - catalog-sig mailing list archive at Nabble.com.
>
> _______________________________________________
> Catalog-SIG mailing list
> Catalog-SIG at python.org
> http://mail.python.org/mailman/listinfo/catalog-sig


From ziade.tarek at gmail.com  Wed Dec 26 19:17:50 2007
From: ziade.tarek at gmail.com (=?UTF-8?Q?Tarek_Ziad=C3=A9?=)
Date: Wed, 26 Dec 2007 10:17:50 -0800 (PST)
Subject: [Catalog-sig] permissive trove classification
In-Reply-To: <B1B7D499-D2F0-4C3B-9F0A-E9CBAF785B89@hellfly.net>
References: <14504481.post@talk.nabble.com>
	<B1B7D499-D2F0-4C3B-9F0A-E9CBAF785B89@hellfly.net>
Message-ID: <14504721.post@talk.nabble.com>



Doug Hellmann wrote:
> 
> As a package owner/maintainer, I would much rather have a warning or  
> error message from the server when I upload something with an unknown  
> category. That way I can correct any typographical mistakes.  If the  
> server completely ignores the bad data, I don't have an easy way to  
> realize something is wrong.
> 

A warning would be fine, as long as the server treats the other items.
An error would block the process.

For example, if we have 2 pypi servers, one that deals with 1..n categories,
one with A..Z,
we could have a package with such classifiers:

classifiers = ['category 1', 'category A', 'category 2']

Each server could pick the categories it knows.

Tarek
-- 
View this message in context: http://www.nabble.com/permissive-trove-classification-tp14504481p14504721.html
Sent from the Python - catalog-sig mailing list archive at Nabble.com.


From doug at hellfly.net  Wed Dec 26 20:13:52 2007
From: doug at hellfly.net (Doug Hellmann)
Date: Wed, 26 Dec 2007 14:13:52 -0500
Subject: [Catalog-sig] permissive trove classification
In-Reply-To: <14504721.post@talk.nabble.com>
References: <14504481.post@talk.nabble.com>
	<B1B7D499-D2F0-4C3B-9F0A-E9CBAF785B89@hellfly.net>
	<14504721.post@talk.nabble.com>
Message-ID: <09EA102E-8B33-465C-9CDD-B3E71C2B586B@hellfly.net>

Offering a warning and accepting the known categories seems like a  
reasonable compromise.  Is it an error if there are no known  
categories in the list?

Doug

On Dec 26, 2007, at 1:17 PM, Tarek Ziad? wrote:

>
>
> Doug Hellmann wrote:
>>
>> As a package owner/maintainer, I would much rather have a warning or
>> error message from the server when I upload something with an unknown
>> category. That way I can correct any typographical mistakes.  If the
>> server completely ignores the bad data, I don't have an easy way to
>> realize something is wrong.
>>
>
> A warning would be fine, as long as the server treats the other items.
> An error would block the process.
>
> For example, if we have 2 pypi servers, one that deals with 1..n  
> categories,
> one with A..Z,
> we could have a package with such classifiers:
>
> classifiers = ['category 1', 'category A', 'category 2']
>
> Each server could pick the categories it knows.
>
> Tarek
> -- 
> View this message in context: http://www.nabble.com/permissive- 
> trove-classification-tp14504481p14504721.html
> Sent from the Python - catalog-sig mailing list archive at Nabble.com.
>
> _______________________________________________
> Catalog-SIG mailing list
> Catalog-SIG at python.org
> http://mail.python.org/mailman/listinfo/catalog-sig


From martin at v.loewis.de  Wed Dec 26 23:44:12 2007
From: martin at v.loewis.de (=?ISO-8859-1?Q?=22Martin_v=2E_L=F6wis=22?=)
Date: Wed, 26 Dec 2007 23:44:12 +0100
Subject: [Catalog-sig] PyPI outage
Message-ID: <4772D93C.9090309@v.loewis.de>

I'm planning to upgrade the system running PyPI tomorrow (Thursday)
around 8:00 UTC; PyPI may not be available during that time.

Regards,
Martin

From ziade.tarek at gmail.com  Thu Dec 27 11:44:04 2007
From: ziade.tarek at gmail.com (=?UTF-8?Q?Tarek_Ziad=C3=A9?=)
Date: Thu, 27 Dec 2007 02:44:04 -0800 (PST)
Subject: [Catalog-sig] permissive trove classification
In-Reply-To: <09EA102E-8B33-465C-9CDD-B3E71C2B586B@hellfly.net>
References: <14504481.post@talk.nabble.com>
	<B1B7D499-D2F0-4C3B-9F0A-E9CBAF785B89@hellfly.net>
	<14504721.post@talk.nabble.com>
	<09EA102E-8B33-465C-9CDD-B3E71C2B586B@hellfly.net>
Message-ID: <14511741.post@talk.nabble.com>



Doug Hellmann wrote:
> 
> Offering a warning and accepting the known categories seems like a  
> reasonable compromise.  Is it an error if there are no known  
> categories in the list?
> 

Well if all classifiers are unknown from any server, this would just not do
anything on those
servers. Each server takes care of its trove and browse the classifiers sent
by the package
to pick the one it knows. It means that if you made a mistake on the
category name intended
for a given server, it will not raise an error and pop a warning.

Let's take an example: I have a server that deals with Zope packages. The
trove for PyPI is:

  Development Status :: 5 - Production/Stable
  Intended Audience :: Developers
  License :: OSI Approved :: Zope Public License
  Programming Language :: Python
  Topic :: Database
  Topic :: Software Development :: Libraries :: Python Modules
  Operating System :: Microsoft :: Windows
  Operating System :: Unix

Now my company "ACME", classifies packages in two categories: public,
private. It has a copy
of the PyPI trove too.
So my classifier become:

  ACME :: Visibility :: Public 
  Development Status :: 5 - Production/Stable
  Intended Audience :: Developers
  License :: OSI Approved :: Zope Public License
  Programming Language :: Python
  Topic :: Database
  Topic :: Software Development :: Libraries :: Python Modules
  Operating System :: Microsoft :: Windows
  Operating System :: Unix

When I upload it to the cheeseshop, I would expect something like this in
return:

Warning "ACME :: Visibility :: Public" classifier not found on the server
200 - OK 

When I upload in ACME:

200 - OK 
-- 
View this message in context: http://www.nabble.com/permissive-trove-classification-tp14504481p14511741.html
Sent from the Python - catalog-sig mailing list archive at Nabble.com.


From doug at hellfly.net  Thu Dec 27 13:57:00 2007
From: doug at hellfly.net (Doug Hellmann)
Date: Thu, 27 Dec 2007 07:57:00 -0500
Subject: [Catalog-sig] permissive trove classification
In-Reply-To: <14511741.post@talk.nabble.com>
References: <14504481.post@talk.nabble.com>
	<B1B7D499-D2F0-4C3B-9F0A-E9CBAF785B89@hellfly.net>
	<14504721.post@talk.nabble.com>
	<09EA102E-8B33-465C-9CDD-B3E71C2B586B@hellfly.net>
	<14511741.post@talk.nabble.com>
Message-ID: <41B8C2E7-0F79-4D89-978B-37DB08754177@hellfly.net>


On Dec 27, 2007, at 5:44 AM, Tarek Ziad? wrote:

>
>
> Doug Hellmann wrote:
>>
>> Offering a warning and accepting the known categories seems like a
>> reasonable compromise.  Is it an error if there are no known
>> categories in the list?
>
> Now my company "ACME", classifies packages in two categories: public,
> private. It has a copy
> of the PyPI trove too.
> So my classifier become:
>
>   ACME :: Visibility :: Public
>   Development Status :: 5 - Production/Stable
>   Intended Audience :: Developers
>   License :: OSI Approved :: Zope Public License
>   Programming Language :: Python
>   Topic :: Database
>   Topic :: Software Development :: Libraries :: Python Modules
>   Operating System :: Microsoft :: Windows
>   Operating System :: Unix
>
> When I upload it to the cheeseshop, I would expect something like  
> this in
> return:
>
> Warning "ACME :: Visibility :: Public" classifier not found on the  
> server
> 200 - OK

That makes sense.

On the other hand, suppose that for some reason "ACME ::  
Visibility :: Public" was the only category listed for your software  
(or that you had a long list of ACME-specific categories, none of  
which are known to PyPI).  What response would you expect when you  
uploaded it to PyPI?  I would want an error, since the resulting  
package would not show up in any categories at all.

Doug


From martin at v.loewis.de  Thu Dec 27 14:59:11 2007
From: martin at v.loewis.de (=?ISO-8859-1?Q?=22Martin_v=2E_L=F6wis=22?=)
Date: Thu, 27 Dec 2007 14:59:11 +0100
Subject: [Catalog-sig] permissive trove classification
In-Reply-To: <14504481.post@talk.nabble.com>
References: <14504481.post@talk.nabble.com>
Message-ID: <4773AFAF.8050506@v.loewis.de>

> I can work on a more formal document (some kind of PEP?) to explain the
> changes needed in the current
> PyPI implementation and on a formal definition of a PyPI (server side) api
> (a bit like the DB API). I am also willing to spend the time needed to code
> it.

Please do. I would suggest you put any design documents into
wiki.python.org/moin, with links from

http://wiki.python.org/moin/CheeseShopDev

The actual patches to PyPI should to the SF tracker.

If you can, please choose wiki names that don't list CheeseShop
anymore; use PyPI instead.

Regards,
Martin

From fdrake at gmail.com  Thu Dec 27 19:22:39 2007
From: fdrake at gmail.com (Fred Drake)
Date: Thu, 27 Dec 2007 13:22:39 -0500
Subject: [Catalog-sig] permissive trove classification
In-Reply-To: <41B8C2E7-0F79-4D89-978B-37DB08754177@hellfly.net>
References: <14504481.post@talk.nabble.com>
	<B1B7D499-D2F0-4C3B-9F0A-E9CBAF785B89@hellfly.net>
	<14504721.post@talk.nabble.com>
	<09EA102E-8B33-465C-9CDD-B3E71C2B586B@hellfly.net>
	<14511741.post@talk.nabble.com>
	<41B8C2E7-0F79-4D89-978B-37DB08754177@hellfly.net>
Message-ID: <9cee7ab80712271022q73805833jd2318602cbf0ff37@mail.gmail.com>

On Dec 27, 2007 7:57 AM, Doug Hellmann <doug at hellfly.net> wrote:
> I would want an error, since the resulting
> package would not show up in any categories at all.

But the Trove classifiers are optional now, so I'm not at all sure it
should be turned into an error.  Leaving it as a warning seems
sufficient; someone who sees that the warning was caused by a typo
after all can still go to the web form and edit the set of classifiers
(or maybe re-register after correcting the metadata; I'm not sure if
that'll work).

Or are you proposing that the classifiers become required?  That's
going to cause a lot of packages to require work before new versions
can be released, which doesn't seem good to me.


  -Fred

-- 
Fred L. Drake, Jr.    <fdrake at gmail.com>
"Chaos is the score upon which reality is written." --Henry Miller

From ziade.tarek at gmail.com  Thu Dec 27 19:28:05 2007
From: ziade.tarek at gmail.com (=?UTF-8?Q?Tarek_Ziad=C3=A9?=)
Date: Thu, 27 Dec 2007 10:28:05 -0800 (PST)
Subject: [Catalog-sig] permissive trove classification
In-Reply-To: <4773AFAF.8050506@v.loewis.de>
References: <14504481.post@talk.nabble.com> <4773AFAF.8050506@v.loewis.de>
Message-ID: <14516698.post@talk.nabble.com>




&quot;Martin v. L?wis&quot; wrote:
> 
>> I can work on a more formal document (some kind of PEP?) to explain the
>> changes needed in the current
>> PyPI implementation and on a formal definition of a PyPI (server side)
>> api
>> (a bit like the DB API). I am also willing to spend the time needed to
>> code
>> it.
> 
> Please do. I would suggest you put any design documents into
> wiki.python.org/moin, with links from
> http://wiki.python.org/moin/CheeseShopDev
> The actual patches to PyPI should to the SF tracker.
> If you can, please choose wiki names that don't list CheeseShop
> anymore; use PyPI instead.
> 

Ok I will write a doc this week then present it here, in order to propose a
patch

Regards
Tarek
-- 
View this message in context: http://www.nabble.com/permissive-trove-classification-tp14504481p14516698.html
Sent from the Python - catalog-sig mailing list archive at Nabble.com.


From doug at hellfly.net  Thu Dec 27 20:25:42 2007
From: doug at hellfly.net (Doug Hellmann)
Date: Thu, 27 Dec 2007 14:25:42 -0500
Subject: [Catalog-sig] permissive trove classification
In-Reply-To: <9cee7ab80712271022q73805833jd2318602cbf0ff37@mail.gmail.com>
References: <14504481.post@talk.nabble.com>
	<B1B7D499-D2F0-4C3B-9F0A-E9CBAF785B89@hellfly.net>
	<14504721.post@talk.nabble.com>
	<09EA102E-8B33-465C-9CDD-B3E71C2B586B@hellfly.net>
	<14511741.post@talk.nabble.com>
	<41B8C2E7-0F79-4D89-978B-37DB08754177@hellfly.net>
	<9cee7ab80712271022q73805833jd2318602cbf0ff37@mail.gmail.com>
Message-ID: <F5200C39-D01B-4D96-A263-CF14EC55371F@hellfly.net>


On Dec 27, 2007, at 1:22 PM, Fred Drake wrote:

> On Dec 27, 2007 7:57 AM, Doug Hellmann <doug at hellfly.net> wrote:
>> I would want an error, since the resulting
>> package would not show up in any categories at all.
>
> But the Trove classifiers are optional now, so I'm not at all sure it
> should be turned into an error.  Leaving it as a warning seems
> sufficient; someone who sees that the warning was caused by a typo
> after all can still go to the web form and edit the set of classifiers
> (or maybe re-register after correcting the metadata; I'm not sure if
> that'll work).
>
> Or are you proposing that the classifiers become required?  That's
> going to cause a lot of packages to require work before new versions
> can be released, which doesn't seem good to me.

Ah, I didn't realize they were optional.  It never occurred to me to  
try to post a package without any categories listed.  :-)

What I'm trying to do is make it easy to figure out when I've botched  
something in my configuration.  If there are no categories listed for  
a package I am uploading, or no *known* categories listed, that seems  
like it warrants a special message, even if the server warns me about  
each category I specify that it doesn't know.

But I won't push it.  As long as the server tells me about categories  
it doesn't recognize, I should be able to figure out if I've not  
given any valid categories at all, and that's good enough.

Doug


From fdrake at gmail.com  Fri Dec 28 05:22:27 2007
From: fdrake at gmail.com (Fred Drake)
Date: Thu, 27 Dec 2007 23:22:27 -0500
Subject: [Catalog-sig] permissive trove classification
In-Reply-To: <F5200C39-D01B-4D96-A263-CF14EC55371F@hellfly.net>
References: <14504481.post@talk.nabble.com>
	<B1B7D499-D2F0-4C3B-9F0A-E9CBAF785B89@hellfly.net>
	<14504721.post@talk.nabble.com>
	<09EA102E-8B33-465C-9CDD-B3E71C2B586B@hellfly.net>
	<14511741.post@talk.nabble.com>
	<41B8C2E7-0F79-4D89-978B-37DB08754177@hellfly.net>
	<9cee7ab80712271022q73805833jd2318602cbf0ff37@mail.gmail.com>
	<F5200C39-D01B-4D96-A263-CF14EC55371F@hellfly.net>
Message-ID: <9cee7ab80712272022l644b576at2669f15a198807d7@mail.gmail.com>

On Dec 27, 2007 2:25 PM, Doug Hellmann <doug at hellfly.net> wrote:
> What I'm trying to do is make it easy to figure out when I've botched
> something in my configuration.  If there are no categories listed for
> a package I am uploading, or no *known* categories listed, that seems
> like it warrants a special message, even if the server warns me about
> each category I specify that it doesn't know.

This suggests that your private PyPI-a-like might treat it as an error
to have unrecognized categories; that certainly supports the immediate
use case (1 public + 1 private repositories).  A more general solution
might be a bit different, of course.


  -Fred

-- 
Fred L. Drake, Jr.    <fdrake at gmail.com>
"Chaos is the score upon which reality is written." --Henry Miller

From richardjones at optushome.com.au  Fri Dec 28 23:45:13 2007
From: richardjones at optushome.com.au (Richard Jones)
Date: Sat, 29 Dec 2007 09:45:13 +1100
Subject: [Catalog-sig] Distribution of Pypi
In-Reply-To: <14434880.post@talk.nabble.com>
References: <14434880.post@talk.nabble.com>
Message-ID: <200712290945.13396.richardjones@optushome.com.au>

On Thu, 20 Dec 2007, Tarek Ziad? wrote:
> I would like to run my own cheeseshop for some project managment, is there
> any public release of the pypi package i can use, or trunk is my friend
> (https://svn.python.org/packages/trunk) ?
>
> What is its licence by the way ? Can't find it in the svn

I have no interest in exerting ownership or restrictive copying practises. I'd 
be happy for it to be in the public domain.

Anyone?


     Richard