From mike_mp at zzzcomputing.com Tue Oct 2 01:31:24 2012 From: mike_mp at zzzcomputing.com (Michael Bayer) Date: Mon, 1 Oct 2012 19:31:24 -0400 Subject: [Catalog-sig] critical pypi registration issue Message-ID: <695A709A-4D26-4C9E-83CA-EFD3E280BEC7@zzzcomputing.com> Hi all - I was asked to draw attention to this sourceforge issue, detailing a blocking 500 error that is preventing me from releasing SQLAlchemy 0.7.9: https://sourceforge.net/tracker/index.php?func=detail&aid=3573564&group_id=66150&atid=513503 if anyone has insight on this issue, let me know. Thanks ! - mike From richard at python.org Tue Oct 2 02:47:44 2012 From: richard at python.org (Richard Jones) Date: Tue, 2 Oct 2012 10:47:44 +1000 Subject: [Catalog-sig] critical pypi registration issue In-Reply-To: <695A709A-4D26-4C9E-83CA-EFD3E280BEC7@zzzcomputing.com> References: <695A709A-4D26-4C9E-83CA-EFD3E280BEC7@zzzcomputing.com> Message-ID: On 2 October 2012 09:31, Michael Bayer wrote: > I was asked to draw attention to this sourceforge issue, detailing a blocking 500 error that is preventing me from releasing SQLAlchemy 0.7.9: > > https://sourceforge.net/tracker/index.php?func=detail&aid=3573564&group_id=66150&atid=513503 > > if anyone has insight on this issue, let me know. Thanks ! I've fixed the problem. It was related to my recent switch to using the new distutils2 version comparison code over the older distutils code: >>> from distutils.version import LooseVersion as V >>> sorted([V('1.0'), V('1.0a1'), V('1.1'), V('1.1rc1')]) [LooseVersion ('1.0'), LooseVersion ('1.0a1'), LooseVersion ('1.1'), LooseVersion ('1.1rc1')] >>> from distutils2.version import NormalizedVersion as V >>> sorted([V('1.0'), V('1.0a1'), V('1.1'), V('1.1rc1')]) [NormalizedVersion('1.0a1'), NormalizedVersion('1.0'), NormalizedVersion('1.1rc1'), NormalizedVersion('1.1')] Anyhoo, it seems there's a bug in the handling of versions including "post" like "1.0.1.post1" where the str()ification of the NormalizedVersion would add on an extra ".z" on the end (a by-product of the sorting mechanism.) I modified PyPI to work around the problem, and have now also filed a bug against distutils2 with a patch implementing a test and fix for the problem. Richard From doug.hellmann at gmail.com Fri Oct 12 12:55:13 2012 From: doug.hellmann at gmail.com (Doug Hellmann) Date: Fri, 12 Oct 2012 06:55:13 -0400 Subject: [Catalog-sig] please add trove classifier for OpenStack Message-ID: There are several official and peripheral OpenStack projects that would like to be registered on PyPI. Could we get a new classifier to help users find the packages? I think something like "Framework :: OpenStack" would make sense, but am open to other suggestions. Thanks! Doug From martin at v.loewis.de Fri Oct 12 16:45:10 2012 From: martin at v.loewis.de (=?ISO-8859-1?Q?=22Martin_v=2E_L=F6wis=22?=) Date: Fri, 12 Oct 2012 16:45:10 +0200 Subject: [Catalog-sig] please add trove classifier for OpenStack In-Reply-To: References: Message-ID: <50782CF6.6000509@v.loewis.de> Am 12.10.12 12:55, schrieb Doug Hellmann: > There are several official and peripheral OpenStack projects that > would like to be registered on PyPI. Could we get a new classifier to > help users find the packages? I think something like "Framework :: > OpenStack" would make sense, but am open to other suggestions. What packages are these specifically? Preferably, I'd like to learn about packages that are already registered at this very point. Regards, Martin From doug.hellmann at gmail.com Sat Oct 13 12:32:00 2012 From: doug.hellmann at gmail.com (Doug Hellmann) Date: Sat, 13 Oct 2012 06:32:00 -0400 Subject: [Catalog-sig] please add trove classifier for OpenStack In-Reply-To: <50782CF6.6000509@v.loewis.de> References: <50782CF6.6000509@v.loewis.de> Message-ID: <35066577-96D6-4747-A2BB-D1CEE9C7DC30@gmail.com> On Oct 12, 2012, at 10:45 AM, Martin v. L?wis wrote: > Am 12.10.12 12:55, schrieb Doug Hellmann: >> There are several official and peripheral OpenStack projects that >> would like to be registered on PyPI. Could we get a new classifier to >> help users find the packages? I think something like "Framework :: >> OpenStack" would make sense, but am open to other suggestions. > > What packages are these specifically? Preferably, I'd like to learn > about packages that are already registered at this very point. In addition to some packages we are preparing for imminent release, there are several client libraries (python-quantumclient, python-novaclient, etc.). I found a good number via a text search (http://pypi.python.org/pypi?%3Aaction=search&term=openstack&submit=search). There is also a project within OpenStack to pull out some of the code common to the various federated projects to make it easier to share, and I anticipate those libraries being listed on PyPI and tagged with this new classifier as well. Doug From doug.hellmann at gmail.com Mon Oct 15 16:05:36 2012 From: doug.hellmann at gmail.com (Doug Hellmann) Date: Mon, 15 Oct 2012 07:05:36 -0700 Subject: [Catalog-sig] please add trove classifier for OpenStack In-Reply-To: <35066577-96D6-4747-A2BB-D1CEE9C7DC30@gmail.com> References: <50782CF6.6000509@v.loewis.de> <35066577-96D6-4747-A2BB-D1CEE9C7DC30@gmail.com> Message-ID: Ping? On Oct 13, 2012, at 3:32 AM, Doug Hellmann wrote: > > On Oct 12, 2012, at 10:45 AM, Martin v. L?wis wrote: > >> Am 12.10.12 12:55, schrieb Doug Hellmann: >>> There are several official and peripheral OpenStack projects that >>> would like to be registered on PyPI. Could we get a new classifier to >>> help users find the packages? I think something like "Framework :: >>> OpenStack" would make sense, but am open to other suggestions. >> >> What packages are these specifically? Preferably, I'd like to learn >> about packages that are already registered at this very point. > > In addition to some packages we are preparing for imminent release, there are several client libraries (python-quantumclient, python-novaclient, etc.). I found a good number via a text search (http://pypi.python.org/pypi?%3Aaction=search&term=openstack&submit=search). There is also a project within OpenStack to pull out some of the code common to the various federated projects to make it easier to share, and I anticipate those libraries being listed on PyPI and tagged with this new classifier as well. > > Doug > From martin at v.loewis.de Mon Oct 15 17:51:20 2012 From: martin at v.loewis.de (=?ISO-8859-1?Q?=22Martin_v=2E_L=F6wis=22?=) Date: Mon, 15 Oct 2012 17:51:20 +0200 Subject: [Catalog-sig] please add trove classifier for OpenStack In-Reply-To: <35066577-96D6-4747-A2BB-D1CEE9C7DC30@gmail.com> References: <50782CF6.6000509@v.loewis.de> <35066577-96D6-4747-A2BB-D1CEE9C7DC30@gmail.com> Message-ID: <507C30F8.2020906@v.loewis.de> Am 13.10.12 12:32, schrieb Doug Hellmann: > >> What packages are these specifically? Preferably, I'd like to >> learn about packages that are already registered at this very >> point. > > In addition to some packages we are preparing for imminent release, > there are several client libraries (python-quantumclient, > python-novaclient, etc.). I found a good number via a text search > (http://pypi.python.org/pypi?%3Aaction=search&term=openstack&submit=search). > There is also a project within OpenStack to pull out some of the code > common to the various federated projects to make it easier to share, > and I anticipate those libraries being listed on PyPI and tagged with > this new classifier as well. I see. ISTM that OpenStack isn't really a framework for many of these packages, in the sense of http://en.wikipedia.org/wiki/Software_framework (i.e. software that can be plugged into to create applications); instead, many of the Python libraries seem to use OpenStack in a client-server manner. If the purpose is primarily to find OpenStack-related code, Environment::OpenStack or Topic::Internet::OpenStack might be more appropriate. OTOH, I know next to nothing about OpenStack, so a second opinion from an expert would be appreciated. Regards, Martin From doug.hellmann at gmail.com Mon Oct 15 23:18:25 2012 From: doug.hellmann at gmail.com (Doug Hellmann) Date: Mon, 15 Oct 2012 14:18:25 -0700 Subject: [Catalog-sig] please add trove classifier for OpenStack In-Reply-To: <507C30F8.2020906@v.loewis.de> References: <50782CF6.6000509@v.loewis.de> <35066577-96D6-4747-A2BB-D1CEE9C7DC30@gmail.com> <507C30F8.2020906@v.loewis.de> Message-ID: <80DE8A60-6B34-4F23-90A7-756F7F3FC027@gmail.com> On Oct 15, 2012, at 8:51 AM, Martin v. L?wis wrote: > Am 13.10.12 12:32, schrieb Doug Hellmann: >> >>> What packages are these specifically? Preferably, I'd like to >>> learn about packages that are already registered at this very >>> point. >> >> In addition to some packages we are preparing for imminent release, >> there are several client libraries (python-quantumclient, >> python-novaclient, etc.). I found a good number via a text search >> (http://pypi.python.org/pypi?%3Aaction=search&term=openstack&submit=search). >> There is also a project within OpenStack to pull out some of the code >> common to the various federated projects to make it easier to share, >> and I anticipate those libraries being listed on PyPI and tagged with >> this new classifier as well. > > I see. ISTM that OpenStack isn't really a framework for many of these > packages, in the sense of > > http://en.wikipedia.org/wiki/Software_framework > > (i.e. software that can be plugged into to create applications); instead, many of the Python libraries seem to use OpenStack in > a client-server manner. Hmm, yes, you could be right. > If the purpose is primarily to find OpenStack-related code, > Environment::OpenStack or Topic::Internet::OpenStack might be > more appropriate. OTOH, I know next to nothing about OpenStack, > so a second opinion from an expert would be appreciated. I like "Environment::OpenStack" for the clients, and it could work for the other pieces, too. I'll ask around a bit and see what others have to say. Doug From aakash at learnstreet.com Tue Oct 16 23:13:34 2012 From: aakash at learnstreet.com (Aakash Prasad) Date: Tue, 16 Oct 2012 14:13:34 -0700 Subject: [Catalog-sig] LearnStreet's Free Online Python Course Message-ID: Hi all, I'd like to tell you about a free online Python course that my startup, LearnStreet (http://www.learnstreet.com), has recently launched (along with courses on JavaScript and Ruby). Our courses are designed for beginners and are fun, engaging and interactive through the use of multiple learning modalities. How is LearnStreet different from other learn-to-code sites you ask? UI/UX: A key aspect of LearnStreet?s courses is its distinct UI/UX. In order to see this, start any one of our courses. Multi-modal: Our courses are designed for beginners, and we have multiple ways to help them learn, including live chat, Twitter, Q&A, hints, videos and background material. http://www.learnstreet.com/lessons/languages/python Code Garage: Like many of you here, if you already know how to code, check out Code Garage where you can try your hand at cool coding projects like building a Mastermind game or a Sudoku Solver. http://www.learnstreet.com/cg/simple/projects/javascript Dev Tools: We?ve culled the web to provide some key resources beyond the core programming language that will help beginners gain a better understanding of what it takes to become a competent coder. http://www.learnstreet.com/dev_tools/ We just launched about a couple of weeks ago and would love to get your thoughts and feedback. We are looking for expert coders to help build out our other courses so check out the Contribute section on our site as well. Thanks Aakash -------------- next part -------------- An HTML attachment was scrubbed... URL: From doug.hellmann at gmail.com Wed Oct 17 14:07:55 2012 From: doug.hellmann at gmail.com (Doug Hellmann) Date: Wed, 17 Oct 2012 05:07:55 -0700 Subject: [Catalog-sig] please add trove classifier for OpenStack In-Reply-To: <80DE8A60-6B34-4F23-90A7-756F7F3FC027@gmail.com> References: <50782CF6.6000509@v.loewis.de> <35066577-96D6-4747-A2BB-D1CEE9C7DC30@gmail.com> <507C30F8.2020906@v.loewis.de> <80DE8A60-6B34-4F23-90A7-756F7F3FC027@gmail.com> Message-ID: On Oct 15, 2012, at 2:18 PM, Doug Hellmann wrote: > > On Oct 15, 2012, at 8:51 AM, Martin v. L?wis wrote: > >> Am 13.10.12 12:32, schrieb Doug Hellmann: >>> >>>> What packages are these specifically? Preferably, I'd like to >>>> learn about packages that are already registered at this very >>>> point. >>> >>> In addition to some packages we are preparing for imminent release, >>> there are several client libraries (python-quantumclient, >>> python-novaclient, etc.). I found a good number via a text search >>> (http://pypi.python.org/pypi?%3Aaction=search&term=openstack&submit=search). >>> There is also a project within OpenStack to pull out some of the code >>> common to the various federated projects to make it easier to share, >>> and I anticipate those libraries being listed on PyPI and tagged with >>> this new classifier as well. >> >> I see. ISTM that OpenStack isn't really a framework for many of these >> packages, in the sense of >> >> http://en.wikipedia.org/wiki/Software_framework >> >> (i.e. software that can be plugged into to create applications); instead, many of the Python libraries seem to use OpenStack in >> a client-server manner. > > Hmm, yes, you could be right. > >> If the purpose is primarily to find OpenStack-related code, >> Environment::OpenStack or Topic::Internet::OpenStack might be >> more appropriate. OTOH, I know next to nothing about OpenStack, >> so a second opinion from an expert would be appreciated. > > I like "Environment::OpenStack" for the clients, and it could work for the other pieces, too. I'll ask around a bit and see what others have to say. I've talked to a few of the leaders on the infrastructure team for the project and they agree that "Environment::OpenStack" makes the most sense for a broader range of packages, so we would like to use that. Thanks, Doug From dholth at gmail.com Wed Oct 17 15:21:45 2012 From: dholth at gmail.com (Daniel Holth) Date: Wed, 17 Oct 2012 09:21:45 -0400 Subject: [Catalog-sig] what is _pypi_ordering? Message-ID: In the JSON API to pypi, what is _pypi_ordering? Is this really the API documentation? http://wiki.python.org/moin/PyPiJson From jacob at jacobian.org Wed Oct 17 20:57:00 2012 From: jacob at jacobian.org (Jacob Kaplan-Moss) Date: Wed, 17 Oct 2012 13:57:00 -0500 Subject: [Catalog-sig] Getting in touch with the owner of the "Django096" package Message-ID: Hey folks -- Can anyone help and put me in touch with "regua", the owner of http://pypi.python.org/pypi/Django096? I need to have a quick conversation with him about what's going on there. Thanks, Jacob From richard at python.org Thu Oct 18 00:57:54 2012 From: richard at python.org (Richard Jones) Date: Thu, 18 Oct 2012 09:57:54 +1100 Subject: [Catalog-sig] what is _pypi_ordering? In-Reply-To: References: Message-ID: On 18 October 2012 00:21, Daniel Holth wrote: > In the JSON API to pypi, what is _pypi_ordering? It's an internal value that's unintentionally leaked out (it's the computed ordering of release versions.) > Is this really the API documentation? http://wiki.python.org/moin/PyPiJson Yes. Apart from the above entry which shouldn't be there, is there additional explanation you'd like to see? Richard From richard at python.org Thu Oct 18 01:02:05 2012 From: richard at python.org (Richard Jones) Date: Thu, 18 Oct 2012 10:02:05 +1100 Subject: [Catalog-sig] please add trove classifier for OpenStack In-Reply-To: References: <50782CF6.6000509@v.loewis.de> <35066577-96D6-4747-A2BB-D1CEE9C7DC30@gmail.com> <507C30F8.2020906@v.loewis.de> <80DE8A60-6B34-4F23-90A7-756F7F3FC027@gmail.com> Message-ID: On 17 October 2012 23:07, Doug Hellmann wrote: > On Oct 15, 2012, at 2:18 PM, Doug Hellmann wrote: >> I like "Environment::OpenStack" for the clients, and it could work for the other pieces, too. I'll ask around a bit and see what others have to say. > > I've talked to a few of the leaders on the infrastructure team for the project and they agree that "Environment::OpenStack" makes the most sense for a broader range of packages, so we would like to use that. Great! It's added. Richard From dholth at gmail.com Thu Oct 18 01:10:30 2012 From: dholth at gmail.com (Daniel Holth) Date: Wed, 17 Oct 2012 19:10:30 -0400 Subject: [Catalog-sig] what is _pypi_ordering? In-Reply-To: References: Message-ID: It looks like /name/json and /name/1.0/json is the entire json api? Can pypi compute the newest final release for me this way? On Oct 17, 2012 6:57 PM, "Richard Jones" wrote: > On 18 October 2012 00:21, Daniel Holth wrote: > > In the JSON API to pypi, what is _pypi_ordering? > > It's an internal value that's unintentionally leaked out (it's the > computed ordering of release versions.) > > > > Is this really the API documentation? > http://wiki.python.org/moin/PyPiJson > > Yes. Apart from the above entry which shouldn't be there, is there > additional explanation you'd like to see? > > > Richard > -------------- next part -------------- An HTML attachment was scrubbed... URL: From richard at python.org Thu Oct 18 02:13:34 2012 From: richard at python.org (Richard Jones) Date: Thu, 18 Oct 2012 11:13:34 +1100 Subject: [Catalog-sig] what is _pypi_ordering? In-Reply-To: References: Message-ID: On 18 October 2012 10:10, Daniel Holth wrote: > It looks like /name/json and /name/1.0/json is the entire json api? Yep. It was added as a mechanism for Javascript applications to embed release information in websites. The XML-RPC interface is much more fully-featured. > Can pypi compute the newest final release for me this way? That is what /name/json does - it orders releases using the PEP 386 rules (falling back on the old distutils rules where packages are not compliant) and gives you the latest release based on that. I've added some clarification regarding this to the doc page. Richard From doug.hellmann at gmail.com Thu Oct 18 15:28:16 2012 From: doug.hellmann at gmail.com (Doug Hellmann) Date: Thu, 18 Oct 2012 06:28:16 -0700 Subject: [Catalog-sig] please add trove classifier for OpenStack In-Reply-To: References: <50782CF6.6000509@v.loewis.de> <35066577-96D6-4747-A2BB-D1CEE9C7DC30@gmail.com> <507C30F8.2020906@v.loewis.de> <80DE8A60-6B34-4F23-90A7-756F7F3FC027@gmail.com> Message-ID: <3AB5CE25-E0BB-4A34-B101-CFCD5DFF1D5D@gmail.com> Thanks, guys! I tested it with a couple of our packages this morning and it's working great. I'll let the infrastructure team know so they can spread the word to the rest of our projects. Doug On Oct 17, 2012, at 4:02 PM, Richard Jones wrote: > On 17 October 2012 23:07, Doug Hellmann wrote: >> On Oct 15, 2012, at 2:18 PM, Doug Hellmann wrote: >>> I like "Environment::OpenStack" for the clients, and it could work for the other pieces, too. I'll ask around a bit and see what others have to say. >> >> I've talked to a few of the leaders on the infrastructure team for the project and they agree that "Environment::OpenStack" makes the most sense for a broader range of packages, so we would like to use that. > > Great! It's added. > > > Richard From tarek at ziade.org Tue Oct 23 10:00:32 2012 From: tarek at ziade.org (=?ISO-8859-1?Q?Tarek_Ziad=E9?=) Date: Tue, 23 Oct 2012 10:00:32 +0200 Subject: [Catalog-sig] Mirror page Message-ID: <50864EA0.8010505@ziade.org> Hey Looking at http://pypi.python.org/mirrors and Looking at http://www.pypi-mirrors.org/ I find the later much more appealing :) If the Ken agrees and think it's a good idea, I'd like to propose to have a big link to http://www.pypi-mirrors.org/ on http://pypi.python.org/mirrors and also on the index page. Cheers Tarek From dholth at gmail.com Sun Oct 28 19:47:43 2012 From: dholth at gmail.com (Daniel Holth) Date: Sun, 28 Oct 2012 14:47:43 -0400 Subject: [Catalog-sig] [Python-Dev] accept the wheel PEPs 425, 426, 427 In-Reply-To: References: <20121018211014.73d56057@pitrou.net> <87k3un5fwh.fsf@uwakimon.sk.tsukuba.ac.jp> <87a9vh694r.fsf@uwakimon.sk.tsukuba.ac.jp> <87626457t6.fsf@uwakimon.sk.tsukuba.ac.jp> Message-ID: I think Metadata 1.3 is done. Who would like to czar? On Oct 22, 2012 12:53 PM, "Daniel Holth" wrote: > http://hg.python.org/peps/rev/50e8ea1a17a0 > > Based on the other "required" field's absence in the wild, only > "Metadata-Version", "Name", "Version", and "Summary" are required. > Hopefully a clearer explanation of 0, 1, or many occurrences of each > field. > -------------- next part -------------- An HTML attachment was scrubbed... URL: From dholth at gmail.com Sun Oct 28 22:48:31 2012 From: dholth at gmail.com (Daniel Holth) Date: Sun, 28 Oct 2012 17:48:31 -0400 Subject: [Catalog-sig] [Python-Dev] accept the wheel PEPs 425, 426, 427 In-Reply-To: References: <20121018211014.73d56057@pitrou.net> <87k3un5fwh.fsf@uwakimon.sk.tsukuba.ac.jp> <87a9vh694r.fsf@uwakimon.sk.tsukuba.ac.jp> <87626457t6.fsf@uwakimon.sk.tsukuba.ac.jp> Message-ID: Now with an implementation at the end and possibly better wording for the required fields. I think it's feature complete. PEP: 426 Title: Metadata for Python Software Packages 1.3 Version: $Revision$ Last-Modified: $Date$ Author: Daniel Holth Discussions-To: Distutils SIG Status: Draft Type: Standards Track Content-Type: text/x-rst Created: 30 Aug 2012 Abstract ======== This PEP describes a mechanism for adding metadata to Python distributions. It includes specifics of the field names, and their semantics and usage. This document specifies version 1.3 of the metadata format. Version 1.0 is specified in PEP 241. Version 1.1 is specified in PEP 314. Version 1.2 is specified in PEP 345. Version 1.3 of the metadata format adds fields designed to make third-party packaging of Python Software easier and defines a formal extension mechanism. The fields are "Setup-Requires-Dist" "Provides-Extra", and "Extension". This version also adds the `extra` variable to the `environment markers` specification and allows the description to be placed into a payload section. Metadata Files ============== The syntax defined in this PEP is for use with Python distribution metadata files. The file format is a simple UTF-8 encoded Key: value format with no maximum line length, followed by a blank line and an arbitrary payload. It is parseable by the ``email`` module with an appropriate ``email.policy.Policy()``. When ``metadata`` is a Unicode string, ```email.parser.Parser().parsestr(metadata)`` is a serviceable parser. There are two standard locations for these metadata files: * the ``PKG-INFO`` file included in the base directory of Python source distribution archives (as created by the distutils ``sdist`` command) * the ``.dist-info/METADATA`` files in a Python installation database, as described in PEP 376. Other tools involved in Python distribution may also use this format. Encoding ======== Metadata 1.3 files are UTF-8 with the restriction that keys must be ASCII. Parser implementations should be aware that older versions of the Metadata specification do not specify an encoding. Fields ====== This section specifies the names and semantics of each of the supported metadata fields. In a single Metadata 1.3 file, fields marked with "(optional)" may occur 0 or 1 times. Fields marked with "(multiple use)" may be specified 0, 1 or more times. Only "Metadata-Version", "Name", "Version", and "Summary" must appear exactly once. The fields may appear in any order within the file. Metadata-Version :::::::::::::::: Version of the file format; "1.3" is the only legal value. Example:: Metadata-Version: 1.3 Name :::: The name of the distribution. Example:: Name: BeagleVote Version ::::::: A string containing the distribution's version number. This field must be in the format specified in PEP 386. Example:: Version: 1.0a2 Summary ::::::: A one-line summary of what the distribution does. Example:: Summary: A module for collecting votes from beagles. Platform (multiple use) ::::::::::::::::::::::: A Platform specification describing an operating system supported by the distribution which is not listed in the "Operating System" Trove classifiers. See "Classifier" below. Examples:: Platform: ObscureUnix Platform: RareDOS Supported-Platform (multiple use) ::::::::::::::::::::::::::::::::: Binary distributions containing a metadata file will use the Supported-Platform field in their metadata to specify the OS and CPU for which the binary distribution was compiled. The semantics of the Supported-Platform field are not specified in this PEP. Example:: Supported-Platform: RedHat 7.2 Supported-Platform: i386-win32-2791 Description (optional, deprecated) :::::::::::::::::::::::::::::::::: A longer description of the distribution that can run to several paragraphs. Software that deals with metadata should not assume any maximum size for this field. The contents of this field can be written using reStructuredText markup [1]_. For programs that work with the metadata, supporting markup is optional; programs can also display the contents of the field as-is. This means that authors should be conservative in the markup they use. Since a line separator immediately followed by another line separator indicates the end of the headers section, any line separators in the description must be suffixed by whitespace to indicate continuation. Since Metadata 1.3 the recommended place for the description is in the payload section of the document, after the last header. The description does not need to be reformatted when it is included in the payload. Keywords (optional) ::::::::::::::::::: A list of additional keywords to be used to assist searching for the distribution in a larger catalog. Example:: Keywords: dog puppy voting election Home-page (optional) :::::::::::::::::::: A string containing the URL for the distribution's home page. Example:: Home-page: http://www.example.com/~cschultz/bvote/ Download-URL (optional) ::::::::::::::::::::::: A string containing the URL from which this version of the distribution can be downloaded. (This means that the URL can't be something like ".../BeagleVote-latest.tgz", but instead must be ".../BeagleVote-0.45.tgz".) Author (optional) ::::::::::::::::: A string containing the author's name at a minimum; additional contact information may be provided. Example:: Author: C. Schultz, Universal Features Syndicate, Los Angeles, CA Author-email (optional) ::::::::::::::::::::::: A string containing the author's e-mail address. It contains a name and e-mail address in the RFC 5322 recommended ``Address Specification`` format. Example:: Author-email: "C. Schultz" Maintainer (optional) ::::::::::::::::::::: A string containing the maintainer's name at a minimum; additional contact information may be provided. Note that this field is intended for use when a project is being maintained by someone other than the original author: it should be omitted if it is identical to ``Author``. Example:: Maintainer: C. Schultz, Universal Features Syndicate, Los Angeles, CA Maintainer-email (optional) ::::::::::::::::::::::::::: A string containing the maintainer's e-mail address. It has the same format as ``Author-email``. Note that this field is intended for use when a project is being maintained by someone other than the original author: it should be omitted if it is identical to ``Author-email``. Example:: Maintainer-email: "C. Schultz" License (optional) :::::::::::::::::: Text indicating the license covering the distribution where the license is not a selection from the "License" Trove classifiers. See "Classifier" below. This field may also be used to specify a particular version of a license which is named via the ``Classifier`` field, or to indicate a variation or exception to such a license. Examples:: License: This software may only be obtained by sending the author a postcard, and then the user promises not to redistribute it. License: GPL version 3, excluding DRM provisions The full text of the license would normally be included in a separate file. Classifier (multiple use) ::::::::::::::::::::::::: Each entry is a string giving a single classification value for the distribution. Classifiers are described in PEP 301 [2]. Examples:: Classifier: Development Status :: 4 - Beta Classifier: Environment :: Console (Text Based) Requires-Dist (multiple use) :::::::::::::::::::::::::::: Each entry contains a string naming some other distutils project required by this distribution. The format of a requirement string is identical to that of a distutils project name (e.g., as found in the ``Name:`` field. optionally followed by a version declaration within parentheses. The distutils project names should correspond to names as found on the `Python Package Index`_. Version declarations must follow the rules described in `Version Specifiers`_ Examples:: Requires-Dist: pkginfo Requires-Dist: PasteDeploy Requires-Dist: zope.interface (>3.5.0) Setup-Requires-Dist (multiple use) :::::::::::::::::::::::::::::::::: Like Requires-Dist, but names dependencies needed while the distributions's distutils / packaging `setup.py` / `setup.cfg` is run. Commonly used to generate a manifest from version control. Examples:: Setup-Requires-Dist: custom_setup_command Dependencies mentioned in `Setup-Requires-Dist` may be installed exclusively for setup and are not guaranteed to be available at run time. Provides-Dist (multiple use) :::::::::::::::::::::::::::: Each entry contains a string naming a Distutils project which is contained within this distribution. This field *must* include the project identified in the ``Name`` field, followed by the version : Name (Version). A distribution may provide additional names, e.g. to indicate that multiple projects have been bundled together. For instance, source distributions of the ``ZODB`` project have historically included the ``transaction`` project, which is now available as a separate distribution. Installing such a source distribution satisfies requirements for both ``ZODB`` and ``transaction``. A distribution may also provide a "virtual" project name, which does not correspond to any separately-distributed project: such a name might be used to indicate an abstract capability which could be supplied by one of multiple projects. E.g., multiple projects might supply RDBMS bindings for use by a given ORM: each project might declare that it provides ``ORM-bindings``, allowing other projects to depend only on having at most one of them installed. A version declaration may be supplied and must follow the rules described in `Version Specifiers`_. The distribution's version number will be implied if none is specified. Examples:: Provides-Dist: OtherProject Provides-Dist: AnotherProject (3.4) Provides-Dist: virtual_package Obsoletes-Dist (multiple use) ::::::::::::::::::::::::::::: Each entry contains a string describing a distutils project's distribution which this distribution renders obsolete, meaning that the two projects should not be installed at the same time. Version declarations can be supplied. Version numbers must be in the format specified in `Version Specifiers`_. The most common use of this field will be in case a project name changes, e.g. Gorgon 2.3 gets subsumed into Torqued Python 1.0. When you install Torqued Python, the Gorgon distribution should be removed. Examples:: Obsoletes-Dist: Gorgon Obsoletes-Dist: OtherProject (<3.0) Requires-Python (optional) :::::::::::::::::::::::::: This field specifies the Python version(s) that the distribution is guaranteed to be compatible with. Version numbers must be in the format specified in `Version Specifiers`_. Examples:: Requires-Python: 2.5 Requires-Python: >2.1 Requires-Python: >=2.3.4 Requires-Python: >=2.5,<2.7 Requires-External (multiple use) :::::::::::::::::::::::::::::::: Each entry contains a string describing some dependency in the system that the distribution is to be used. This field is intended to serve as a hint to downstream project maintainers, and has no semantics which are meaningful to the ``distutils`` distribution. The format of a requirement string is a name of an external dependency, optionally followed by a version declaration within parentheses. Because they refer to non-Python software releases, version numbers for this field are **not** required to conform to the format specified in PEP 386: they should correspond to the version scheme used by the external dependency. Notice that there's is no particular rule on the strings to be used. Examples:: Requires-External: C Requires-External: libpng (>=1.5) Project-URL (multiple use) :::::::::::::::::::::::::: A string containing a browsable URL for the project and a label for it, separated by a comma. Example:: Bug Tracker, http://bitbucket.org/tarek/distribute/issues/ The label is a free text limited to 32 signs. Provides-Extra (multiple use) ::::::::::::::::::::::::::::: A string containing the name of an optional feature. Must be printable ASCII, not containing whitespace, comma (,), or square brackets []. May be used to make a dependency conditional on whether the optional feature has been requested. Example:: Name: beaglevote Provides-Extra: pdf Requires-Dist: reportlab; extra == 'pdf' Requires-Dist: nose; extra == 'test' Requires-Dist: sphinx; extra == 'doc' A second distribution requires an optional dependency by placing it inside square brackets and can request multiple features by separating them with a comma (,). The full set of requirements is the union of the `Requires-Dist` sets evaluated with `extra` set to `None` and then to the name of each requested feature. Example:: Requires-Dist: beaglevote[pdf] -> requires beaglevote, reportlab Requires-Dist: beaglevote[test, doc] -> requires beaglevote, sphinx, nose Two feature names `test` and `doc` are reserved to mark dependencies that are needed for running automated tests and generating documentation, respectively. It is legal to specify `Provides-Extra` without referencing it in any `Requires-Dist`. It is an error to request a feature name that has not been declared with `Provides-Extra`. Extension (multiple use) :::::::::::::::::::::::: An ASCII string, not containing whitespace or the / character, that indicates the presence of extended metadata. Additional tags defined by an `Extension: Chili` must be of the form `Chili/Name`:: Extension: Chili Chili/Type: Poblano Chili/Heat: Mild An implementation might iterate over all the declared `Extension:` fields to invoke the processors for those extensions. As the order of the fields is not used, the `Extension: Chili` field may appear before or after its declared tags `Chili/Type:` etc. Version Specifiers ================== Version specifiers are a series of conditional operators and version numbers, separated by commas. Conditional operators must be one of "<", ">", "<=", ">=", "==" and "!=". Any number of conditional operators can be specified, e.g. the string ">1.0, !=1.3.4, <2.0" is a legal version declaration. The comma (",") is equivalent to the **and** operator. Each version number must be in the format specified in PEP 386. When a version is provided, it always includes all versions that starts with the same value. For example the "2.5" version of Python will include versions like "2.5.2" or "2.5.3". Pre and post releases in that case are excluded. So in our example, versions like "2.5a1" are not included when "2.5" is used. If the first version of the range is required, it has to be explicitly given. In our example, it will be "2.5.0". Notice that some projects might omit the ".0" prefix for the first release of the "2.5.x" series: - 2.5 - 2.5.1 - 2.5.2 - etc. In that case, "2.5.0" will have to be explicitly used to avoid any confusion between the "2.5" notation that represents the full range. It is a recommended practice to use schemes of the same length for a series to completely avoid this problem. Some Examples: - ``Requires-Dist: zope.interface (3.1)``: any version that starts with 3.1, excluding post or pre-releases. - ``Requires-Dist: zope.interface (==3.1)``: equivalent to ``Requires-Dist: zope.interface (3.1)``. - ``Requires-Dist: zope.interface (3.1.0)``: any version that starts with 3.1.0, excluding post or pre-releases. Since that particular project doesn't use more than 3 digits, it also means "only the 3.1.0 release". - ``Requires-Python: 3``: Any Python 3 version, no matter wich one, excluding post or pre-releases. - ``Requires-Python: >=2.6,<3``: Any version of Python 2.6 or 2.7, including post releases of 2.6, pre and post releases of 2.7. It excludes pre releases of Python 3. - ``Requires-Python: 2.6.2``: Equivalent to ">=2.6.2,<2.6.3". So this includes only Python 2.6.2. Of course, if Python was numbered with 4 digits, it would have include all versions of the 2.6.2 series. - ``Requires-Python: 2.5.0``: Equivalent to ">=2.5.0,<2.5.1". - ``Requires-Dist: zope.interface (3.1,!=3.1.3)``: any version that starts with 3.1, excluding post or pre-releases of 3.1 *and* excluding any version that starts with "3.1.3". For this particular project, this means: "any version of the 3.1 series but not 3.1.3". This is equivalent to: ">=3.1,!=3.1.3,<3.2". Environment markers =================== An **environment marker** is a marker that can be added at the end of a field after a semi-colon (";"), to add a condition about the execution environment. Here are some example of fields using such markers:: Requires-Dist: pywin32 (>1.0); sys.platform == 'win32' Obsoletes-Dist: pywin31; sys.platform == 'win32' Requires-Dist: foo (1,!=1.3); platform.machine == 'i386' Requires-Dist: bar; python_version == '2.4' or python_version == '2.5' Requires-External: libxslt; 'linux' in sys.platform The micro-language behind this is a simple subset of Python: it compares only strings, with the ``==`` and ``in`` operators (and their opposites), and with the ability to combine expressions. Parenthesis are supported for grouping. The pseudo-grammar is :: EXPR [in|==|!=|not in]?EXPR [or|and] ... where ``EXPR`` belongs to any of those: - python_version = '%s.%s' % (sys.version_info[0], sys.version_info[1]) - python_full_version = sys.version.split()[0] - os.name = os.name - sys.platform = sys.platform - platform.version = platform.version() - platform.machine = platform.machine() - platform.python_implementation = platform.python_implementation() - a free string, like ``'2.4'``, or ``'win32'`` - extra = (name of requested feature) or None Notice that ``in`` is restricted to strings, meaning that it is not possible to use other sequences like tuples or lists on the right side. The fields that benefit from this marker are: - Requires-Python - Requires-External - Requires-Dist - Setup-Requires-Dist - Provides-Dist - Obsoletes-Dist - Classifier (The `extra` variable is only meaningful for Requires-Dist.) Summary of Differences From PEP 345 =================================== * Metadata-Version is now 1.3. * Values are now expected to be UTF-8. * A payload (containing the description) may appear after the headers. * Added `extra` to environment markers. * Most fields are now optional. * Changed fields: - Requires-Dist - Description * Added fields: - Setup-Requires-Dist - Provides-Extra - Extension References ========== This document specifies version 1.3 of the metadata format. Version 1.0 is specified in PEP 241. Version 1.1 is specified in PEP 314. Version 1.2 is specified in PEP 345. .. [1] reStructuredText markup: http://docutils.sourceforge.net/ .. _`Python Package Index`: http://pypi.python.org/pypi/ .. [2] PEP 301: http://www.python.org/dev/peps/pep-0301/ Appendix ======== Parsing and generating the Metadata 1.3 serialization format using Python 3.3:: # Metadata 1.3 demo from email.generator import Generator from email import header from email.parser import Parser from email.policy import Compat32 from email.utils import _has_surrogates class MetadataPolicy(Compat32): max_line_length = 0 continuation_whitespace = '\t' def _sanitize_header(self, name, value): if not isinstance(value, str): return value if _has_surrogates(value): raise NotImplementedError() else: return value def _fold(self, name, value, sanitize): body = ((self.linesep+self.continuation_whitespace) .join(value.splitlines())) return ''.join((name, ': ', body, self.linesep)) if __name__ == "__main__": import sys import textwrap pkg_info = """\ Metadata-Version: 1.3 Name: package Version: 0.1.0 Summary: A package. Description: Description =========== A description of the package. """ m = Parser(policy=MetadataPolicy()).parsestr(pkg_info) m['License'] = 'GPL' description = m['Description'] description_lines = description.splitlines() m.set_payload(description_lines[0] + '\n' + textwrap.dedent('\n'.join(description_lines[1:])) + '\n') del m['Description'] # Correct if sys.stdout.encoding == 'UTF-8': Generator(sys.stdout, maxheaderlen=0).flatten(m) Copyright ========= This document has been placed in the public domain. .. Local Variables: mode: indented-text indent-tabs-mode: nil sentence-end-double-space: t fill-column: 70 End: From vinay_sajip at yahoo.co.uk Tue Oct 30 00:28:45 2012 From: vinay_sajip at yahoo.co.uk (Vinay Sajip) Date: Mon, 29 Oct 2012 23:28:45 +0000 (UTC) Subject: [Catalog-sig] Rules for registering project names on PyPI Message-ID: Can someone please point me to where the rules are defining what are acceptable names for projects registered on PyPI? There are some unusual names, e.g. ? ('\u2603') fl??gelform "Coversation With Your Car" (including the quotes) Aaaaaaaaaaaaaaaaaaa aaaaaaaaa aaaaaaasa aaaaaaasa aaaaasaa aaaaaaasa bbbbbbbbbbb __past__ Plus there are some names which show up in the XML-RPC API, but not in any other interface (e.g. __my__schachtler) It's a little hard to believe that these are genuine projects. Has there been any discussion about tightening the rules for new registrations, or about tightening the rules for version formats for new projects? I would appreciate any pointers people can provide. Regards, Vinay Sajip From donald.stufft at gmail.com Tue Oct 30 00:38:37 2012 From: donald.stufft at gmail.com (Donald Stufft) Date: Mon, 29 Oct 2012 19:38:37 -0400 Subject: [Catalog-sig] Rules for registering project names on PyPI In-Reply-To: References: Message-ID: <54A0971BB5DD44B8B5EF5CAEBC47AE87@gmail.com> I believe the rules are doesn't contain a slash character, as in / On Monday, October 29, 2012 at 7:28 PM, Vinay Sajip wrote: > Can someone please point me to where the rules are defining what are acceptable > names for projects registered on PyPI? There are some unusual names, e.g. > > ? ('\u2603') > fl??gelform > "Coversation With Your Car" (including the quotes) > Aaaaaaaaaaaaaaaaaaa aaaaaaaaa aaaaaaasa aaaaaaasa aaaaasaa aaaaaaasa bbbbbbbbbbb > __past__ > > Plus there are some names which show up in the XML-RPC API, but not in any other > interface (e.g. __my__schachtler) > > It's a little hard to believe that these are genuine projects. > > Has there been any discussion about tightening the rules for new registrations, > or about tightening the rules for version formats for new projects? I would > appreciate any pointers people can provide. > > Regards, > > Vinay Sajip > > _______________________________________________ > Catalog-SIG mailing list > Catalog-SIG at python.org (mailto:Catalog-SIG at python.org) > http://mail.python.org/mailman/listinfo/catalog-sig > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From donald.stufft at gmail.com Tue Oct 30 05:11:26 2012 From: donald.stufft at gmail.com (Donald Stufft) Date: Tue, 30 Oct 2012 00:11:26 -0400 Subject: [Catalog-sig] Rules for registering project names on PyPI In-Reply-To: References: Message-ID: <683B7BCED36844D39FB08471EC5A83C0@gmail.com> On Monday, October 29, 2012 at 7:28 PM, Vinay Sajip wrote: > Plus there are some names which show up in the XML-RPC API, but not in any other > interface (e.g. __my__schachtler) This normally means that the project is registered on PyPI but has no versions associated with it. -------------- next part -------------- An HTML attachment was scrubbed... URL: From g.brandl at gmx.net Tue Oct 30 09:12:08 2012 From: g.brandl at gmx.net (Georg Brandl) Date: Tue, 30 Oct 2012 09:12:08 +0100 Subject: [Catalog-sig] Rules for registering project names on PyPI In-Reply-To: References: Message-ID: Am 30.10.2012 00:28, schrieb Vinay Sajip: > Can someone please point me to where the rules are defining what are acceptable > names for projects registered on PyPI? There are some unusual names, e.g. > > ? ('\u2603') I hope this one implements PEP 3117. > fl??gelform Looks like UTF-8 coding of an umlaut ? gone wrong (or did it happen in your mailer? then it is a perfectly fine project name). > "Coversation With Your Car" (including the quotes) > Aaaaaaaaaaaaaaaaaaa aaaaaaaaa aaaaaaasa aaaaaaasa aaaaasaa aaaaaaasa bbbbbbbbbbb Well, it doesn't seem like anyone would use them, but as long as they don't do any harm, they increase the number of registered packages we can boast about ;-) > __past__ Could be a good package providing more backwards compatibility. Georg From asmeurer at gmail.com Tue Oct 30 09:19:43 2012 From: asmeurer at gmail.com (Aaron Meurer) Date: Tue, 30 Oct 2012 02:19:43 -0600 Subject: [Catalog-sig] Rules for registering project names on PyPI In-Reply-To: References: Message-ID: On Tue, Oct 30, 2012 at 2:12 AM, Georg Brandl wrote: > Am 30.10.2012 00:28, schrieb Vinay Sajip: >> Can someone please point me to where the rules are defining what are acceptable >> names for projects registered on PyPI? There are some unusual names, e.g. >> >> ? ('\u2603') > > I hope this one implements PEP 3117. > >> fl??gelform > > Looks like UTF-8 coding of an umlaut ? gone wrong (or did it happen in your > mailer? then it is a perfectly fine project name). > >> "Coversation With Your Car" (including the quotes) >> Aaaaaaaaaaaaaaaaaaa aaaaaaaaa aaaaaaasa aaaaaaasa aaaaasaa aaaaaaasa bbbbbbbbbbb > > Well, it doesn't seem like anyone would use them, but as long as they don't do > any harm, they increase the number of registered packages we can boast about ;-) > >> __past__ > > Could be a good package providing more backwards compatibility. I can't find the actual source anywhere, but my guess is that this was a joke. Perhaps it implemented something like http://stackoverflow.com/a/1036396/161801. Aaron Meurer > > Georg > > _______________________________________________ > Catalog-SIG mailing list > Catalog-SIG at python.org > http://mail.python.org/mailman/listinfo/catalog-sig