Code

Opened 10 months ago

Closed 10 months ago

Last modified 10 months ago

#20615 closed Cleanup/optimization (fixed)

Django 1.5.1 Trove classification is incorrect

Reported by: anonymous Owned by: nobody
Component: Packaging Version: 1.5
Severity: Normal Keywords:
Cc: Triage Stage: Accepted
Has patch: no Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: yes UI/UX: no

Description

Django shows up the list of Python packages that people want Python 3 support for at http://www.python.org/3kpoll. That page says "Please ask the package authors to use the Trove classifier 'Programming Language :: Python :: 3' to indicate that the port (to Python 3) has been done." I note that Django 1.5.1 has the Trove classifiers "Programming Language :: Python :: 3.2" and "Programming Language :: Python :: 3.3", but not "Programming Language :: Python :: 3".

Attachments (0)

Change History (3)

comment:1 Changed 10 months ago by bmispelon

  • Needs documentation unset
  • Needs tests unset
  • Patch needs improvement unset
  • Triage Stage changed from Unreviewed to Accepted

I couldn't find a reference, but the Programming Language :: Python :: 3 trove seems to be used in practice and appears in the list of classifiers [1].

I don't see any reason against adding it.

[1] https://pypi.python.org/pypi?%3Aaction=list_classifiers

comment:2 Changed 10 months ago by Aymeric Augustin <aymeric.augustin@…>

  • Resolution set to fixed
  • Status changed from new to closed

In efe6e16008b4a123666cc445f7319efce8e9b6bf:

Fixed #20615 -- Added trove classifiers for major Python versions.

comment:3 Changed 10 months ago by Aymeric Augustin <aymeric.augustin@…>

In 9d86550a70ccb84249f493cef74db4636f20c3f1:

[1.5.x] Fixed #20615 -- Added trove classifiers for major Python versions.

Backport of efe6e160.

Add Comment

Modify Ticket

Change Properties
<Author field>
Action
as closed
as The resolution will be set. Next status will be 'closed'
The resolution will be deleted. Next status will be 'new'
Author


E-mail address and user name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.