On 10/16/11 3:07 AM, Wichert Akkerman wrote:
On 2011-10-16 02:29, Alex Clark wrote:
On 10/13/11 3:01 AM, Wichert Akkerman wrote:
On 2011-10-13 05:31, Jon Stahl wrote:
In the longer term, I do think we want to seriously consider shifting
Plone.org to be more of a selective Pypi scraper. We'd have to think
about how to best include the ultra-important Plone version
compatibility metadata, but I assume that with so many smart folks
running around, that is solveable.
It would be pretty simple to do this as a trove classifier:
classifiers = [
'Framework :: Plone :: 4.1',
'Framework :: Plone :: 4.2',
'Natural Language :: Dutch',
'Programming Language :: Python :: 2.6',
'Programming Language :: Python :: 2.7',
]
that is exposed directly on the pypi UI and can be used as a search key
when searching for packages.
Sure, but is The Right Way™? IOW, wouldn't it be "better" if these were
"real" trove classifiers as defined by:
= http://pypi.python.org/pypi?%3Aaction=list_classifiers
They are "real" trove classifiers. If you look at your URL you'll see
all the different python versions listed in there as well.
Right but we have to get the PyPI folks to add them, correct? Or is
there an approach that involves acting independently of their actions.
That's what I am getting at, and what has always been my concern.
Anyway, seems like they are receptive so maybe I won't have to worry
about it.
Alex
Wichert.
--
Alex Clark · http://aclark.net
_______________________________________________
Product-Developers mailing list
[email protected]
https://lists.plone.org/mailman/listinfo/plone-product-developers
