Re: [Framework-Team] pypi ticket for adding Plone 5.0 to trove tags
Giacomo Spettoli schreef op 15-04-14 15:32: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 04/15/2014 12:50 PM, Johannes Raggam wrote: I just opened a ticket on the pypi issue tracker to add Framework :: Plone :: 5.0 to the trove tags. https://sourceforge.net/p/pypi/support-requests/366/ Looks like, Plone is the only project, which has version-specific trove tags. https://pypi.python.org/pypi?%3Aaction=list_classifiers Should we give up these version specific tags? IMHO no one would really trust the classifiers list for knowing the plugin's compatibility. I normally take a look at the README (when I'm lucky) and to the code (when I'm not lucky). When I am working on a package in the collective and wonder what it is supposed to be compatible with, I do look at the classifiers, so that I know with which Plone versions I should be testing any changes that I make. I like that. Of course they can be out of date, just like a remark in the readme can be out of date. -- Maurits van Rees: http://maurits.vanrees.org/ ___ Framework-Team mailing list framework-t...@lists.plone.org https://lists.plone.org/mailman/listinfo/plone-framework-team
Re: [Framework-Team] pypi ticket for adding Plone 5.0 to trove tags
I'm a bit undecided on that topic. On the one hand, it would be super-handy to consistently use these classifiers. Although, the process of getting them into the PyPi list is a bit tedious. On the other hand, I don't like to be Plone the project, which spams the list of trove classifiers with version specific ones. We already have 7, while every other Framework just has one. FYI, the issue on sourceforge was rejected: http://sourceforge.net/p/pypi/support-requests/366/ Sorry, we only add classifiers that would be in active use. Please ask again when you have a number of Plone 5.0 related packages which would have that classifier. On Wed, 2014-04-16 at 11:01 +0200, Maurits van Rees wrote: Giacomo Spettoli schreef op 15-04-14 15:32: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 04/15/2014 12:50 PM, Johannes Raggam wrote: I just opened a ticket on the pypi issue tracker to add Framework :: Plone :: 5.0 to the trove tags. https://sourceforge.net/p/pypi/support-requests/366/ Looks like, Plone is the only project, which has version-specific trove tags. https://pypi.python.org/pypi?%3Aaction=list_classifiers Should we give up these version specific tags? IMHO no one would really trust the classifiers list for knowing the plugin's compatibility. I normally take a look at the README (when I'm lucky) and to the code (when I'm not lucky). When I am working on a package in the collective and wonder what it is supposed to be compatible with, I do look at the classifiers, so that I know with which Plone versions I should be testing any changes that I make. I like that. Of course they can be out of date, just like a remark in the readme can be out of date. -- Maurits van Rees: http://maurits.vanrees.org/ ___ Framework-Team mailing list framework-t...@lists.plone.org https://lists.plone.org/mailman/listinfo/plone-framework-team -- programmatic web development di(fh) johannes raggam / thet python plone zope development plone framework team member mail: off...@programmatic.pro web: http://programmatic.pro http://bluedynamics.com signature.asc Description: This is a digitally signed message part ___ Framework-Team mailing list framework-t...@lists.plone.org https://lists.plone.org/mailman/listinfo/plone-framework-team
Re: [Framework-Team] pypi ticket for adding Plone 5.0 to trove tags
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 04/15/2014 12:50 PM, Johannes Raggam wrote: I just opened a ticket on the pypi issue tracker to add Framework :: Plone :: 5.0 to the trove tags. https://sourceforge.net/p/pypi/support-requests/366/ Looks like, Plone is the only project, which has version-specific trove tags. https://pypi.python.org/pypi?%3Aaction=list_classifiers Should we give up these version specific tags? IMHO no one would really trust the classifiers list for knowing the plugin's compatibility. I normally take a look at the README (when I'm lucky) and to the code (when I'm not lucky). I agree that maybe the versioning doesn't make much sense and, in the best of all the possible universes, it would be better to move the current classifiers to something more linked to the purpose of the package that you're publishing. For example: Framework :: Plone :: Theme Framework :: Plone :: Plugin But, truth be told, I don't know how much work would this take and if this is doable by the Plone community or it has to be done by the pypi maintainers. I asked to some colleague of mine and, even though everybody uses them in the packages, no one ever really used those classifiers for searching packages or whatever. So.././much effort for a low gain My 2c Giacomo Cheers, Johannes ___ Framework-Team mailing list framework-t...@lists.plone.org https://lists.plone.org/mailman/listinfo/plone-framework-team - -- Giacomo Spettoli Twitter: http://twitter.com/giacomospettoli LinkedIn: http://linkedin.com/in/giacomospettoli -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.14 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQEcBAEBAgAGBQJzAAoJEC+mVWm56Xu8Ri8H/1EBSBrQXPstJ6Soz6HCDMEc ITFJzoGfsnay7jhlMcvk9Ryr9xlceVjzxzb2ghvrGtop9S4pJZ2g1bBj8DbYhnNv H3GVLmKc2iq1kVA+DDI6Ll5e4R4d09faSdmknLw5k6Qw+E9UgasCSmDoPbaaC9ss k52owmP+6n1HBox7AbDmVDZav/xIkKBwYgJfFNoH194fWClY339AKxE5g383ct6H 65ET1x4kiwPGhAkKhR/4PugYosHfvZcUzEKRp4TCUb8kwaQ7bEuCKItEdbWtXnnl EiZYw+Ai6WS6M+8iKqkbVyjeR/W+JVA9LaTklN2ao8naPglqMA29X6UOTlY/KbU= =Wz0u -END PGP SIGNATURE- ___ Framework-Team mailing list framework-t...@lists.plone.org https://lists.plone.org/mailman/listinfo/plone-framework-team
