On Sun, 2011-12-11 at 23:36 +0100, "Martin v. Löwis" wrote:
> > It'd be useful to have a Trove classifier that signified "the authors
> > have no current intention to port this code to Python 3".
>
> That classifier already exists: "Programming Language :: Python :: 2"
> indicates support for Pyt
On Sun, Dec 11, 2011 at 11:36:26PM +0100, "Martin v. Löwis" wrote:
> > It'd be useful to have a Trove classifier that signified "the authors
> > have no current intention to port this code to Python 3".
>
> That classifier already exists: "Programming Language :: Python :: 2"
> indicates support
On 11 December 2011 23:02, Richard Jones wrote:
> On 12 December 2011 09:36, "Martin v. Löwis" wrote:
> > If you think that this is still different from what you are asking:
> > What specific packages would be tagged with that classifier (I need
> > two at least), and did that package authors ag
On 12 December 2011 09:36, "Martin v. Löwis" wrote:
> If you think that this is still different from what you are asking:
> What specific packages would be tagged with that classifier (I need
> two at least), and did that package authors agree to add the classifier
> to their package if it was ava
On 11 December 2011 15:44, Chris McDonough wrote:
> It'd be useful to have a Trove classifier that signified "the authors
> have no current intention to port this code to Python 3". Such a
> classifier could be used by e.g. http://python3wos.appspot.com/ to
> present a more accurate picture of th
> It'd be useful to have a Trove classifier that signified "the authors
> have no current intention to port this code to Python 3".
That classifier already exists: "Programming Language :: Python :: 2"
indicates support for Python 2, and absence of "Programming Language ::
Python :: 3" then indic
On Sun, 2011-12-11 at 13:01 -0800, Noah Kantrowitz wrote:
> The "keywords" argument to setup(), which can then be searched via the
> XML-RPC API.
>
> --Noah
The intent is to allow a site like http://python3wos.appspot.com/ to
ignore distributions that signify an intent never to port to Python 3.
The "keywords" argument to setup(), which can then be searched via the XML-RPC
API.
--Noah
On Dec 11, 2011, at 11:16 AM, Chris McDonough wrote:
> On Sun, 2011-12-11 at 11:12 -0800, Noah Kantrowitz wrote:
>> Is there a reason this needs to be a trove classifier? Just make some
>> standard tag a
On Sun, 2011-12-11 at 11:12 -0800, Noah Kantrowitz wrote:
> Is there a reason this needs to be a trove classifier? Just make some
> standard tag and use that :-)
Please define "tag".
- C
>
> --Noah
>
> On Dec 10, 2011, at 8:44 PM, Chris McDonough wrote:
>
> > Hi,
> >
> > It'd be useful to
Is there a reason this needs to be a trove classifier? Just make some standard
tag and use that :-)
--Noah
On Dec 10, 2011, at 8:44 PM, Chris McDonough wrote:
> Hi,
>
> It'd be useful to have a Trove classifier that signified "the authors
> have no current intention to port this code to Python
These are the ones I would like to see:
> >License :: OSI Approved :: GNU Lesser General Public License v2 (LGPLv2)
> >License :: OSI Approved :: GNU Lesser General Public License v3 (LGPLv3)
> >License :: OSI Approved :: GNU Lesser General Public License v2 or later
> >(LGPLv2+)
> >License :: OS
11 matches
Mail list logo
