Re: [Zope3-dev] z3c.widget(.tiny) widget available to easy_install anywhere?
On Apr 20, 2007, at 2:04 PM, Fred Drake wrote: For one, "setup.py register" shouldn't always hide other releases; it should be possible to configure that on the client side. I'd prefer ro configure it on the server, once per project. But I'd take either. :) Yes, it's possible to have multiple releases visible now, but PyPI makes it unnecessarily tedious. And if you do, you lose the nice project home page. (You still have a home page per release, but then it can't use a simple URL to point to it.) Jim -- Jim Fulton mailto:[EMAIL PROTECTED]Python Powered! CTO (540) 361-1714 http://www.python.org Zope Corporationhttp://www.zope.com http://www.zope.org ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
Re: [Zope3-dev] z3c.widget(.tiny) widget available to easy_install anywhere?
On 4/20/07, David Pratt <[EMAIL PROTECTED]> wrote: I am not sure why there are two resources for obtaining eggs myself, not sure if it is because pipy gets busy. Should the default be pipy or will this slow buildouts? Maybe all packages could be put there in any case even if primary dependency link for zope packages is download.zope.org. Performance is certainly one reason; PyPI gets its share of aggressive crawlers. Another issue is that PyPI isn't all that interesting for deploying production applications; we need to be able to rely on getting the same set of releases when re-deploying, and we can't do that if someone else is able to hide/remove releases (or the associated downloads), so for longer-term reliability, we all need to maintain a repository of at least the things we expect to be able to get again. pipy already has the infrastructure for some proper searching and management for package maintainers - so not sure that the wheel needs to be invented. For one, "setup.py register" shouldn't always hide other releases; it should be possible to configure that on the client side. Yes, it's possible to have multiple releases visible now, but PyPI makes it unnecessarily tedious. -Fred -- Fred L. Drake, Jr. "Chaos is the score upon which reality is written." --Henry Miller ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
Re: [Zope3-dev] z3c.widget(.tiny) widget available to easy_install anywhere?
Hi Martin. Cheeseshop does this already. You can see how a nice overview page is constructed by putting readme.txt with readme.txt release notes in setup.py as restructured text. This is available on some zope packages but also the zif packages on pipy. See zif.headincludes in the cheeseshop as an example of how this works for a nice web page explaining the package. I am not sure why there are two resources for obtaining eggs myself, not sure if it is because pipy gets busy. Should the default be pipy or will this slow buildouts? Maybe all packages could be put there in any case even if primary dependency link for zope packages is download.zope.org. Maybe this just adds to the headache of releases to have more than a single location. pipy already has the infrastructure for some proper searching and management for package maintainers - so not sure that the wheel needs to be invented. Actually, I thought the way this was all going to unfold was with the ZF website which I think is still being worked on. Many thanks. Regards, David Martijn Faassen wrote: Hi there, I'm interested in adding a dependency on z3c.widget, and in particular z3c.widget.tiny, in an application I'm available. In the svn checkins I see a comment by dobe saying: buildout and egg, clean imports This implies to me there might be an tgz that buildout/easy_install can use available somewhere. But where? I cannot find it in the cheeseshop, nor in download.zope.org/distribution. Is it available somewhere else? Or should I upload a version of it myself? Regards, Martijn P.S. Visibility of Zope 3 extensions would be increased greatly if we could have an overview page per extension on zope.org somewhere. It would of course include the canonical download link as well. I think we can accomplish this relatively quickly with a fairly low-tech project, but we need a volunteer. Anyone? ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/fairwinds%40eastlink.ca ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
Re: [Zope3-dev] z3c.widget(.tiny) widget available to easy_install anywhere?
On Apr 20, 2007, at 1:32 PM, Sidnei da Silva wrote: P.S. Visibility of Zope 3 extensions would be increased greatly if we could have an overview page per extension on zope.org somewhere. It would of course include the canonical download link as well. I think we can accomplish this relatively quickly with a fairly low-tech project, but we need a volunteer. Anyone? Sort of like cheeseshop? BTW, why aren't the Zope packages on cheeseshop to start with? Many of the zope packages have been minimally eggified. I personally don't want to see packages appear in the cheeseshop until their meta data has been filled out and have documentation that either shows up in the cheeseshop or is linked from there. I'm also finding it challenging to manage eggs in the cheeseshop. The cheeseshop makes it really hard to publish multiple versions and multiple versions need to be accessable to buildout so that versions can be frozen. I wish we had our own tool that we could link to from the cheesehop, but, of course, I don't have time to write it. I guess I should request cheeseshop enhancements. Jim -- Jim Fulton mailto:[EMAIL PROTECTED]Python Powered! CTO (540) 361-1714 http://www.python.org Zope Corporationhttp://www.zope.com http://www.zope.org ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
Re: [Zope3-dev] z3c.widget(.tiny) widget available to easy_install anywhere?
P.S. Visibility of Zope 3 extensions would be increased greatly if we could have an overview page per extension on zope.org somewhere. It would of course include the canonical download link as well. I think we can accomplish this relatively quickly with a fairly low-tech project, but we need a volunteer. Anyone? Sort of like cheeseshop? BTW, why aren't the Zope packages on cheeseshop to start with? -- Sidnei da Silva Enfold Systemshttp://enfoldsystems.com Fax +1 832 201 8856 Office +1 713 942 2377 Ext 214 ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
