Re: [Zope3-dev] eggifying zc.resourcelibrary, zc.table and others
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). I'll try to verify this. Note that this __init__.py change will occur in an __init__.py that currently doesn't in fact *exist* in these packages (in the 'zc' directory). Presumably you don't need it now in deployment. 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). Thanks for the reference to that script. I'm going to avoid zpkg if I can though, and I think you're right in that there's no ZPKG data to speak of for these extensions. * 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. Okay, good. Warm fuzzies are nice, but I won't worry too much about that. [snip] * 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. Okay, that's interesting - I'll investigate this ex-secret location. :) If you want to use the cheeseshop anyway, that's ok too. Okay, I'll take a look around and decide what makes sense. Thanks! 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] eggifying zc.resourcelibrary, zc.table and others
Gary Poster wrote: [snip] 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. I'm trying to find a way to scp the zc.resourcelibrary egg into it, but I get permission denied when I scp, possibly because I don't know which directory 'distribution' really is on the actual system. 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: eggifying zc.resourcelibrary, zc.table and others
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Martijn Faassen wrote:
* 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.
Okay, good. Warm fuzzies are nice, but I won't worry too much about that.
There is some support for kickstarting an eggifying project. E.g.:
$ export ZSVN=svn+ssh://svn.zope.org/repos/main
$ svn cp -m Eggify $ZSVN/productsupport/trunk/project-template \
$ZSVN/zope.foopackage
The top-level 'zope.foopackage' will have a skeleton 'trunk', plus empty
'branches' and 'tags':
$ svn co $ZSVN/zope.foopackage/trunk zope.foopackage-trunk
$ cd zope.foopackage-trunk
$ ls -1
CHANGES.txt
develop.py
INSTALL.txt
README.txt
setup.cfg.in
setup.py
src
test.py
workspace
The text files are templates, and should be edited to fit.
The 'develop.py' script will set up a local 'bin' and 'lib' directory
inside your checkout, and try to install dependencies as specified in
'setup.py' and 'setup.cfg' (which it copies from 'setup.cfg.in'). It
also jams the Zope egg URL into 'setup.cfg'.
I usually run 'setup.py develop' afterwards, as it is better at
finding all the dependencies:
$ PYTHONPATH=lib /path/to/your/python setup.py develop
The 'zope.testing' package is supposed to be pulled in during that
bootstrapping, but often seems missed (I haven't yet figured out
why). Running the local 'easy_install' does the trick:
$ PYTHONPATH=lib /path/to/your/python bin/easy_install \
zope.testing
The 'src/zope' directory is intended to contain a 'svn:externals'
pointer to the canonical location of the source (we may eventually
reverse this, and make the main Zope tree point out at the top-level
package directories). E.g.
$ svn propedit svn:externals src/zope
#... add your external here
$ svn up
# ... fetches your external.
That 'src/zope' directory also contains setuptools / pkgutil
boilerplat namespace __init__.py:
$ cat src/zope/__init__.py
# namespace package boilerplate
try:
__import__('pkg_resources').declare_namespace(__name__)
except ImportError, e:
from pkgutil import extend_path
__path__ = extend_path(__path__, __name__)
The 'test.py' needs to be edited to point to your package. At that
point, you should have all your package's dependencies installed
(assuming that you named them in 'setup.py'), and should be able to run
the tests using your local eggs:
$ PYTHONPATH=lib /path/to/your/python test.py
Nathan, Jim, please correct any mistakes you see.
Tres.
- --
===
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
iD8DBQFEM7tX+gerLs4ltQ4RArrjAJ9GAW9klbLC9n4ZUdcmbvvsrSDQCgCgsz+l
SojySIyJZEGgMVercdKH8Uk=
=FdIS
-END PGP SIGNATURE-
___
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
Tres Seaver wrote: * 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. Okay, good. Warm fuzzies are nice, but I won't worry too much about that. There is some support for kickstarting an eggifying project. E.g.: $ export ZSVN=svn+ssh://svn.zope.org/repos/main $ svn cp -m Eggify $ZSVN/productsupport/trunk/project-template \ $ZSVN/zope.foopackage Note that such a svn cp will make it quite painful to dump the repository later on using svadmin dump and then filtering the dump using svndumpfilter to keep only this package. (We've been bitten by that.) I'd suggest doing instead a svn export of the project-template, then svn import as your new package. Florent -- Florent Guillaume, Nuxeo (Paris, France) Director of RD +33 1 40 33 71 59 http://nuxeo.com [EMAIL PROTECTED] ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
[Zope3-dev] zope.schema sets
zope.schema.Set currently only accepts sets.Set objects. Anyone object if I change zope.schema.Set to accept py2.4 builtin sets, or if I add a zope.schema.FrozenSet? I don't see any reasonable objections, so I'll probably check this in within a couple of hours if there is no dissent. Gary ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
Re: [Zope3-dev] Re: eggifying zc.resourcelibrary, zc.table and others
On Apr 5, 2006, at 11:03 AM, Martijn Faassen wrote: Tres Seaver wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Martijn Faassen wrote: Gary Poster wrote: [snip] 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. I'm trying to find a way to scp the zc.resourcelibrary egg into it, but I get permission denied when I scp, possibly because I don't know which directory 'distribution' really is on the actual system. /var/www/download.zope.org/distribution Hm, now I get this from scp: Command not accepted and verbose info says: debug1: Sending command: scp -v -t /var/www/download.zope.org/ distribution debug1: Entering interactive session. debug1: fd 0 clearing O_NONBLOCK Command not accepted Apologies for the confusion, Martijn. I checked with Jim. The procedure that Tres described is only for people who have direct access to the machine. The intended use is similar to the following: $ touch gary_test.txt $ scp gary_test.txt [EMAIL PROTECTED]:/distribution/ gary_test.txt 100%0 0.0KB/s 00:00 Any Zope contributor should have privileges to add to this directory (but not to sub directories). Gary ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
[Zope3-dev] ILayer deprecation warning on trunk
Looks like it only appears if you run the functional tests separately. $ ~/z4i/bin/python test.py -f Running zope.app.testing.functional.Functional tests: Set up zope.app.testing.functional.Functional in 5.218 seconds. /home/gary/z4i/var/src/zope3/src/zope/app/apidoc/ifacemodule/ ifacemodule.py:78: DeprecationWarning: ILayer: The zope.publisher.interfaces.ILayer interface has been deprecated and will go away in Zope 3.5. iface = getattr(mod, parts[-1], default) Gary ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
Re: [Zope3-dev] Re: [Checkins] SVN: Zope3/trunk/src/zope/app/form/browser/itemswidgets.py The label for the list items widgets could not point to the field, because
Gary Poster wrote: FWIW, I seem to recall that IE doesn't handle form fields whose `id` and `name` are different very well. Can anyone verify, from memory or otherwise? I can verify that it (at least) once had that problem. I've been bitten by it within the last two years. I don't know about the current status, so voodoo coding reigns. :) -- Benji York Senior Software Engineer Zope Corporation ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
Re: [Zope3-dev] Re: [Checkins] SVN: Zope3/trunk/src/zope/app/form/browser/itemswidgets.py The label for the list items widgets could not point to the field, because
Hmm, I'm inclined to doubt whether IE expects the id and name attributes to be identical. Distinct values for id and name shouldn't be a problem, afaik. See http://msdn.microsoft.com/workshop/author/forms/formsoverview.asp - Kamal -- Kamal Gill - [EMAIL PROTECTED] http://www.adaptivewave.com Content Management Made Simple On Apr 5, 2006, at 1:03 PM, Gary Poster wrote: On Apr 5, 2006, at 3:42 PM, Stephan Richter wrote: Modified: Zope3/trunk/src/zope/app/form/browser/itemswidgets.py === --- Zope3/trunk/src/zope/app/form/browser/itemswidgets.py 2006-04-05 19:34:34 UTC (rev 66578) +++ Zope3/trunk/src/zope/app/form/browser/itemswidgets.py 2006-04-05 19:42:44 UTC (rev 66579) @@ -518,6 +518,7 @@ rendered_items = self.renderItems(value) return renderElement(self.tag, name=self.name + ':list', + id=self.name, multiple='multiple', size=self.size, contents=\n.join(rendered_items), FWIW, I seem to recall that IE doesn't handle form fields whose `id` and `name` are different very well. Can anyone verify, from memory or otherwise? Gary ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/kamal.gill% 40adaptivewave.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] Re: [Checkins] SVN: Zope3/trunk/src/zope/app/form/browser/itemswidgets.py The label for the list items widgets could not point to the field, because
On Apr 5, 2006, at 4:14 PM, Kamal Gill wrote: Hmm, I'm inclined to doubt whether IE expects the id and name attributes to be identical. Distinct values for id and name shouldn't be a problem, afaik Wait, someone used shouldn't be a problem in reference to IE? :-) As Benji said, this isn't idle: we've encountered some pain that makes me bring this up. A quick Google search didn't come up with any confirmation, though, so, without further backup, I'm happy to let this lie. 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: [Checkins] SVN: Zope3/trunk/src/zope/app/form/browser/itemswidgets.py The label for the list items widgets could not point to the field, because
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Gary Poster wrote: On Apr 5, 2006, at 4:14 PM, Kamal Gill wrote: Hmm, I'm inclined to doubt whether IE expects the id and name attributes to be identical. Distinct values for id and name shouldn't be a problem, afaik Wait, someone used shouldn't be a problem in reference to IE? :-) As Benji said, this isn't idle: we've encountered some pain that makes me bring this up. A quick Google search didn't come up with any confirmation, though, so, without further backup, I'm happy to let this lie. I'm pretty sure that at least some flavors of IE were fussy about 'id' attributes which were not valid according the HTML DTD's; I therefore quit giving form fields an 'id' attribute long ago, just because I couldn't keep it straight. Tres. - -- === 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 iD8DBQFENFJc+gerLs4ltQ4RApmfAKCFRB3tvLCbNXRarJ96hoxeGTCvagCeOHTc /GpIl9O6n4uAbJ7r5HDMeLo= =jcyG -END PGP SIGNATURE- ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
Re: [Zope3-dev] Re: [Checkins] SVN: Zope3/trunk/src/zope/app/form/browser/itemswidgets.py The label for the list items widgets could not point to the field, because
Tres Seaver wrote: I'm pretty sure that at least some flavors of IE were fussy about 'id' attributes which were not valid according the HTML DTD's; I therefore quit giving form fields an 'id' attribute long ago, just because I couldn't keep it straight. Then you can't have a label for that field that refers to it via id. Sometimes you just can't win. -- Benji York Senior Software Engineer Zope Corporation ___ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com
