[Zope] calling javascript method from dtml method
Hi Is there any way to call a javascript method from a dtml method somewhere in the body of it? The method cam be in a different js file which is preferable or in the dtml method if there is no other way, from what I found on the web it looks like I can't but I want to make sure that I didn't miss anything ___ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )
Re: [Zope] calling javascript method from dtml method
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 15.03.2009 9:09 Uhr, Dvir Bar-lev wrote: Hi Is there any way to call a javascript method from a dtml method somewhere in the body of it? The method cam be in a different js file which is preferable or in the dtml method if there is no other way, from what I found on the web it looks like I can’t but I want to make sure that I didn’t miss anything This question makes no sense. DTML=server-side, JS=browser-side. - -aj -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkm8uHkACgkQCJIWIbr9KYwudQCgsmSmyVr+DKWqktqIvjc6ALxU 43gAn1vIRNVATDnu4U7kNK3KsPYWTMI2 =speP -END PGP SIGNATURE- begin:vcard fn:Andreas Jung n:Jung;Andreas org:ZOPYX Ltd. Co. KG adr;quoted-printable:;;Charlottenstr. 37/1;T=C3=BCbingen;;72070;Germany email;internet:i...@zopyx.com title:CEO tel;work:+49-7071-793376 tel;fax:+49-7071-7936840 tel;home:+49-7071-793257 x-mozilla-html:FALSE url:www.zopyx.com version:2.1 end:vcard ___ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )
Re: [Zope] calling javascript method from dtml method
Just put a dtml-var x where x is a dtml document with your javascript in it. Even though it should be in the header it still seems to work 2009/3/15 Dvir Bar-lev dvi...@puresight.com Hi Is there any way to call a javascript method from a dtml method somewhere in the body of it? The method cam be in a different js file which is preferable or in the dtml method if there is no other way, from what I found on the web it looks like I can’t but I want to make sure that I didn’t miss anything ___ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev ) ___ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )
[Zope-dev] [Zope 2.12] distribution broken
In order to test my external 'ZClasses' implementation,
I easy_installed Zope2 (about 1 hour ago) -- but unfortunately,
the distribution is broken: version conflict zope.component 3.5.1 versus
zope.component 3.6.0.
Maybe, the eggification of Zope2 will not turn out to be an advantage --
at least not when installed via easy_install from PyPI (i.e. without
a KnownGoodSet index)
(zcpython)newdm: mkzopeinstance
Traceback (most recent call last):
File /home/dieter/ZopeSVN/ZClasses/zcpython/bin/mkzopeinstance, line 5, in ?
from pkg_resources import load_entry_point
File
/home/dieter/ZopeSVN/ZClasses/zcpython/lib/python2.5/site-packages/setuptools-0.6c7-py2.5.egg/pkg_resources.py,
line 2564, in ?
for dist in working_set.resolve(
File
/home/dieter/ZopeSVN/ZClasses/zcpython/lib/python2.5/site-packages/setuptools-0.6c7-py2.5.egg/pkg_resources.py,
line 528, in resolve
raise VersionConflict(dist,req) # XXX put more info here
pkg_resources.VersionConflict: (zope.component 3.5.1
(/home/dieter/ZopeSVN/ZClasses/zcpython/lib/python2.5/site-packages/zope.component-3.5.1-py2.5.egg),
Requirement.parse('zope.component=3.6.0'))
--
Dieter
___
Zope-Dev maillist - Zope-Dev@zope.org
http://mail.zope.org/mailman/listinfo/zope-dev
** No cross posts or HTML encoding! **
(Related lists -
http://mail.zope.org/mailman/listinfo/zope-announce
http://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] [Zope 2.12] how to test products/packages?
The Zope 2.12 documention tells that the test command was removed from zopectl. test was a convenient way to test products and packages in the context of the instance. How is this use case now supported? -- Dieter ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] [Zope 2.12] Packaging weakness
The documentation on PyPI tells to look into doc/INSTALL.txt to find installation instructions. However, doc is not installed by the standard easy_install process. Therefore, it is not so easy to find it. Relevant documentation should be installed by the standard easy_install process (it should be part of the installed egg). I will file a bug report. Minor note: the installation instructions are actually in INSTALL.rst not INSTALL.txt. -- Dieter ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] [Zope 2.12] distribution broken
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 15.03.2009 8:28 Uhr, Dieter Maurer wrote:
In order to test my external 'ZClasses' implementation,
I easy_installed Zope2 (about 1 hour ago) -- but unfortunately,
the distribution is broken: version conflict zope.component 3.5.1 versus
zope.component 3.6.0.
Maybe, the eggification of Zope2 will not turn out to be an advantage --
at least not when installed via easy_install from PyPI (i.e. without
a KnownGoodSet index)
(zcpython)newdm: mkzopeinstance
Traceback (most recent call last):
File /home/dieter/ZopeSVN/ZClasses/zcpython/bin/mkzopeinstance, line 5,
in ?
from pkg_resources import load_entry_point
File
/home/dieter/ZopeSVN/ZClasses/zcpython/lib/python2.5/site-packages/setuptools-0.6c7-py2.5.egg/pkg_resources.py,
line 2564, in ?
for dist in working_set.resolve(
File
/home/dieter/ZopeSVN/ZClasses/zcpython/lib/python2.5/site-packages/setuptools-0.6c7-py2.5.egg/pkg_resources.py,
line 528, in resolve
raise VersionConflict(dist,req) # XXX put more info here
pkg_resources.VersionConflict: (zope.component 3.5.1
(/home/dieter/ZopeSVN/ZClasses/zcpython/lib/python2.5/site-packages/zope.component-3.5.1-py2.5.egg),
Requirement.parse('zope.component=3.6.0'))
Try using the traditional
python bootstrap.py
bin/buildout
approach.
easy_install support wasn't the primary goal for alpha 1 and other
things have to be sorted out.
In addition: setuptools 0.6c7 is pretty old and known to be broken in
some ways.
- -aj
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAkm8srsACgkQCJIWIbr9KYyCVACeNb+gfNFZF5/fdvWcpYhnj5oJ
4K8An3TFAYK87pmRsjETyuBybxHtUGqQ
=kL6p
-END PGP SIGNATURE-
begin:vcard
fn:Andreas Jung
n:Jung;Andreas
org:ZOPYX Ltd. Co. KG
adr;quoted-printable:;;Charlottenstr. 37/1;T=C3=BCbingen;;72070;Germany
email;internet:i...@zopyx.com
title:CEO
tel;work:+49-7071-793376
tel;fax:+49-7071-7936840
tel;home:+49-7071-793257
x-mozilla-html:FALSE
url:www.zopyx.com
version:2.1
end:vcard
___
Zope-Dev maillist - Zope-Dev@zope.org
http://mail.zope.org/mailman/listinfo/zope-dev
** No cross posts or HTML encoding! **
(Related lists -
http://mail.zope.org/mailman/listinfo/zope-announce
http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] [Zope 2.12] how to test products/packages?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 15.03.2009 8:31 Uhr, Dieter Maurer wrote: The Zope 2.12 documention tells that the test command was removed from zopectl. Have to investigate that. test was a convenient way to test products and packages in the context of the instance. How is this use case now supported? Go with the buildout approach and use the alltests.cfg for testing support (see alltests.cfg). Means: work with a SVN checkout. - -aj - -- ZOPYX Ltd. Co. KG - Charlottenstr. 37/1 - 72070 Tübingen - Germany Web: www.zopyx.com - Email: i...@zopyx.com - Phone +49 - 7071 - 793376 Registergericht: Amtsgericht Stuttgart, Handelsregister A 381535 Geschäftsführer/Gesellschafter: ZOPYX Limited, Birmingham, UK - E-Publishing, Python, Zope Plone development, Consulting -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkm8s+0ACgkQCJIWIbr9KYzEXwCgyo8SjYiDiHBJbucpaf/xbaWR TaoAoLQ0b5W7+oiBQW2EI+PW0O0Niihr =vJNj -END PGP SIGNATURE- begin:vcard fn:Andreas Jung n:Jung;Andreas org:ZOPYX Ltd. Co. KG adr;quoted-printable:;;Charlottenstr. 37/1;T=C3=BCbingen;;72070;Germany email;internet:i...@zopyx.com title:CEO tel;work:+49-7071-793376 tel;fax:+49-7071-7936840 tel;home:+49-7071-793257 x-mozilla-html:FALSE url:www.zopyx.com version:2.1 end:vcard ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] [Zope 2.12] Packaging weakness
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 15.03.2009 8:36 Uhr, Dieter Maurer wrote: The documentation on PyPI tells to look into doc/INSTALL.txt to find installation instructions. However, doc is not installed by the standard easy_install process. Therefore, it is not so easy to find it. Relevant documentation should be installed by the standard easy_install process (it should be part of the installed egg). All related docs are available from our new place: http://docs.zope.org/ - -aj -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkm8tKkACgkQCJIWIbr9KYyS1QCg4EcHdYFA190MYS97aGEX2hCo ffAAnRL7wOgxOG0IWtfXQSNzD6SRxYI0 =AtSf -END PGP SIGNATURE- begin:vcard fn:Andreas Jung n:Jung;Andreas org:ZOPYX Ltd. Co. KG adr;quoted-printable:;;Charlottenstr. 37/1;T=C3=BCbingen;;72070;Germany email;internet:i...@zopyx.com title:CEO tel;work:+49-7071-793376 tel;fax:+49-7071-7936840 tel;home:+49-7071-793257 x-mozilla-html:FALSE url:www.zopyx.com version:2.1 end:vcard ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] Dependencies on zope.app.appsetup
Hi there. One of most annoying dependencies is the zope.app.appsetup package. Some packages, like zope.session depend on it just to provide boostrap setup for using these packages in context of zope3, the application server, however, they can be greatly used without it, so this is really awful dependency. I saw that, on last sprint, the subscriber for error reporting utility was moved from zope.error to zope.app.appsetup, so zope.error could lose the dependency on zope.app.appsetup. So, the first question is: do we want to move all subscribers like that? It doesn't seem like a best solution though, because then zope.app.appsetup should depend on all those packages, like zope.session. :-/ The problem is that the bootstrap code in zope.app.appsetup is really zope3, the application-specific, so it uses root folders, persistent site managers, site management containers, ZopePublication.root_name, and so on. The code itself is okay, because it provides an easy way to setup misc. components for the zope3 application server, but still it's a problem, because it's probably impossible to refactor it in a application-independent way (until we provide some cool pluggable application bootstrapping mechanism, which is probably will become too complex and not needed/used by most application developers). So, the general question is where should we move the bootstrap setup code? Or, alternatively, we could just leave it in place, but greatly separate it from another package components and provide zope.app.appsetup as an extra dependency (sigh...). Ideas? -- WBR, Dan Korostelev ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] Zope Tests: 6 OK
Summary of messages to the zope-tests list. Period Sat Mar 14 12:00:00 2009 UTC to Sun Mar 15 12:00:00 2009 UTC. There were 6 messages: 6 from Zope Tests. Tests passed OK --- Subject: OK : Zope-2.10 Python-2.4.6 : Linux From: Zope Tests Date: Sat Mar 14 21:21:06 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-March/011271.html Subject: OK : Zope-2.11 Python-2.4.6 : Linux From: Zope Tests Date: Sat Mar 14 21:23:12 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-March/011272.html Subject: OK : Zope-trunk Python-2.4.6 : Linux From: Zope Tests Date: Sat Mar 14 21:25:12 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-March/011273.html Subject: OK : Zope-trunk Python-2.5.4 : Linux From: Zope Tests Date: Sat Mar 14 21:27:13 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-March/011274.html Subject: OK : Zope-trunk-alltests Python-2.4.6 : Linux From: Zope Tests Date: Sat Mar 14 21:29:14 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-March/011275.html Subject: OK : Zope-trunk-alltests Python-2.5.4 : Linux From: Zope Tests Date: Sat Mar 14 21:31:14 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-March/011276.html ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] [Checkins] SVN: zope.app.component/trunk/setup.py set missing minimum version
Am 15.03.2009 um 04:25 schrieb Stephan Richter: On Saturday 14 March 2009, Michael Howitz wrote: Log message for revision 98113: set missing minimum version Changed: U zope.app.component/trunk/setup.py -=- Modified: zope.app.component/trunk/setup.py = --- zope.app.component/trunk/setup.py 2009-03-14 19:56:47 UTC (rev 98112) +++ zope.app.component/trunk/setup.py 2009-03-14 20:14:47 UTC (rev 98113) @@ -78,7 +78,7 @@ 'zope.interface', 'zope.lifecycleevent', 'zope.location3.4.0b1', - 'zope.publisher', + 'zope.publisher=3.6.0', 'zope.schema', 'zope.security', 'zope.traversing', Please, please, please no versions in setup.py. But it is impossible to use zope.app.component together with an older version of zope.publisher: an ImportError is raised in zope/app/ component/__init__.py otherwise. I upgraded zope.app.component in a project of mine and it broke because I did not upgrade zope.publisher the same time. With the version information in setup.py I would have known what's the minimum version of zope.publisher I have to use. Yours sincerely, -- Michael Howitz · m...@gocept.com · software developer gocept gmbh co. kg · forsterstraße 29 · 06112 halle (saale) · germany http://gocept.com · tel +49 345 1229889 8 · fax +49 345 1229889 1 Zope and Plone consulting and development ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] XML-RPC does not work under the paster process
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 When using paste.httpserver instead of twisted.wsgi server zope.publisher.xmlrpc.XMLRPCRequest.processInputs() hangs when reading 0 Bytes from the request (wsgi.input socket._fileobject object). As i found the zope.publisher.http.HTTPInputStream.readlines() signature was changed 3 years ago from readlines(self, hint=None) to readlines(self, hint=0) http://svn.zope.org/Zope3/trunk/src/zope/publisher/http.py?rev=66941r1=66940r2=66941 Do you think we could revert the change? Bugs reported: zopeproject: https://bugs.launchpad.net/zope3/+bug/283089 grokproject: https://bugs.launchpad.net/grok/+bug/332063 Regards Michael - -- http://blog.d2m.at http://planetzope.org -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFJvRDVl0uAvQJUKVYRAuMZAJ0eZBKjoInmx5CigwgjUf2gDpQyXQCfTBh5 IVbnn5i1v5WAwGPJxUJWCZs= =+cQ+ -END PGP SIGNATURE- ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] [Zope3-checkins] [Checkins] SVN: zope.app.component/trunk/setup.py set missing minimum version
Previously Stephan Richter wrote: On Saturday 14 March 2009, Michael Howitz wrote: Log message for revision 98113: set missing minimum version Changed: U zope.app.component/trunk/setup.py -=- Modified: zope.app.component/trunk/setup.py === --- zope.app.component/trunk/setup.py 2009-03-14 19:56:47 UTC (rev 98112) +++ zope.app.component/trunk/setup.py 2009-03-14 20:14:47 UTC (rev 98113) @@ -78,7 +78,7 @@ 'zope.interface', 'zope.lifecycleevent', 'zope.location3.4.0b1', - 'zope.publisher', + 'zope.publisher=3.6.0', 'zope.schema', 'zope.security', 'zope.traversing', Please, please, please no versions in setup.py. If the package does not work with an older version of zope.publisher than imho that version restriction *has* to be in setup.py. Wichert. -- Wichert Akkerman wich...@wiggy.netIt is simple to make things. http://www.wiggy.net/ It is hard to make things simple. ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] [Zope 2.12] how to test products/packages?
Andreas Jung wrote at 2009-3-15 08:53 +0100: On 15.03.2009 8:31 Uhr, Dieter Maurer wrote: The Zope 2.12 documention tells that the test command was removed from zopectl. Have to investigate that. test was a convenient way to test products and packages in the context of the instance. How is this use case now supported? Go with the buildout approach and use the alltests.cfg for testing support (see alltests.cfg). Means: work with a SVN checkout. I do not want to test Zope, I want to test *MY* Zope based components. -- Dieter ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] [Zope 2.12] how to test products/packages?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 15.03.2009 18:27 Uhr, Dieter Maurer wrote: Andreas Jung wrote at 2009-3-15 08:53 +0100: On 15.03.2009 8:31 Uhr, Dieter Maurer wrote: The Zope 2.12 documention tells that the test command was removed from zopectl. Have to investigate that. test was a convenient way to test products and packages in the context of the instance. How is this use case now supported? Go with the buildout approach and use the alltests.cfg for testing support (see alltests.cfg). Means: work with a SVN checkout. I do not want to test Zope, I want to test *MY* Zope based components. Then write *your* dieter.cfg containing [buildout] extends = buildout.cfg parts += alltests [alltests] recipe = zc.recipe.testrunner eggs = dm.foo.bar and run buildout -c dieter.cfg and later bin/alltests - -aj -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkm9PKIACgkQCJIWIbr9KYxXoQCgr8j6/YMeP/N/OUX35Zz862ov pRoAoNqOu74upBaf20esiozNajq7+U/U =X1wQ -END PGP SIGNATURE- begin:vcard fn:Andreas Jung n:Jung;Andreas org:ZOPYX Ltd. Co. KG adr;quoted-printable:;;Charlottenstr. 37/1;T=C3=BCbingen;;72070;Germany email;internet:i...@zopyx.com title:CEO tel;work:+49-7071-793376 tel;fax:+49-7071-7936840 tel;home:+49-7071-793257 x-mozilla-html:FALSE url:www.zopyx.com version:2.1 end:vcard ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] [Zope 2.12] Packaging weakness
Andreas Jung wrote at 2009-3-15 08:56 +0100: ... On 15.03.2009 8:36 Uhr, Dieter Maurer wrote: The documentation on PyPI tells to look into doc/INSTALL.txt to find installation instructions. However, doc is not installed by the standard easy_install process. Therefore, it is not so easy to find it. Relevant documentation should be installed by the standard easy_install process (it should be part of the installed egg). All related docs are available from our new place: http://docs.zope.org/ Hint: then the PyPI page should get considerable overhaul: * It should point to http://docs.zope.org;. Instead, it currently points to http://www.zope.org/Documentation/; where no current installation instructions can be found * It should indicate that unlike natural expectation, the packagers of the Zope2 egg decided to put the installation instructions not into the eggs but instead on the internet. And as this is a new place, a link there would be appropriate. * Maybe, it should warn people agaist easy_installing Zope2 -- as the developers did not yet care much about this distribution way and the installed egg may not work. -- Dieter ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] [Fwd: [Bug 343079] [NEW] Broken distribution (2009-03-15)]
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 - Original Message Subject: [Bug 343079] [NEW] Broken distribution (2009-03-15) Date: Sun, 15 Mar 2009 07:42:00 - From: dmaurer die...@handshake.de Reply-To: Bug 343079 343...@bugs.launchpad.net To: tsea...@palladion.com References: 20090315074200.12457.19313.malone...@potassium.ubuntu.com Public bug reported: The current (2009-03-12) PyPI distribution for Zope2 2.12.0a1 is broken. 'easy_install'ing it leads to version conflicts for 'zope.component' (3.5.1 versus 3.6.0) in the call of 'mkzopeinstance'. ** Affects: zope2 Importance: Undecided Status: New The breakage is due to the release of the new zope.prinipalregistry egg. We should probably manage a Zope2 indes and tell people to use it when running easy_install, because PyPI is not suitable for the task given setuptools' incremental requirements discovery design. Tres. - -- === Tres Seaver +1 540-429-0999 tsea...@palladion.com Palladion Software Excellence by Designhttp://palladion.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFJvT4A+gerLs4ltQ4RAo0LAJ4q83+Ua0hEQUb5ecOhU8IufTcXnQCfV9wd 6eFVN+pmQTi0CW+ki8f+f8M= =zsxY -END PGP SIGNATURE- ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] [Zope 2.12] how to test products/packages?
Hanno Schlichting wrote at 2009-3-15 11:10 +0100: Dieter Maurer wrote: The Zope 2.12 documention tells that the test command was removed from zopectl. test was a convenient way to test products and packages in the context of the instance. How is this use case now supported? The normal way to develop anything in the Zope world is based on zc.buildout today. You can define a testrunner like this: I do not have good experience with buildout and will try to avoid it. I will probably resurrect the old way to run tests in the same way I will resurrect ZClasses (i.e. though an externally maintained PyPI package). -- Dieter ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Dependencies on zope.app.appsetup
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Dan Korostelev wrote:
Hi there.
One of most annoying dependencies is the zope.app.appsetup package.
Some packages, like zope.session depend on it just to provide
boostrap setup for using these packages in context of zope3, the
application server, however, they can be greatly used without it, so
this is really awful dependency.
I saw that, on last sprint, the subscriber for error reporting utility
was moved from zope.error to zope.app.appsetup, so zope.error could
lose the dependency on zope.app.appsetup. So, the first question is:
do we want to move all subscribers like that? It doesn't seem like a
best solution though, because then zope.app.appsetup should depend on
all those packages, like zope.session. :-/
Making the application depend on the libraries is fine, and the name
of the package ('appsetup') suggests that it *should* be the place with
all the dependencies: OO frameworks need to have *somebody* wire in the
pieces, and that bit is usually the part which runs at startup.
The problem is that the bootstrap code in zope.app.appsetup is really
zope3, the application-specific, so it uses root folders,
persistent site managers, site management containers,
ZopePublication.root_name, and so on. The code itself is okay, because
it provides an easy way to setup misc. components for the zope3
application server, but still it's a problem, because it's probably
impossible to refactor it in a application-independent way (until we
provide some cool pluggable application bootstrapping mechanism, which
is probably will become too complex and not needed/used by most
application developers).
So, the general question is where should we move the bootstrap setup
code? Or, alternatively, we could just leave it in place, but greatly
separate it from another package components and provide
zope.app.appsetup as an extra dependency (sigh...).
+1 for moving all that stuff into the application.
Tres.
- --
===
Tres Seaver +1 540-429-0999 tsea...@palladion.com
Palladion Software Excellence by Designhttp://palladion.com
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFJvT/E+gerLs4ltQ4RAg3GAJ9+ns3Vos2k3nwLsfJywxYwcrWKuQCgphjG
MyH570P+c4JoxhuNBEUDc7k=
=ePCM
-END PGP SIGNATURE-
___
Zope-Dev maillist - Zope-Dev@zope.org
http://mail.zope.org/mailman/listinfo/zope-dev
** No cross posts or HTML encoding! **
(Related lists -
http://mail.zope.org/mailman/listinfo/zope-announce
http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] [Zope 2.12] Packaging weakness
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 15.03.2009 18:37 Uhr, Dieter Maurer wrote: Andreas Jung wrote at 2009-3-15 08:56 +0100: ... On 15.03.2009 8:36 Uhr, Dieter Maurer wrote: The documentation on PyPI tells to look into doc/INSTALL.txt to find installation instructions. However, doc is not installed by the standard easy_install process. Therefore, it is not so easy to find it. Relevant documentation should be installed by the standard easy_install process (it should be part of the installed egg). All related docs are available from our new place: http://docs.zope.org/ Hint: then the PyPI page should get considerable overhaul: * It should point to http://docs.zope.org;. Instead, it currently points to http://www.zope.org/Documentation/; where no current installation instructions can be found * It should indicate that unlike natural expectation, the packagers of the Zope2 egg decided to put the installation instructions not into the eggs but instead on the internet. And as this is a new place, a link there would be appropriate. This is already fixed long ago in the README.txt in SVN. * Maybe, it should warn people agaist easy_installing Zope2 -- as the developers did not yet care much about this distribution way and the installed egg may not work. We are at alpha 1. You're smart enough in order to deal with an Zope 2 alpha release and all other people interested in a Zope 2.12 release also know how to work with the current code base (you know, the our circles). Andreas -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkm9P8oACgkQCJIWIbr9KYyvtgCdHMVDs8qMNme5vzcBzGm6tJlx zZIAoNxABI8u1Coi/Vy0fEZAbrXs2m5U =bZ5/ -END PGP SIGNATURE- begin:vcard fn:Andreas Jung n:Jung;Andreas org:ZOPYX Ltd. Co. KG adr;quoted-printable:;;Charlottenstr. 37/1;T=C3=BCbingen;;72070;Germany email;internet:i...@zopyx.com title:CEO tel;work:+49-7071-793376 tel;fax:+49-7071-7936840 tel;home:+49-7071-793257 x-mozilla-html:FALSE url:www.zopyx.com version:2.1 end:vcard ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] [Zope 2.12] distribution broken
Andreas Jung wrote at 2009-3-15 08:48 +0100: ... Zope2 2.12.1a1 version conflict ... ... In addition: setuptools 0.6c7 is pretty old and known to be broken in some ways. As expected, setuptool 0.6.c7 was not the problem. After easy_install -U setuptools, an easy_install -U Zope2 leads to (zcpython)newdm: easy_install -U Zope2 Searching for Zope2 Reading http://pypi.python.org/simple/Zope2/ Reading http://www.zope.org Best match: Zope2 2.12.0.a1 Processing Zope2-2.12.0.a1-py2.5-linux-i686.egg Zope2 2.12.0.a1 is already the active version in easy-install.pth Installing zpasswd script to /home/dieter/ZopeSVN/ZClasses/zcpython/bin Installing mkzeoinstance script to /home/dieter/ZopeSVN/ZClasses/zcpython/bin Installing mkzopeinstance script to /home/dieter/ZopeSVN/ZClasses/zcpython/bin Using /home/dieter/ZopeSVN/ZClasses/zcpython/lib/python2.5/site-packages/Zope2-2.12.0.a1-py2.5-linux-i686.egg Processing dependencies for Zope2 Searching for zope.component==3.5.1 Reading http://pypi.python.org/simple/zope.component/ Best match: zope.component 3.5.1 Downloading http://pypi.python.org/packages/source/z/zope.component/zope.component-3.5.1.tar.gz#md5=006c43ad77ed4982e49c07f6e65b68a2 Processing zope.component-3.5.1.tar.gz Running zope.component-3.5.1/setup.py -q bdist_egg --dist-dir /tmp/easy_install-KtgqcP/zope.component-3.5.1/egg-dist-tmp-3BefxU Adding zope.component 3.5.1 to easy-install.pth file Installed /home/dieter/ZopeSVN/ZClasses/zcpython/lib/python2.5/site-packages/zope.component-3.5.1-py2.5.egg error: Installed distribution zope.component 3.5.1 conflicts with requirement zope.component=3.6.0 -- Dieter ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] [Zope 2.12] distribution broken
Andreas Jung wrote at 2009-3-15 08:48 +0100: ... Zope2 2.12.0a1 distribution broken ... ... Try using the traditional python bootstrap.py bin/buildout approach. That (magically) worked. -- Dieter ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] [Zope 2.12] how to test products/packages?
Andreas Jung wrote at 2009-3-15 18:36 +0100: ... test was a convenient way to test products and packages in the context of the instance. How is this use case now supported? Go with the buildout approach and use the alltests.cfg for testing support (see alltests.cfg). Means: work with a SVN checkout. I do not want to test Zope, I want to test *MY* Zope based components. Then write *your* dieter.cfg containing [buildout] extends = buildout.cfg parts += alltests [alltests] recipe = zc.recipe.testrunner eggs = dm.foo.bar and run buildout -c dieter.cfg My experience with buildout is not good. I want to avoid it. -- Dieter ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] [Zope 2.12] distribution broken
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 15.03.2009 18:59 Uhr, Dieter Maurer wrote: Andreas Jung wrote at 2009-3-15 08:48 +0100: ... Zope2 2.12.1a1 version conflict ... ... In addition: setuptools 0.6c7 is pretty old and known to be broken in some ways. As expected, setuptool 0.6.c7 was not the problem. After easy_install -U setuptools, an easy_install -U Zope2 leads to (zcpython)newdm: easy_install -U Zope2 Searching for Zope2 Reading http://pypi.python.org/simple/Zope2/ Reading http://www.zope.org Best match: Zope2 2.12.0.a1 Processing Zope2-2.12.0.a1-py2.5-linux-i686.egg Zope2 2.12.0.a1 is already the active version in easy-install.pth Installing zpasswd script to /home/dieter/ZopeSVN/ZClasses/zcpython/bin Installing mkzeoinstance script to /home/dieter/ZopeSVN/ZClasses/zcpython/bin Installing mkzopeinstance script to /home/dieter/ZopeSVN/ZClasses/zcpython/bin Using /home/dieter/ZopeSVN/ZClasses/zcpython/lib/python2.5/site-packages/Zope2-2.12.0.a1-py2.5-linux-i686.egg Processing dependencies for Zope2 Searching for zope.component==3.5.1 Reading http://pypi.python.org/simple/zope.component/ Best match: zope.component 3.5.1 Downloading http://pypi.python.org/packages/source/z/zope.component/zope.component-3.5.1.tar.gz#md5=006c43ad77ed4982e49c07f6e65b68a2 Processing zope.component-3.5.1.tar.gz Running zope.component-3.5.1/setup.py -q bdist_egg --dist-dir /tmp/easy_install-KtgqcP/zope.component-3.5.1/egg-dist-tmp-3BefxU Adding zope.component 3.5.1 to easy-install.pth file Installed /home/dieter/ZopeSVN/ZClasses/zcpython/lib/python2.5/site-packages/zope.component-3.5.1-py2.5.egg error: Installed distribution zope.component 3.5.1 conflicts with requirement zope.component=3.6.0 As mentioned earlier: use buildout. easy_install support has no high priority right now. - -aj -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkm9TUsACgkQCJIWIbr9KYy9RACg1gzsh7El4WsRXYjpBxEBrCnC RiUAoICbUYxyDmVALCw98iQ/iv8y3VUV =i2uH -END PGP SIGNATURE- begin:vcard fn:Andreas Jung n:Jung;Andreas org:ZOPYX Ltd. Co. KG adr;quoted-printable:;;Charlottenstr. 37/1;T=C3=BCbingen;;72070;Germany email;internet:i...@zopyx.com title:CEO tel;work:+49-7071-793376 tel;fax:+49-7071-7936840 tel;home:+49-7071-793257 x-mozilla-html:FALSE url:www.zopyx.com version:2.1 end:vcard ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] producing a list of packages in the Zope Framework?
On Fri, 2009-03-06 at 16:37 +0100, Hanno Schlichting wrote: Hi. Martijn Faassen wrote: No volunteers to help produce such a list? This is the friendly reminder that this thread is stalled. ;) When going through the list myself I didn't see a clear cut-off-point for things to include and things not to include. So? Attached you'll find my suggestion for the list. It is based on the Zope2/Plone perspective: Which packages do those two actually use from all the zope.* packages. I suspect the set will initially be a bit larger to accommodate Grok. There is also going to be a set of new packages which should be included over time I guess and a set of packages which should no longer be part of the Zope Framework. This might be a good start however. Hanno plain text document attachment (zope_framework.txt) Dependencies not part of the Zope Framework ClientForm RestrictedPython ZConfig ZODB3 docutils mechanize pytz setuptools transaction zc.lockfile zdaemon Zope Framework zope.annotation zope.app.applicationcontrol zope.app.appsetup zope.app.authentication zope.app.basicskin zope.app.cache zope.app.component zope.app.container zope.app.debug zope.app.dependable zope.app.exception zope.app.form zope.app.http zope.app.interface zope.app.locales zope.app.pagetemplate zope.app.publication zope.app.publisher zope.app.schema zope.app.security zope.app.testing It might be a goal to get rid of all of zope.app with respect to the Zope Framework definition. zope.broken Hmm. There's only a single marker interface in that package. zope.browser zope.cachedescriptors zope.component zope.configuration zope.container zope.contentprovider zope.contenttype zope.copy zope.copypastemove zope.datetime Is this actually still needed? It looks like this pre-dates Python's datetime module. There's also pytz around. zope.deferredimport I feel like we might wanna keep it although we want to avoid deferredimports. zope.deprecation We're talking about getting rid of deprecation so we might want to give up the package too, once decided. ;) zope.dottedname zope.dublincore zope.error zope.event zope.exceptions zope.filerepresentation zope.formlib zope.hookable zope.i18n zope.i18nmessageid zope.interface zope.lifecycleevent zope.location zope.minmax zope.pagetemplate zope.proxy zope.publisher zope.schema zope.security zope.sendmail zope.sequencesort zope.server zope.session zope.site zope.size zope.structuredtext zope.tal zope.tales zope.testbrowser zope.testing zope.traversing zope.viewlet I don't see a package that would be blindingly obvious to take away from the remainder of the list. Parts of the Zope 3.5 KGS not required by Zope 2.12 / Plone 4 Most of the following list I agree to exclude, except the ones I marked up. Some I'm not sure about. zope.catalog +1 for keeping zope.decorator zope.documenttemplate zope.file zope.html zope.index +1 for keeping zope.intid +1 for keeping zope.keyreference +1 for keeping zope.mimetype unsure zope.modulealias zope.rdb zope.securitypolicy zope.testrecorder zope.ucol zope.wfmc zope.xmlpickle zope.app.apidoc zope.app.boston zope.app.broken zope.app.catalog zope.app.content zope.app.dav zope.app.debugskin zope.app.dtmlpage zope.app.error zope.app.externaleditor zope.app.file zope.app.folder zope.app.ftp zope.app.generations zope.app.homefolder zope.app.i18n zope.app.i18nfile zope.app.interpreter zope.app.intid zope.app.layers zope.app.locking zope.app.module zope.app.onlinehelp zope.app.pluggableauth zope.app.preference zope.app.preview zope.app.principalannotation zope.app.pythonpage zope.app.renderer zope.app.rotterdam zope.app.securitypolicy zope.app.server zope.app.session zope.app.skins zope.app.sqlscript zope.app.traversing zope.app.tree zope.app.twisted zope.app.undo zope.app.wfmc zope.app.workflow zope.app.wsgi zope.app.xmlrpcintrospection zope.app.zapi zope.app.zcmlfiles zope.app.zopeappgenerations zope.app.zptpage Christian -- Christian Theune · c...@gocept.com gocept gmbh co. kg · forsterstraße 29 · 06112 halle (saale) · germany http://gocept.com · tel +49 345 1229889 7 · fax +49 345 1229889 1 Zope and Plone consulting and development signature.asc Description: This is a digitally signed message part ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] setup.py extra dependencies
On Thu, 2009-03-05 at 21:36 +0100, Wichert Akkerman wrote: Previously Sidnei da Silva wrote: On Thu, Mar 5, 2009 at 5:20 PM, Wichert Akkerman wich...@wiggy.net wrote: I would like to see a move away from zope testing frameworks to a more standard testing infrastructure: setup.py test, possibly combined with using nose. Wichert. Be aware of nose issue #102: http://code.google.com/p/python-nose/issues/detail?id=102 Is there a particular reason to keep using the test_suite convention? Personally I much prefer nose's habit of automatically picking up tests. I think there is not. One of the reasons I refactored the test runner a while ago was to make it possible to support a less-boilerplate-heavy scheme of getting tests set up. Christian -- Christian Theune · c...@gocept.com gocept gmbh co. kg · forsterstraße 29 · 06112 halle (saale) · germany http://gocept.com · tel +49 345 1229889 7 · fax +49 345 1229889 1 Zope and Plone consulting and development signature.asc Description: This is a digitally signed message part ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Standard request/response API
On Tue, 2009-03-03 at 01:33 +0100, Martijn Faassen wrote: Hi there, Jim Fulton wrote: There's been some discussion recently about separating the interfaces in zope.publisher from the implementations to facilitate other implementations. I think it would be great to standardize request and response APIs. I'd love to see this extend beyond the Zope community. I believe that there have been some moves to try to do this at the WSGI level, although I haven't kept up with the discussion. See WebOb for Ian Bicking's effort (who did investigate a lot of these APIs including ours in that effort). WebOb is very widely adopted in the WSGI community already and I see no realistic way for us to make any headway there now that it is established. I believe that Pylons, TurboGears 2, repoze.bfg and restish all use it. WebOb is more than an interface but also an implementation and in that sense is quite a bit like our zope.publisher. Even though it's a specific implementation it's on top of WSGI so people can adopt it easily. I think it would be very interesting to look for ways to make bits of Zope work with WebOb somehow. @Martijn: This thread somewhat overlapped with the forming of the steering group. Do you think this should go to the list of open issues? -- Christian Theune · c...@gocept.com gocept gmbh co. kg · forsterstraße 29 · 06112 halle (saale) · germany http://gocept.com · tel +49 345 1229889 7 · fax +49 345 1229889 1 Zope and Plone consulting and development signature.asc Description: This is a digitally signed message part ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] [Zope 2.12] how to test products/packages?
Dieter Maurer wrote: Hanno Schlichting wrote at 2009-3-15 11:10 +0100: Dieter Maurer wrote: The Zope 2.12 documention tells that the test command was removed from zopectl. test was a convenient way to test products and packages in the context of the instance. How is this use case now supported? The normal way to develop anything in the Zope world is based on zc.buildout today. You can define a testrunner like this: I do not have good experience with buildout and will try to avoid it. It ought to be possible to run the Zope testrunner by installing a script, e.g. installing zope.testrunner in a virtualenv to get the 'test' script. I don't know what more zc.recipe.testrunner does, but I agree that we shouldn't be dependent on buildout (over virtualenv+easy_install/pip) to be able to run tests. Martin -- Author of `Professional Plone Development`, a book for developers who want to work with Plone. See http://martinaspeli.net/plone-book ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] [Zope 2.12] distribution broken
Andreas Jung wrote: As mentioned earlier: use buildout. easy_install support has no high priority right now. Whilst I understand that we don't have the capacity to test all different configurations now, I think it's a good principle to try to avoid a 'hard' dependency on zc.buildout. If we can, we should rely on e.g. setuptools console scripts rather than things generated through specific recipes. Of course, this is just part of an evolution. 'mkzopeinstance' was a completely custom build solution. Using a standard zc.buildout configuration is better, imho, than maintaining a custom build script. But using just setuptools/eggs and letting buildout be a preference rather than a hard dependency is better still. Martin -- Author of `Professional Plone Development`, a book for developers who want to work with Plone. See http://martinaspeli.net/plone-book ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] [Zope3-checkins] [Checkins] SVN: zope.app.component/trunk/setup.py set missing minimum version
On Sunday 15 March 2009, Wichert Akkerman wrote: If the package does not work with an older version of zope.publisher than imho that version restriction *has* to be in setup.py. And what if I backport the fix? We have done version specification like this in the Zope packages before and it almost brought development to complete halt, because versions would not match anymore. Regards, Stephan -- Stephan Richter Web Software Design, Development and Training Google me. Zope Stephan Richter ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] [Zope3-checkins] [Checkins] SVN:zope.app.component/trunk/setup.py set missing minimum version
Hi Stephan, Wichert, Michael Betreff: Re: [Zope3-checkins] [Checkins] SVN:zope.app.component/trunk/setup.py set missing minimum version On Sunday 15 March 2009, Wichert Akkerman wrote: If the package does not work with an older version of zope.publisher than imho that version restriction *has* to be in setup.py. And what if I backport the fix? We have done version specification like this in the Zope packages before and it almost brought development to complete halt, because versions would not match anymore. +1 If one of several packages doesn't get updated with buildout is only possible if someone uses an index server which only have one of the both released packages available. If this is not true, then this is a bug in buildout and buildout doesn't catch the package versions correct. Which I think is not the case. All other reason I can think about that someone only got one package and another not if two package get released depends on a bad package management. Fix versions are a pain because you can't be sure that someone uses a patched or branched package which you will fix the version for. Package management should never be done in a single package! Michael, can you explain what's happen that you didn't got the zope.publisher release? And was this problem solved after fixing the version or did you do something else too? Regards Roger Ineichen Regards, Stephan -- Stephan Richter Web Software Design, Development and Training Google me. Zope Stephan Richter ___ Zope3-Checkins mailing list zope3-check...@zope.org http://mail.zope.org/mailman/listinfo/zope3-checkins ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] [Fwd: [Bug 343079] [NEW] Broken distribution (2009-03-15)]
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Andreas Jung wrote: On 15.03.2009 18:42 Uhr, Tres Seaver wrote: Original Message Subject: [Bug 343079] [NEW] Broken distribution (2009-03-15) Date: Sun, 15 Mar 2009 07:42:00 - From: dmaurer die...@handshake.de Reply-To: Bug 343079 343...@bugs.launchpad.net To: tsea...@palladion.com References: 20090315074200.12457.19313.malone...@potassium.ubuntu.com Public bug reported: The current (2009-03-12) PyPI distribution for Zope2 2.12.0a1 is broken. 'easy_install'ing it leads to version conflicts for 'zope.component' (3.5.1 versus 3.6.0) in the call of 'mkzopeinstance'. ** Affects: zope2 Importance: Undecided Status: New The breakage is due to the release of the new zope.prinipalregistry egg. We should probably manage a Zope2 indes and tell people to use it when running easy_install, because PyPI is not suitable for the task given setuptools' incremental requirements discovery design. Easy_installing the a1 sdist should behave like using buildout since the versions within the sdist are pinned as well. It actually worked at the time of the a1 release. I don't understand right now why we get this failure. I don't see any pinning at all here: http://svn.zope.org/Zope/tags/2.12.0a1/setup.py?rev=97288view=auto This kind of issue was the source of my contentiont that released versions should ship with exact pins of the egg versions (the full transitive closure): it should at least be possible to generate a 'Zope2-exact' distribution which provides a known good installation, even it a 'Zope2-upgradable' distribution might be better for some people. The other option, as I said earlier, is to maintain an index for each release branch of Zope2, and populate it only with eggs which have been tested not to break the upgrade. We could specify that index in the install docs, and maybe even in the 'setup.cfg' of the package. Tres. - -- === Tres Seaver +1 540-429-0999 tsea...@palladion.com Palladion Software Excellence by Designhttp://palladion.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFJvczs+gerLs4ltQ4RAjnqAKDHjP2hnJvkEwxiXVYBVwHzSe7x7wCbBnkQ /fc3lmFuTV2lXOby+8s1sfA= =3H9B -END PGP SIGNATURE- ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] [Fwd: [Bug 343079] [NEW] Broken distribution (2009-03-15)]
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 16.03.2009 4:52 Uhr, Tres Seaver wrote: Andreas Jung wrote: On 15.03.2009 18:42 Uhr, Tres Seaver wrote: Original Message Subject: [Bug 343079] [NEW] Broken distribution (2009-03-15) Date: Sun, 15 Mar 2009 07:42:00 - From: dmaurer die...@handshake.de Reply-To: Bug 343079 343...@bugs.launchpad.net To: tsea...@palladion.com References: 20090315074200.12457.19313.malone...@potassium.ubuntu.com Public bug reported: The current (2009-03-12) PyPI distribution for Zope2 2.12.0a1 is broken. 'easy_install'ing it leads to version conflicts for 'zope.component' (3.5.1 versus 3.6.0) in the call of 'mkzopeinstance'. ** Affects: zope2 Importance: Undecided Status: New The breakage is due to the release of the new zope.prinipalregistry egg. We should probably manage a Zope2 indes and tell people to use it when running easy_install, because PyPI is not suitable for the task given setuptools' incremental requirements discovery design. Easy_installing the a1 sdist should behave like using buildout since the versions within the sdist are pinned as well. It actually worked at the time of the a1 release. I don't understand right now why we get this failure. I don't see any pinning at all here: http://svn.zope.org/Zope/tags/2.12.0a1/setup.py?rev=97288view=auto Please look at the getPackages() method taking the version*cfg files into account. So all versions should be pinned. However there is obviously a difference between using buildout with pinned versions and setuptools or a small undetected hole in the process. This kind of issue was the source of my contentiont that released versions should ship with exact pins of the egg versions (the full transitive closure): it should at least be possible to generate a 'Zope2-exact' distribution which provides a known good installation, even it a 'Zope2-upgradable' distribution might be better for some people. The other option, as I said earlier, is to maintain an index for each release branch of Zope2, and populate it only with eggs which have been tested not to break the upgrade. We could specify that index in the install docs, and maybe even in the 'setup.cfg' of the package. I hope we can discuss and resolve remaining issues during PyCon. Andreas -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkm96JYACgkQCJIWIbr9KYwwUgCfa9WNM94Q0J6bHKyjTWeeox94 wP8An0ZVHB6wrp0MyZ2ZbvlEWbFFtEK3 =tVTH -END PGP SIGNATURE- begin:vcard fn:Andreas Jung n:Jung;Andreas org:ZOPYX Ltd. Co. KG adr;quoted-printable:;;Charlottenstr. 37/1;T=C3=BCbingen;;72070;Germany email;internet:i...@zopyx.com title:CEO tel;work:+49-7071-793376 tel;fax:+49-7071-7936840 tel;home:+49-7071-793257 x-mozilla-html:FALSE url:www.zopyx.com version:2.1 end:vcard ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
