Hi all,
I started writing a book about Zope Component Architecture.
http://www.muthukadan.net/docs/zca.html
http://www.muthukadan.net/docs/zca.pdf
If you have any suggestions/comments please send it to me.
The book's source is hosted here:
https://edge.launchpad.net/zcadoc
BTW, I
Chris McDonough wrote:
- Institute a policy that all distributions that are released to the
cheeseshop should be installable via easy_install. IMO, if they
are not installable this way, they should not be released to the
cheeseshop, given the larger Python community's
Tres Seaver wrote:
I've never known of transactions in anything to do with setuptools...
I wasn't literally referring to a transaction, in the ZODB sense -- I
meant, install using a separate run of easy_install'.
Unless I'm missing something, that seems... sub-optimal.
So I have to do
On Wednesday 14 November 2007, Philipp von Weitershausen wrote:
- Figure out why buildout can (apparently) qsuccesfully install
dependencies of currently failing zope.* eggs while easy_install
can't. I probably won't be able to do this.
Because most buildouts specifically point
Hi Baiju
I started writing a book about Zope Component Architecture.
Great news! Thank you for this effort!
If you have any suggestions/comments please send it to me.
We've taken a quick look at it and We've seen something strange on page
21:
... def register(self):
... next_id =
Nando Quintana wrote:
Hi Baiju
I started writing a book about Zope Component Architecture.
Great news! Thank you for this effort!
If you have any suggestions/comments please send it to me.
We've taken a quick look at it and We've seen something strange on
page 21:
... def
On Wednesday 14 November 2007, Philipp von Weitershausen wrote:
Yes, you lose the
ability to make a bugfix in one subpackage and release it, but
IIRC the intent is to trim zope.app down anyway, pushing
libraryish things out to top-level or zope.* packages.
That *was* the
Summary of messages to the zope-tests list.
Period Tue Nov 13 13:00:00 2007 UTC to Wed Nov 14 13:00:00 2007 UTC.
There were 5 messages: 5 from Zope Unit Tests.
Tests passed OK
---
Subject: OK : Zope-2.7 Python-2.3.6 : Linux
From: Zope Unit Tests
Date: Tue Nov 13 20:55:02 EST 2007
Attempting to easy_install all 'zope'-related releases using the
script at http://svn.repoze.org/playground/trunk/chris/zopesvnchecker/releasechecker.py
, the results were:
122 failures, 67 successes.
See http://www.plope.com/static/misc/rcresults-2007-11-14.txt for
details.
- C
On Nov 14, 2007, at 6:05 AM, Stephan Richter wrote:
On Wednesday 14 November 2007, Philipp von Weitershausen wrote:
- Figure out why buildout can (apparently) qsuccesfully install
dependencies of currently failing zope.* eggs while easy_install
can't. I probably won't be able to do
On Nov 14, 2007, at 8:38 AM, Chris McDonough wrote:
On Nov 14, 2007, at 6:05 AM, Stephan Richter wrote:
On Wednesday 14 November 2007, Philipp von Weitershausen wrote:
- Figure out why buildout can (apparently) qsuccesfully install
dependencies of currently failing zope.* eggs while
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Chris Withers wrote:
Tres Seaver wrote:
I've never known of transactions in anything to do with setuptools...
I wasn't literally referring to a transaction, in the ZODB sense -- I
meant, install using a separate run of easy_install'.
Unless I'm
On Nov 14, 2007, at 4:46 AM, Philipp von Weitershausen wrote:
...
The individual eggs typically can't be used
outside of a zope appserver installation (and if they can, they
probably shouldn't be in zope.app, they should be in zope or
they should be their own top-level package),
On Nov 14, 2007, at 9:57 AM, Jim Fulton wrote:
On Nov 14, 2007, at 8:38 AM, Chris McDonough wrote:
On Nov 14, 2007, at 6:05 AM, Stephan Richter wrote:
On Wednesday 14 November 2007, Philipp von Weitershausen wrote:
- Figure out why buildout can (apparently) qsuccesfully install
On Wednesday 14 November 2007, Chris McDonough wrote:
In the meantime, whose feet would I be shooting if I changed setup.py
dependency info so that, e.g. zope.tales (and the like) didn't pull in
as many dependencies? Installing zope.tales (as an example, I'm sure
its as a result of a
Chris Withers wrote at 2007-11-14 09:14 +:
Tres Seaver wrote:
I've never known of transactions in anything to do with setuptools...
I wasn't literally referring to a transaction, in the ZODB sense -- I
meant, install using a separate run of easy_install'.
Unless I'm missing something,
Hi Peter,
I recently switched setup.py and buildout to use the new zope3.4 KGS
and this caused some problems for existing installations of zcontact.
Please submit a bug on launchpad (http://launchpad.net/zcontact) and
I'll see if I can find what is causing the clonflict sometime today.
- Paul
Is there an equivalent for tests_require in buildout.cfg/
zc.recipe.testrunner?
The reason I ask is this... currently the zope.18n distribution has an
install_requires that looks something like this:
install_requires=[
'setuptools',
'pytz',
Hello,
how can the error be corrected?
./bin/easy_install -U zcontact
Searching for zcontact
Reading http://pypi.python.org/simple/zcontact/
Reading http://launchpad.net/zcontact
Best match: zcontact 0.1.0a9
Processing zcontact-0.1.0a9-py2.4.egg
zcontact 0.1.0a9 is already the active version in
On Nov 14, 2007, at 9:57 AM, Jim Fulton wrote:
So what makes this stuff work via buildout is all version-pinning
now?
They aren't using the cheeseshop. They are using the KGS instead.
They are currently also pinned.
zope.tal's buildout.cfg contains:
[versions]
zope.traversing = 3.4.0
What's causing the conflict is the fact that
zope.traversing=3.5.0a1.dev-r78730 isn't in the KGS (nor will it get
in there). It might help for Peter to move his zope.app.publisher egg
aside (which is the thing that depends on this release) and try the -U
again.
On Nov 14, 2007, at 3:21
Stephan Richter wrote:
Yes, everyone has to sign a contributor agreement, but you do not have to
become a Zope Foundation member.
Please gimme advice or a link, AFAIK after standing up ZoFo (sounds very
nerdy B-) haha ) old rules changed. What we need to do?
Note that svn.zope.org will
Sidnei da Silva wrote:
I believe you can host code on launchpad.net too, but using 'bzr'
instead of Subversion.
There is a lot of tools include online services such as ohloh.net, that
use subversion. For example eggs can automatically checkout from svn.
Does bzr repos allow that?
BTW, who
On Wednesday 14 November 2007, Chris McDonough wrote:
zope.tal's buildout.cfg contains:
[versions]
zope.traversing = 3.4.0
zope.app.publisher = 3.4.0
zope.tal shouldn't depend on either of these, so I'd like to remove
both the pinning in buildout.cfg and fix the dependency bug that
On Wednesday 14 November 2007, Jim Fulton wrote:
For a while,
those of us working on Zope 3 revelled in refactor mercilessly.
This was fine before Zope 3 was widely adopted. We have since leaned
the value of mercy. :)
LOL!
(This should make it into the eternal list of Zope quotes.)
On Wednesday 14 November 2007, Chris McDonough wrote:
That's actually a no-good pack of lies, though. ;-) I'd like to
change setup.py to something like this:
test_suite = __main__.alltests, # to support setup.py test
tests_require=[
'zope.testing',
Chris McDonough wrote:
Is there an equivalent for tests_require in
buildout.cfg/zc.recipe.testrunner?
The reason I ask is this... currently the zope.18n distribution has
an install_requires that looks something like this:
install_requires=[ 'setuptools', 'pytz', 'zope.i18nmessageid',
27 matches
Mail list logo
