Following up on some IRC discussion with other folks:
There is precedent (Plone) for PyPI trove classifiers corresponding to
particular versions of a framework. So I'd like to get feedback on the idea
of expanding that, particularly in the case of Django.
The rationale here is that the ecosystem
I complete support James. This trove classifier is something that
could be pretty easily plugged right into Django Packages and the rest
of the Django ecosystem.
--Daniel Greenfeld
On Sun, Mar 29, 2015 at 9:49 PM, James Bennett wrote:
> Following up on some IRC discussion with other folks:
>
> T
Hi James,
I tend to just require that there already exists a number of packages that
would use the classifier. Sounds like that's the case?
Richard
On Mon, 30 Mar 2015 at 15:50 James Bennett wrote:
> Following up on some IRC discussion with other folks:
>
> There is precedent (Plone) for
On Sun, Mar 29, 2015 at 11:58 PM, Richard Jones wrote:
>
> I tend to just require that there already exists a number of packages that
> would use the classifier. Sounds like that's the case?
>
I don't have a count handy, but yes, I suspect the number of packages which
currently use the "Framwork
Richard,
If you look at https://www.djangopackages.com you'll see that 631
packages are Python 3 compatible out of 2714 listed. This number has
been growing steadily, as package maintainers have learned that they
can get listed there by utilizing the trove classifier system. It
wasn't hard for us
OK, so what's the set of versions you'd like to see?
On Mon, 30 Mar 2015 at 16:03 Daniel Greenfeld wrote:
> Richard,
>
> If you look at https://www.djangopackages.com you'll see that 631
> packages are Python 3 compatible out of 2714 listed. This number has
> been growing steadily, as package ma
Since a lot of sites are still migrating from 1.5, shouldn't we add
that version to the mix?
1.4
1.5
1.6
1.7
--Danny
On Sun, Mar 29, 2015 at 10:06 PM, James Bennett wrote:
> On Mon, Mar 30, 2015 at 12:04 AM, Richard Jones wrote:
>>
>> OK, so what's the set of versions you'd like to see?
>>
>
On Mon, Mar 30, 2015 at 12:04 AM, Richard Jones wrote:
> OK, so what's the set of versions you'd like to see?
>
>
The current upstream-supported version set is Django 1.4, Django 1.6,
Django 1.7. Soon 1.6 will drop out and be replaced by 1.8, but that's just
because we're coming up on a release.
I would be OK with including 1.5 just for completeness' sake.
___
Distutils-SIG maillist - Distutils-SIG@python.org
https://mail.python.org/mailman/listinfo/distutils-sig
Added!
Framework :: Django :: 1.4
Framework :: Django :: 1.5
Framework :: Django :: 1.6
Framework :: Django :: 1.7
Framework :: Django :: 1.8
On Mon, 30 Mar 2015 at 16:09 James Bennett wrote:
> I would be OK with including 1.5 just for completeness' sake.
>
___
On 3/30/15 1:13 AM, Richard Jones wrote:
Added!
Framework :: Django :: 1.4
Framework :: Django :: 1.5
Framework :: Django :: 1.6
Framework :: Django :: 1.7
Framework :: Django :: 1.8
Great! In Plone's case, we also added every foreseeable future version,
which it appears you have already don
Reviving this old thread because today is Django 1.9's release date and I'm
unsure of the process for keeping up with new-released versions in trove
classifiers. Do we need to manually poke someone each time (as with today,
when "Framework :: Django :: 1.9" becomes a thing), or is there a way to
au
At the moment it's a manual poke, but I have done this thing right now.
On 2 December 2015 at 10:46, James Bennett wrote:
> Reviving this old thread because today is Django 1.9's release date and
> I'm unsure of the process for keeping up with new-released versions in
> trove classifiers. Do we
Could you add Plone 5.1 too? It may still take half a year or more
before we release this, but we are starting to think about what we want
to put in there.
So this one:
Framework :: Plone :: 5.1
Thanks,
Maurits
Op 02/12/15 om 01:54 schreef Richard Jones:
At the moment it's a manual poke, b
I prefer not to add classifiers unless they're actually going to be used.
Half a year could turn into a year :-)
On 4 December 2015 at 08:22, Maurits van Rees
wrote:
> Could you add Plone 5.1 too? It may still take half a year or more before
> we release this, but we are starting to think about
Fair enough. :-)
See you in six or more months. ;-)
Maurits
Op 04/12/15 om 00:53 schreef Richard Jones:
I prefer not to add classifiers unless they're actually going to be
used. Half a year could turn into a year :-)
On 4 December 2015 at 08:22, Maurits van Rees
mailto:m.van.r...@zestsoftware
Could we get 'Framework :: Django :: 1.10' please? Django 1.10 has been out
for a while :)
On Fri, Dec 4, 2015 at 12:59 AM, Maurits van Rees <
m.van.r...@zestsoftware.nl> wrote:
> Fair enough. :-)
>
> See you in six or more months. ;-)
>
> Maurits
>
> Op 04/12/15 om 00:53 schreef Richard Jones:
>
Bumping this because Django 1.11 is out, so 'Framework :: Django :: 1.11'
would be a useful thing to have.
___
Distutils-SIG maillist - Distutils-SIG@python.org
https://mail.python.org/mailman/listinfo/distutils-sig
18 matches
Mail list logo
