From sanxiyn at gmail.com Fri Sep 1 06:41:57 2006 From: sanxiyn at gmail.com (Sanghyeon Seo) Date: Fri, 1 Sep 2006 13:41:57 +0900 Subject: [Catalog-sig] Table of Python Packages Message-ID: <5b0248170608312141x340acd52j387c45cb0242ef37@mail.gmail.com> Hello, c.l.py, and catalog-sig, This post updates last year's post: http://mail.python.org/pipermail/catalog-sig/2005-March/000506.html Believe it or not, I am still maintaining this table, and it can be now found here: http://sparcs.kaist.ac.kr/~tinuviel/package/list.cgi?name=python Now you can see version comparison between distributions: http://sparcs.kaist.ac.kr/~tinuviel/package/list.cgi?name=python&version=1 Version information is updated daily by an automated cron job. Now the table contains over 400 entries. If you have any suggestions or corrections, please mail me. Seo Sanghyeon From jim at zope.com Thu Sep 7 13:42:58 2006 From: jim at zope.com (Jim Fulton) Date: Thu, 7 Sep 2006 07:42:58 -0400 Subject: [Catalog-sig] What triggers treating long descriptions text as reST in PyPI? Message-ID: Most of my packages' long descriptions are treated as reST. For example: http://www.python.org/pypi/zc.recipe.testrunner However, for: http://www.python.org/pypi/zc.recipe.egg the long description was treated as plain text. What triggers treatment as reStructuredText? Is this documented anywhere? Jim -- Jim Fulton mailto:jim at zope.com Python Powered! CTO (540) 361-1714 http://www.python.org Zope Corporation http://www.zope.com http://www.zope.org From richardjones at optushome.com.au Thu Sep 7 14:51:52 2006 From: richardjones at optushome.com.au (Richard Jones) Date: Thu, 7 Sep 2006 22:51:52 +1000 Subject: [Catalog-sig] What triggers treating long descriptions text as reST in PyPI? In-Reply-To: References: Message-ID: <200609072251.52968.richardjones@optushome.com.au> On Thursday 07 September 2006 21:42, Jim Fulton wrote: > Most of my packages' long descriptions are treated as reST. For example: > > http://www.python.org/pypi/zc.recipe.testrunner > > However, for: > > http://www.python.org/pypi/zc.recipe.egg > > the long description was treated as plain text. > > What triggers treatment as reStructuredText? Is this documented > anywhere? If the reStructuredText parsing fails for some reason it'll be treated as plain text. The specific docutils settings used are: settings_overrides={ 'raw_enabled': '0', # no raw HTML code 'file_insertion_enabled': '0', # no file/URL access 'halt_level': 2, # at warnings or errors, raise an exception 'report_level': 5, # never report problems with the reST code } We pass the description through the docutils trim_docstring function (from docutils.readers.python.moduleparser) before parsing it. This dedents as appropriate. Richard From jim at zope.com Thu Sep 7 15:49:19 2006 From: jim at zope.com (Jim Fulton) Date: Thu, 7 Sep 2006 09:49:19 -0400 Subject: [Catalog-sig] What triggers treating long descriptions text as reST in PyPI? In-Reply-To: <200609072251.52968.richardjones@optushome.com.au> References: <200609072251.52968.richardjones@optushome.com.au> Message-ID: Yeah, Fred pointed out to me that reST barfed on my ise of the string "py_" in my text. :/ I should have thought to try processing the text myself. I'll do so the next time I get a failure to reST. Thanks. Jim On Sep 7, 2006, at 8:51 AM, Richard Jones wrote: > On Thursday 07 September 2006 21:42, Jim Fulton wrote: >> Most of my packages' long descriptions are treated as reST. For >> example: >> >> http://www.python.org/pypi/zc.recipe.testrunner >> >> However, for: >> >> http://www.python.org/pypi/zc.recipe.egg >> >> the long description was treated as plain text. >> >> What triggers treatment as reStructuredText? Is this documented >> anywhere? > > If the reStructuredText parsing fails for some reason it'll be > treated as > plain text. The specific docutils settings used are: > > settings_overrides={ > 'raw_enabled': '0', # no raw HTML code > 'file_insertion_enabled': '0', # no file/URL access > 'halt_level': 2, # at warnings or errors, raise an exception > 'report_level': 5, # never report problems with the reST code > } > > We pass the description through the docutils trim_docstring > function (from > docutils.readers.python.moduleparser) before parsing it. This > dedents as > appropriate. > > > Richard > _______________________________________________ > Catalog-sig mailing list > Catalog-sig at python.org > http://mail.python.org/mailman/listinfo/catalog-sig -- Jim Fulton mailto:jim at zope.com Python Powered! CTO (540) 361-1714 http://www.python.org Zope Corporation http://www.zope.com http://www.zope.org From jim at riversnake.com Thu Sep 14 13:38:40 2006 From: jim at riversnake.com (Jim Fulton) Date: Thu, 14 Sep 2006 07:38:40 -0400 Subject: [Catalog-sig] Framework classifiers Message-ID: <4191E0E4-CCC2-4102-85B2-5A5AD744A185@riversnake.com> Please define the following Trove classifiers: Framework :: Buildout Recipes and Extensions for zc.buildout Framework :: ZODB Packages that provide objects that can be stored in the ZODB or packages that provide ZODB extensions, such as storage implementations. Framework :: Zope2 Zope 2 add-on packages. Framework :: Zope3 Zope3 add-on packages, especially applications. This should be used for packages that are designed specifically for the Zope 3 application server. This classification should not be used for more general packages that happen to be used by or that can be used in Zope 3. It sure would be nice if PyPI stored and presented classifier descriptions. :) Jim From richardjones at optushome.com.au Fri Sep 15 00:32:15 2006 From: richardjones at optushome.com.au (Richard Jones) Date: Fri, 15 Sep 2006 08:32:15 +1000 Subject: [Catalog-sig] Framework classifiers In-Reply-To: <4191E0E4-CCC2-4102-85B2-5A5AD744A185@riversnake.com> References: <4191E0E4-CCC2-4102-85B2-5A5AD744A185@riversnake.com> Message-ID: <200609150832.15327.richardjones@optushome.com.au> On Thursday 14 September 2006 21:38, Jim Fulton wrote: > Please define the following Trove classifiers: > > Framework :: Buildout > Framework :: ZODB > Framework :: Zope2 > Framework :: Zope3 Done. > It sure would be nice if PyPI stored and presented classifier > descriptions. :) Yeah. Perhaps a wiki page linked from the tutorial would be a good start? Richard From fdrake at gmail.com Fri Sep 15 02:18:04 2006 From: fdrake at gmail.com (Fred Drake) Date: Thu, 14 Sep 2006 20:18:04 -0400 Subject: [Catalog-sig] Framework classifiers In-Reply-To: <200609150832.15327.richardjones@optushome.com.au> References: <4191E0E4-CCC2-4102-85B2-5A5AD744A185@riversnake.com> <200609150832.15327.richardjones@optushome.com.au> Message-ID: <9cee7ab80609141718p68ba2d4fof7dcc30128fa7fd8@mail.gmail.com> On 9/14/06, Richard Jones wrote: > Yeah. Perhaps a wiki page linked from the tutorial would be a good start? +1 That should be much better than the current situation. -Fred -- Fred L. Drake, Jr. "Every sin is the result of a collaboration." --Lucius Annaeus Seneca From jim at zope.com Fri Sep 15 12:52:50 2006 From: jim at zope.com (Jim Fulton) Date: Fri, 15 Sep 2006 06:52:50 -0400 Subject: [Catalog-sig] Framework classifiers In-Reply-To: <200609150832.15327.richardjones@optushome.com.au> References: <4191E0E4-CCC2-4102-85B2-5A5AD744A185@riversnake.com> <200609150832.15327.richardjones@optushome.com.au> Message-ID: On Sep 14, 2006, at 6:32 PM, Richard Jones wrote: > On Thursday 14 September 2006 21:38, Jim Fulton wrote: >> Please define the following Trove classifiers: >> >> Framework :: Buildout >> Framework :: ZODB >> Framework :: Zope2 >> Framework :: Zope3 > > Done. Thanks. >> It sure would be nice if PyPI stored and presented classifier >> descriptions. :) > > Yeah. Perhaps a wiki page linked from the tutorial would be a good > start? Yup. Could it also be linked from: http://www.python.org/pypi?%3Aaction=list_classifiers ? Jim -- Jim Fulton mailto:jim at zope.com Python Powered! CTO (540) 361-1714 http://www.python.org Zope Corporation http://www.zope.com http://www.zope.org From richardjones at optushome.com.au Fri Sep 15 13:28:28 2006 From: richardjones at optushome.com.au (Richard Jones) Date: Fri, 15 Sep 2006 21:28:28 +1000 Subject: [Catalog-sig] Framework classifiers In-Reply-To: References: <4191E0E4-CCC2-4102-85B2-5A5AD744A185@riversnake.com> <200609150832.15327.richardjones@optushome.com.au> Message-ID: <200609152128.28701.richardjones@optushome.com.au> On Friday 15 September 2006 20:52, Jim Fulton wrote: > Could it also be linked from: > http://www.python.org/pypi?%3Aaction=list_classifiers > ? I guess the problem is that that page is intended to be a plain-text listing of the classifiers. Richard From jim at zope.com Fri Sep 15 15:38:04 2006 From: jim at zope.com (Jim Fulton) Date: Fri, 15 Sep 2006 09:38:04 -0400 Subject: [Catalog-sig] Framework classifiers In-Reply-To: <200609152128.28701.richardjones@optushome.com.au> References: <4191E0E4-CCC2-4102-85B2-5A5AD744A185@riversnake.com> <200609150832.15327.richardjones@optushome.com.au> <200609152128.28701.richardjones@optushome.com.au> Message-ID: <225C8ADE-D97F-4399-9399-A3F2E3410FC6@zope.com> On Sep 15, 2006, at 7:28 AM, Richard Jones wrote: > On Friday 15 September 2006 20:52, Jim Fulton wrote: >> Could it also be linked from: >> http://www.python.org/pypi?%3Aaction=list_classifiers >> ? > > I guess the problem is that that page is intended to be a plain- > text listing > of the classifiers. OK. I assume that is because it is read by some automated processes. Jim -- Jim Fulton mailto:jim at zope.com Python Powered! CTO (540) 361-1714 http://www.python.org Zope Corporation http://www.zope.com http://www.zope.org From richardjones at optushome.com.au Mon Sep 18 01:44:53 2006 From: richardjones at optushome.com.au (Richard Jones) Date: Mon, 18 Sep 2006 09:44:53 +1000 Subject: [Catalog-sig] Framework classifiers In-Reply-To: <225C8ADE-D97F-4399-9399-A3F2E3410FC6@zope.com> References: <4191E0E4-CCC2-4102-85B2-5A5AD744A185@riversnake.com> <200609152128.28701.richardjones@optushome.com.au> <225C8ADE-D97F-4399-9399-A3F2E3410FC6@zope.com> Message-ID: <200609180944.53772.richardjones@optushome.com.au> On Friday 15 September 2006 23:38, Jim Fulton wrote: > On Sep 15, 2006, at 7:28 AM, Richard Jones wrote: > > On Friday 15 September 2006 20:52, Jim Fulton wrote: > >> Could it also be linked from: > >> http://www.python.org/pypi?%3Aaction=list_classifiers > >> ? > > > > I guess the problem is that that page is intended to be a plain- > > text listing > > of the classifiers. > > OK. I assume that is because it is read by some automated processes. That was always the intention. Whether anyone is actually *doing* this I couldn't say, but as I've already discovered I can't change the web interface these days without someone coming out of the woodwork and yelling at me :) Richard From jim at zope.com Mon Sep 18 16:13:05 2006 From: jim at zope.com (Jim Fulton) Date: Mon, 18 Sep 2006 10:13:05 -0400 Subject: [Catalog-sig] Framework classifiers In-Reply-To: <200609180944.53772.richardjones@optushome.com.au> References: <4191E0E4-CCC2-4102-85B2-5A5AD744A185@riversnake.com> <200609152128.28701.richardjones@optushome.com.au> <225C8ADE-D97F-4399-9399-A3F2E3410FC6@zope.com> <200609180944.53772.richardjones@optushome.com.au> Message-ID: <83E269E7-7A94-44A7-8BED-6A46F1E6B101@zope.com> On Sep 17, 2006, at 7:44 PM, Richard Jones wrote: > On Friday 15 September 2006 23:38, Jim Fulton wrote: >> On Sep 15, 2006, at 7:28 AM, Richard Jones wrote: >>> On Friday 15 September 2006 20:52, Jim Fulton wrote: >>>> Could it also be linked from: >>>> http://www.python.org/pypi?%3Aaction=list_classifiers >>>> ? >>> >>> I guess the problem is that that page is intended to be a plain- >>> text listing >>> of the classifiers. >> >> OK. I assume that is because it is read by some automated processes. > > That was always the intention. Whether anyone is actually *doing* > this I > couldn't say, but as I've already discovered I can't change the web > interface > these days without someone coming out of the woodwork and yelling > at me :) Perhaps we should reserve that page for the current output -- just in case, but create a new page aimed at humans that has the classifiers with descriptions and link to that page from the cheese shop navigation. Jim -- Jim Fulton mailto:jim at zope.com Python Powered! CTO (540) 361-1714 http://www.python.org Zope Corporation http://www.zope.com http://www.zope.org From richardjones at optushome.com.au Mon Sep 18 23:50:48 2006 From: richardjones at optushome.com.au (Richard Jones) Date: Tue, 19 Sep 2006 07:50:48 +1000 Subject: [Catalog-sig] Framework classifiers In-Reply-To: <83E269E7-7A94-44A7-8BED-6A46F1E6B101@zope.com> References: <4191E0E4-CCC2-4102-85B2-5A5AD744A185@riversnake.com> <200609180944.53772.richardjones@optushome.com.au> <83E269E7-7A94-44A7-8BED-6A46F1E6B101@zope.com> Message-ID: <200609190750.48942.richardjones@optushome.com.au> On Tuesday 19 September 2006 00:13, Jim Fulton wrote: > Perhaps we should reserve that page for the current output -- just in > case, but create a new page aimed at humans that has the classifiers with > descriptions and link to that page from the cheese shop navigation. Indeed - this is where my suggestion for a wiki page comes in. Richard From rokkamraja at gmail.com Fri Sep 22 15:17:39 2006 From: rokkamraja at gmail.com (Raja Rokkam) Date: Fri, 22 Sep 2006 18:47:39 +0530 Subject: [Catalog-sig] Python Network Programming Message-ID: <357297a00609220617q1e4ecfe4v32f286459945eaf5@mail.gmail.com> Hi, I am currently doing my final year project "Secure mobile Robot Management" . I have done the theoretical aspects of it till now and now thinking of coding it . I would like to code in Python , but i am new to Python Network Programming . Some of features of my project are: 1. Each robot can send data to any other robot. 2. Each robot can receive data from any other robot. 3. Every Robot has atleast 1 other bot in its communication range. 4. maximum size of a data packet is limited to 35 bytes 5. each mobile robot maintains a table with routes 6. all the routes stored in the routing table include a ??eld named life-time. 7. Route Discovery Process initiated if there is no known route to other bot. 8. There is no server over here . 9. every bot should be able to process the data from other bots and both multicast/unicast need to be supported. Assume the environment is gridded mesh and bots exploring the area. They need to perform a set of tasks (assume finding some locations which are dangerous or smthing like that). My main concern is how to go about modifying the headers such that everything fits in 35bytes . I would like to know how to proceed and if any links or resources in this regard. How to modify the headers ? ie. all in 35 bytes . Thank You, Raja. -------------- next part -------------- An HTML attachment was scrubbed... URL: http://mail.python.org/pipermail/catalog-sig/attachments/20060922/73d34391/attachment.html From ufs at ufsoft.org Mon Sep 18 04:11:11 2006 From: ufs at ufsoft.org (Pedro Algarvio) Date: Mon, 18 Sep 2006 03:11:11 +0100 Subject: [Catalog-sig] Framework :: Trac :: Plugins category Message-ID: <20060918031111.94burgihtwoww8gs@horde.ufsoft.org> Could you please add yet another category(ies)? Framework :: Trac Framework :: Trac :: Plugins The last one is the one I'd like to use. Trac can be found here: http://trac.edgewall.org/ Thank you, -- Pedro Algarvio __ ___ ___ _______ ___ __ | Y .' _| _ .-----.' _| |_ .-----.----.-----. |. | | _| 1___| _ | _| _|__| _ | _| _ | |. | |__| |____ |_____|__| |____|__|_____|__| |___ | |: 1 | |: 1 | |_____| |::.. . | |::.. . | ufs [AT] ufsoft [DOT] org `-------' `-------' ufs [AT] sapo [DOT] pt From richardjones at optushome.com.au Sun Sep 24 23:09:35 2006 From: richardjones at optushome.com.au (Richard Jones) Date: Mon, 25 Sep 2006 07:09:35 +1000 Subject: [Catalog-sig] Framework :: Trac :: Plugins category In-Reply-To: <20060918031111.94burgihtwoww8gs@horde.ufsoft.org> References: <20060918031111.94burgihtwoww8gs@horde.ufsoft.org> Message-ID: <200609250709.35151.richardjones@optushome.com.au> On Monday 18 September 2006 12:11, Pedro Algarvio wrote: > Could you please add yet another category(ies)? > Framework :: Trac > Framework :: Trac :: Plugins > > The last one is the one I'd like to use. Why two classifiers? What distinguishes something classifying itself as "Framework :: Trac" from something classifying itself "Framework :: Trac :: Plugins"? At this point I would create the former, but not the latter. Richard From fdrake at gmail.com Mon Sep 25 03:35:59 2006 From: fdrake at gmail.com (Fred Drake) Date: Sun, 24 Sep 2006 21:35:59 -0400 Subject: [Catalog-sig] Framework :: Trac :: Plugins category In-Reply-To: <200609250709.35151.richardjones@optushome.com.au> References: <20060918031111.94burgihtwoww8gs@horde.ufsoft.org> <200609250709.35151.richardjones@optushome.com.au> Message-ID: <9cee7ab80609241835y7a53d232y7e73bad43f147fb2@mail.gmail.com> On 9/24/06, Richard Jones wrote: > Why two classifiers? What distinguishes something classifying itself > as "Framework :: Trac" from something classifying itself "Framework :: > Trac :: Plugins"? At this point I would create the former, but not the > latter. Agreed. Trac itself is a framework; users of the framework can look for plugins using the framework classifier. There's no need to create a classifier for the framework alone. (Now, it's fine to classify the framework as Framework::Trac, but the plugins should be in the same classification. That way a user finds both plugins and updates all together, which makes a lot of sense to me.) -Fred -- Fred L. Drake, Jr. "Every sin is the result of a collaboration." --Lucius Annaeus Seneca From richardjones at optushome.com.au Mon Sep 25 08:46:34 2006 From: richardjones at optushome.com.au (Richard Jones) Date: Mon, 25 Sep 2006 16:46:34 +1000 Subject: [Catalog-sig] Framework :: Trac :: Plugins category In-Reply-To: <9cee7ab80609241835y7a53d232y7e73bad43f147fb2@mail.gmail.com> References: <20060918031111.94burgihtwoww8gs@horde.ufsoft.org> <200609250709.35151.richardjones@optushome.com.au> <9cee7ab80609241835y7a53d232y7e73bad43f147fb2@mail.gmail.com> Message-ID: <200609251646.35098.richardjones@optushome.com.au> On Monday 25 September 2006 11:35, Fred Drake wrote: > On 9/24/06, Richard Jones wrote: > > Why two classifiers? What distinguishes something classifying itself > > as "Framework :: Trac" from something classifying itself "Framework :: > > Trac :: Plugins"? At this point I would create the former, but not the > > latter. > > Agreed. Trac itself is a framework; users of the framework can look > for plugins using the framework classifier. There's no need to create > a classifier for the framework alone. I'm certainly not creating a new Trove category for every framework that comes along :) I've added "Framework :: Trac" Richard From ianb at colorstudy.com Mon Sep 25 17:51:06 2006 From: ianb at colorstudy.com (Ian Bicking) Date: Mon, 25 Sep 2006 10:51:06 -0500 Subject: [Catalog-sig] Cheese shop: search Message-ID: <4517FAEA.3010801@colorstudy.com> Can we please get the search back? I really really hate Google search. For instance, I know there's a package with "wsgi" and "xml" in the name (I later guess that the name is actually just wsgixml, but name guessing is silly). This is what I get: http://www.google.com/search?sitesearch=cheeseshop.python.org&sitesearch=cheeseshop.python.org&sourceid=google-search&q=wsgi+xml&submit=search It's utterly and completely useless. It's all stupid browse pages. Alternately, it could be improved by putting in hints to Google not to index any of the browse pages. The browse pages are really the problem. But I'd prefer just putting the old search page back in. Though Page Rank is not actually useful, and the packages Google does find are totally wrong. Google also has references to old/hidden packages, and doesn't update nearly enough to be useful. Actually, looking through all 8 pages wsgixml doesn't even show up. Totally useless. Maybe Google would index more properly given a sitemap. -- Ian Bicking | ianb at colorstudy.com | http://blog.ianbicking.org From bob at redivi.com Mon Sep 25 22:44:41 2006 From: bob at redivi.com (Bob Ippolito) Date: Mon, 25 Sep 2006 13:44:41 -0700 Subject: [Catalog-sig] CheeseShop upload broken? Message-ID: <6a36e7290609251344tad9a0b3l2dbefee22227502f@mail.gmail.com> I'm having problems uploading to CheeseShop via setuptools. This is using the following checkout and incantations on Mac OS X 10.4 w/ Python 2.4.3: $ svn co http://svn.pythonmac.org/bdist_mpkg/bdist_mpkg/tags/bdist_mpkg-0.4.2 $ cd bdist_mpkg-0.4.2 $ python setup.py egg_info -RDb '' register bdist_egg sdist upload -s .... Submitting dist/bdist_mpkg-0.4.2-py2.4.egg to http://www.python.org/pypi Upload failed (400): Bad Request -bob From pje at telecommunity.com Mon Sep 25 22:53:06 2006 From: pje at telecommunity.com (Phillip J. Eby) Date: Mon, 25 Sep 2006 16:53:06 -0400 Subject: [Catalog-sig] CheeseShop upload broken? In-Reply-To: <6a36e7290609251344tad9a0b3l2dbefee22227502f@mail.gmail.com > Message-ID: <5.1.1.6.0.20060925165211.02cea358@sparrow.telecommunity.com> At 01:44 PM 9/25/2006 -0700, Bob Ippolito wrote: >I'm having problems uploading to CheeseShop via setuptools. > >This is using the following checkout and incantations on Mac OS X 10.4 >w/ Python 2.4.3: > >$ svn co http://svn.pythonmac.org/bdist_mpkg/bdist_mpkg/tags/bdist_mpkg-0.4.2 >$ cd bdist_mpkg-0.4.2 >$ python setup.py egg_info -RDb '' register bdist_egg sdist upload -s >.... >Submitting dist/bdist_mpkg-0.4.2-py2.4.egg to http://www.python.org/pypi >Upload failed (400): Bad Request You'll get that error if you already have a file with that name uploaded (and you do). Delete it from the Cheeseshop management interface first. From bob at redivi.com Mon Sep 25 23:01:31 2006 From: bob at redivi.com (Bob Ippolito) Date: Mon, 25 Sep 2006 14:01:31 -0700 Subject: [Catalog-sig] CheeseShop upload broken? In-Reply-To: <5.1.1.6.0.20060925165211.02cea358@sparrow.telecommunity.com> References: <5.1.1.6.0.20060925165211.02cea358@sparrow.telecommunity.com> Message-ID: <6a36e7290609251401n72280e1bk1a659be21db70de0@mail.gmail.com> On 9/25/06, Phillip J. Eby wrote: > At 01:44 PM 9/25/2006 -0700, Bob Ippolito wrote: > >I'm having problems uploading to CheeseShop via setuptools. > > > >This is using the following checkout and incantations on Mac OS X 10.4 > >w/ Python 2.4.3: > > > >$ svn co http://svn.pythonmac.org/bdist_mpkg/bdist_mpkg/tags/bdist_mpkg-0.4.2 > >$ cd bdist_mpkg-0.4.2 > >$ python setup.py egg_info -RDb '' register bdist_egg sdist upload -s > >.... > >Submitting dist/bdist_mpkg-0.4.2-py2.4.egg to http://www.python.org/pypi > >Upload failed (400): Bad Request > > You'll get that error if you already have a file with that name uploaded > (and you do). Delete it from the Cheeseshop management interface first. That was it, thanks. -bob