[Zope3-dev] Get nearest site from TALES
Hello, is there a TALES expression I can use in PageTemplates to get the nearest site? Thanks, Florian ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
[Zope3-dev] eggs for Zope 3 extensions
Hi there, I know there are lots of ideas about eggs in Zope 3 land, so I'd like to pick the brains of the people who have looked into this more than I have for a bit. First to say what I'm not talking about: I'm not talking about eggifying Zope 3 itself. This is a valuable project but hopefully mostly independent of what I'd like to do. There are a whole bunch of interesting Zope 3 extensions that I'd like to use in a project, such as some of the various zc.* packages. Imagine they've been turned into eggs. Now my project wants to use them. What's the Zope 3 pattern for this, if any? The project needs to have some way to do the following: svn co myproject cd myproject make where 'make' creates a Zope 3 installation, and downloads all the eggs listed as requirements for this project from the net, and installs them so that the Zope 3 instance actually picks them up. In particular, are there any ideas of how the -configure.zcml and -meta.zcml files would end up being generated and installed in package-includes? Eggs do not provide for this directly, but perhaps there are some ideas about Zope 3 specific eggs that do? Regards, Martijn ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
Re: [Zope3-dev] eggs for Zope 3 extensions
On Tue, Apr 04, 2006 at 02:51:37PM +0200, Martijn Faassen wrote: | where 'make' creates a Zope 3 installation, and downloads all the eggs | listed as requirements for this project from the net, and installs them | so that the Zope 3 instance actually picks them up. I think you would give a argument to easy_install to install the eggs in `INSTANCE_HOME/lib/python`. | In particular, are there any ideas of how the -configure.zcml and | -meta.zcml files would end up being generated and installed in | package-includes? Eggs do not provide for this directly, but perhaps | there are some ideas about Zope 3 specific eggs that do? I think those would be handled by 'entry points'. -- Sidnei da Silva Enfold Systems, Inc. http://enfoldsystems.com ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
Re: [Zope3-dev] eggs for Zope 3 extensions
Sidnei da Silva wrote: On Tue, Apr 04, 2006 at 02:51:37PM +0200, Martijn Faassen wrote: | where 'make' creates a Zope 3 installation, and downloads all the eggs | listed as requirements for this project from the net, and installs them | so that the Zope 3 instance actually picks them up. I think you would give a argument to easy_install to install the eggs in `INSTANCE_HOME/lib/python`. Right, I can make it work, I just wondered if there was some canonical way. :) | In particular, are there any ideas of how the -configure.zcml and | -meta.zcml files would end up being generated and installed in | package-includes? Eggs do not provide for this directly, but perhaps | there are some ideas about Zope 3 specific eggs that do? I think those would be handled by 'entry points'. Looking them up... As far as I understand them, Zope 3 would need to be able to understand entry points before I could use these in a project that uses Zope 3, right? Regards, Martijn ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
[Zope3-dev] Re: SVN: Zope3/trunk/ Merge bug fixes to the FTP server from the mkerrin-remove_trial_tests
Michael Kerrin wrote: Modified: Zope3/trunk/test.py === --- Zope3/trunk/test.py 2006-04-04 08:46:11 UTC (rev 66372) +++ Zope3/trunk/test.py 2006-04-04 10:02:50 UTC (rev 66373) @@ -57,6 +57,9 @@ # Get rid of twisted.conch.ssh warning warnings.filterwarnings( 'ignore', 'PyCrypto', RuntimeWarning, 'twisted[.]conch[.]ssh') +warnings.filterwarnings( +'ignore', '', DeprecationWarning, +'(zope[.]app[.]twisted[.]ftp|twisted[.]test[.]test_ftp)') result = testrunner.run(defaults) Michael, this last filter seems to ignore more than you really want. I'm curious, which DeprecationWarnings are you trying to ignore anyways. I couldn't find any in zope.app.twisted.ftp or twisted.test.test_ftp... Philipp ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
[Zope3-dev] eggifying zc.resourcelibrary, zc.table and others
Hi there, * does anyone have any objections if I make eggs for various zc.* packages? In svn, this involves adding a setup.py to these packages, and to add a __init__.py to the zc package that they contain (which contains some egg-specific stuff). * the setup.py I'll create will only work with setuptools installed; is this a problem? * what email address should I list for the author of some zc package? this is information that will appear in the cheeseshop. * to get the full egg experience, I'd like to have them uploaded to the cheeseshop. I could do this myself, but they're not my packages. Can I? or does someone else want to do this? I'll of course gladly give admin rights for these packages to the real creators. Regards, Martijn ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
[Zope3-dev] Guess who
Hello! Have a look at this. This company is giving away ipods. http://giftresource321.com/?r=cTE0BIEFQQRIBGQKAykMi=gmailz=1tc=2 What do you think? Talk soon. ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
Re: [Zope3-dev] eggs for Zope 3 extensions
On 4/4/06, Martijn Faassen [EMAIL PROTECTED] wrote: Another question about eggs: I assume that Zope 3 extensions at present cannot be zipped, as Zope needs access to their zcml files. Correct? Extensions that contain ZCML or other file-based resources (page templates, ZConfig schema components) cannot currently be used directly from a ZIP file. I started work to support that on the zipimport-branch, but didn't have time to finish the proposal that went with that. That branch allowed ZCML and page templates to be loaded from within ZIP files, and support code to allow packages to refer to their own resources abstractly, even without the egg-support code being available. The changes on that branch work with ZIP-based imports generally, and are not specific to eggs (but I think they work fine with eggs). There's a wiki page about this at http://dev.zope.org/Zope3/ZIPImportSupportForZope3 -Fred -- Fred L. Drake, Jr.fdrake at gmail.com Don't let schooling interfere with your education. -- Mark Twain ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
Re: [Zope3-dev] eggifying zc.resourcelibrary, zc.table and others
On Apr 4, 2006, at 12:38 PM, Martijn Faassen wrote: Hi there, * does anyone have any objections if I make eggs for various zc.* packages? In svn, this involves adding a setup.py to these packages, and to add a __init__.py to the zc package that they contain (which contains some egg-specific stuff). Sounds great! (I assume the __init__ changes won't cause problems without setuptools around). Jim points out that Nathan Yergler has a script that can generate eggs from zpkg data; you might or might not find that to be easier. It's less of an obvious win with these packages that have little or no zpkg metadata already, but it might still be quicker in some cases (no idea myself). * the setup.py I'll create will only work with setuptools installed; is this a problem? Not from us. You'd maybe get even more warm fuzzies from people by making it not require setuptools, but that limitation doesn't bother us. * what email address should I list for the author of some zc package? this is information that will appear in the cheeseshop. zope3-dev@zope.org * to get the full egg experience, I'd like to have them uploaded to the cheeseshop. I could do this myself, but they're not my packages. Can I? or does someone else want to do this? I'll of course gladly give admin rights for these packages to the real creators. Jim also suggests the new, as-of-this-moment-no-longer-secret http:// download.zope.org/distribution/ as a possible location instead. All Zope committers have the appropriate privileges to scp to this directory. That's where he will be doing his egg work, at least until he thinks we have figured out the best way to make Zope eggs. It can be used a setuptools source. If you want to use the cheeseshop anyway, that's ok too. Thanks Gary ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
[Zope3-dev] Re: eggifying zc.resourcelibrary, zc.table and others
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Gary Poster wrote: On Apr 4, 2006, at 12:38 PM, Martijn Faassen wrote: Hi there, * does anyone have any objections if I make eggs for various zc.* packages? In svn, this involves adding a setup.py to these packages, and to add a __init__.py to the zc package that they contain (which contains some egg-specific stuff). Sounds great! (I assume the __init__ changes won't cause problems without setuptools around). There is supposed to be a dance in Python itself for declaring a namespace package. Framkly, anybody who wants to play along *without* setuptools installed has rocks in their heads: distutils is too wanky to use by itself for complicated cases, and setuptools makes it just barely tolerable. Jim points out that Nathan Yergler has a script that can generate eggs from zpkg data; you might or might not find that to be easier. It's less of an obvious win with these packages that have little or no zpkg metadata already, but it might still be quicker in some cases (no idea myself). * the setup.py I'll create will only work with setuptools installed; is this a problem? Not from us. You'd maybe get even more warm fuzzies from people by making it not require setuptools, but that limitation doesn't bother us. * what email address should I list for the author of some zc package? this is information that will appear in the cheeseshop. zope3-dev@zope.org * to get the full egg experience, I'd like to have them uploaded to the cheeseshop. I could do this myself, but they're not my packages. Can I? or does someone else want to do this? I'll of course gladly give admin rights for these packages to the real creators. Jim also suggests the new, as-of-this-moment-no-longer-secret http:// download.zope.org/distribution/ as a possible location instead. All Zope committers have the appropriate privileges to scp to this directory. That's where he will be doing his egg work, at least until he thinks we have figured out the best way to make Zope eggs. It can be used a setuptools source. Note that I am actively working in that directory on eggifying a number of the top-level zope packages in released verisons (typically in the flavors which shipped with ZopeX3.0.0 and Zope3.2). If you want to use the cheeseshop anyway, that's ok too. - -- === Tres Seaver +1 202-558-7113 [EMAIL PROTECTED] Palladion Software Excellence by Designhttp://palladion.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFEMsG5+gerLs4ltQ4RAq4rAKDCwrsDs/nmkJVv7ASzuhLsa81LOQCeIt6/ mBewTTCRqCgcK5EjiAO039U= =GITX -END PGP SIGNATURE- ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
