Re: collective packages on pypi

Maurits van Rees <m.van.rees@...> writes:


> Package uploading via 'python setup.py sdist mupload' (well, fullrelease 
> from zest.releaser of course) at least works.  I got an error doing this 
> last week on a package I recently got upload rights to, tried it again 
> and it worked.


We should check to see if blob content is being created. If so then it's
probably OK to serve the content directly from Plone.


> 
> I think I am not really using the uploaded packages, as buildout gets 
> them from PyPI, but uploading at least still works for me.  I keep 
> uploading because then the products with their latest info can be found 
> on plone.org.


That's the only reason this feature was ever useful IMHO, because it automated
the creation of a lot of PSC content.


> In other news, updating plone.org to Plone 4.3 has broken Poi, giving a 
> validation error when creating a new issue, and only one person has 
> complained to me so far, which tells something about how much Poi is 
> being used on plone.org.  Probably more people have seen it and have 
> simply gone to issue trackers on github.  The error was fixed a few 
> months before, but the Poi version on plone.org is old.  I created a 
> pull request for plone.org here, in case someone wants to have a go at 
> that: https://github.com/plone/Products.PloneOrg/pull/11


Deployed.



> 
> Cheers,
> 





------------------------------------------------------------------------------
Introducing Performance Central, a new site from SourceForge and 
AppDynamics. Performance Central is your source for news, insights, 
analysis and resources for efficient Application Performance Management. 
Visit us today!
http://pubads.g.doubleclick.net/gampad/clk?id=48897511&iu=/4140/ostg.clktrk