zope.testing trunk has five tests failing in Python 2.4.6 and four
failing in Python 2.5.4 (on self-compiled versions on Mac OS X).
Anyone know what the story is here?
Gary
___
Zope-Dev maillist - Zope-Dev@zope.org
http://mail.zope.org/mailman
On Feb 16, 2009, at 3:11 PM, Marius Gedminas wrote:
On Mon, Feb 16, 2009 at 10:17:06AM -0500, Gary Poster wrote:
zope.testing trunk has five tests failing in Python 2.4.6 and four
failing in Python 2.5.4 (on self-compiled versions on Mac OS X).
Anyone know what the story is here?
No clue
On Feb 17, 2009, at 7:55 PM, Shane Hathaway wrote:
Gary Poster wrote:
Launchpad uses OpenID. We don't have that slated for abstraction
and open-sourcing immediately. However, most of the Launchpad code
(including this bit) is to be open-sourced by this summer,
abstracted
how to use the OpenID consumer API in
AuthKit.
I could be mistaken about any of the particular points here.
I'm glad that Shane replied that what Francis said helped him.
FWIW, IRT Launchpad being an OpenID consumer, that's supposed to be a
possibility very soon.
Gary
as internal data structures. I regard that as a primary
use case for this package, so IMO that's important to note in the doc
and in the Python file.
Otherwise, looks great to me.
Thank you!
Gary
___
Zope-Dev maillist - Zope-Dev@zope.org
http
experience Martin is recounting, just so we have
*something*.
Gary
___
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
to be tested. The Zope Framework team leader then
decides some time to make a release, so people might shuffle around
versions more than usual, but it's just another KGS.
Gary
___
Zope-Dev maillist - Zope-Dev@zope.org
http://mail.zope.org/mailman
On Mar 3, 2009, at 12:31 PM, Martijn Faassen wrote:
Hey Gary,
[panarchist approach where we have people starting groups that could
compete for attention]
[Had to look up panarchist, but yes, essentially.]
I agree that it should be relatively easy to start Zope projects
under
the Zope
On Mar 3, 2009, at 10:57 AM, Stephan Richter wrote:
On Tuesday 03 March 2009, Gary Poster wrote:
My mild counter proposal was this.
- The ZF formally institutes an easy way for people to start Zope
projects
- Hopefully, Martijn F. starts something like the project he
described
On Mar 4, 2009, at 2:20 AM, Thomas Lotze wrote:
Gary Poster gary.pos...@gmail.com schrieb:
Index: src/zc/dict/configure.zcml
===
--- src/zc/dict/configure.zcml (.../trunk) (revision 0)
+++ src/zc/dict/configure.zcml
in it to adapt
it to existing APIs.
This might be an excellent project for PyCon.
Hey.
I have some other projects to work on there as well, but I'll be at
PyCon, and am interested in helping on this (specifically the WebOb
idea already discussed).
Gary
different ways, of
course), as far as I can tell.
Gary
___
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
packages.
Gary
___
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
On Mar 6, 2009, at 9:50 AM, Martijn Faassen wrote:
Hi there,
Thanks Gary for sketching our the zc.async usecase. Note that zc.async
isn't in the Zope Framework at this point in time so it wouldn't be
directly affected by this policy, but it's still a useful usecase of
course.
Right
?
Gary
___
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 )
and the current language reference/PEP 8 , see my blog post this from
February:
http://codesinger.blogspot.com/2009/02/dont-use-in-python-unless-you-are.html
. It may come off more strongly than it should, but I still find the
point to be a good one.)
Gary
the barf's traceback?
Gary
___
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
On Mar 16, 2009, at 8:39 AM, Martin Aspeli wrote:
Gary Poster wrote:
On Mar 16, 2009, at 4:02 AM, Martin Aspeli wrote:
Hi,
I *think* this is a bug in zc.relationship, but I'm not quite sure.
I'm using ZODB3 3.8.1 (to get BLOB support) and trying to install
plone.app.relations, which
On Mar 16, 2009, at 9:19 AM, Martin Aspeli wrote:
Hi Gary,
zc.relationship 2.0 trunk is now essentially a wrapping of
zc.relation
code for backwards compatibility.
I see. But 2.0dev on pypi isn't?
What's the story behind zc.relation and the evolution of
zc.relationship?
Briefly, I
On Mar 16, 2009, at 10:21 AM, Martin Aspeli wrote:
Hi Gary,
Thanks for being so helpful!
Happy to.
What's the difference between 1.1.1 and 2.0dev on pypi?
I intended that 1.1.1 would simply make the absolutely minimal
changes
necessary for you to be able to use the 1.1 branch
that
requirements can only say zope.foo = x.y, and never zope.foo =
x.y.z.
What do people think?
That looks sane, so I'm +1 :)
Also +1
Gary
___
Zope-Dev maillist - Zope-Dev@zope.org
http://mail.zope.org/mailman/listinfo/zope-dev
** No cross posts or HTML
On Mar 16, 2009, at 1:20 PM, Martin Aspeli wrote:
Martin Aspeli wrote:
Gary Poster wrote:
Hopefully. Do we know that zc.relationship 1.1 works with both ZODB
versions?
That would be a significant point of its existence, so I certainly
hope so. I'm 80%+ confident that it does, and would
On Mar 16, 2009, at 10:55 PM, Martin Aspeli wrote:
Gary Poster wrote:
Yes, +1. Thank you. I was about to write to your other message that
this was quite possibly the only 3.8 dependency.
Cool. Committed.
If we do that, then we can let plone.relations depend on
zc.relationship
1.1.1
-template-engine
I can help setting up this structure, if needed.
I agree with Sidnei. Another example is the lazr projects
(https://launchpad.net/lazr
).
To be clear, making an umbrella project like this does need someone
with admin rights in lp, so it will need help if it is desired. :-)
Gary
in touch with me, though I'm
happy to share cell phone/skype info privately.
Gary
___
Zope-Dev maillist - Zope-Dev@zope.org
http://mail.zope.org/mailman/listinfo/zope-dev
** No cross posts or HTML encoding! **
(Related lists -
http
if it happens and meanwhile be
happy to take the zope3 project in as legacy.
Gary
___
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
. I'll write something up to zope-dev tomorrow.
Gary
___
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
On Apr 2, 2009, at 7:35 PM, Tres Seaver wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Gary Poster wrote:
I'd like to report back on the progress that Bzr/Launchpad has made
addressing concerns we heard since I last brought up Canonical's
offer
to host the code and contribute
gives a convincing reason why
it is preferable to putting constants in the module, in which case I
will suddenly have a polar shift to +0. :-)
Gary
___
Zope-Dev maillist - Zope-Dev@zope.org
http://mail.zope.org/mailman/listinfo/zope-dev
/lazr.enum .
Gary
___
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
On Apr 6, 2009, at 9:28 AM, Chris Withers wrote:
Gary Poster wrote:
Sadly, I suspect none of the tools are as advanced as TortoiseSVN.
Which
is a real shame :-( Perforce maybe? ;-)
Fair enough that bzr didn't take your fancy, but FWIW, did you try
TortoiseBzr? That has received love
3, as defined by the KGS -
Zope Toolkit. The software switch that this name change implies has
started quite some time ago, with the eggification, and will continue
in its natural and usual open-source course.
Gary
___
Zope-Dev maillist - Zope
, and some of
this is about the zope.org repo.)
Gary
___
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
, but this package doesn't have them yet, so I don't
see why it should block this contribution.
FWIW, I did notice a trivial issue: a spelling error in the CHANGES:
seperated - separated.
Thanks!
Gary
On Apr 28, 2009, at 9:25 AM, markus korn wrote:
I'm not familiar with your process
of interaction they
encourage.
Jono Lange has a nice talk about code review, FWIW, with links to more
(like Guido's old Mondrian video). http://mumak.net/stuff/your-code-sucks.html
Gary
___
Zope-Dev maillist - Zope-Dev@zope.org
http://mail.zope.org/mailman
the
zc.async approach.
Gary
___
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
see Jim checked
this in back at the dawns of time in rev 8532. On IRC, he didn't
recognize this code on a quick look, so he thinks someone else might
be more familiar with this.)
Gary
___
Zope-Dev maillist - Zope-Dev@zope.org
http
On Aug 20, 2009, at 1:50 PM, Jim Fulton wrote:
On Mon, Aug 17, 2009 at 1:43 PM, Gary Postergary.pos...@gmail.com
wrote:
Two teams here at Canonical just encountered the STAGGER_RETRIES
behavior in
http://svn.zope.org/zope.publisher/trunk/src/zope/publisher/http.py?rev=101538view=auto
Hm. I sent this from the wrong account, so it didn't make it to the
zope-dev list. I'm also adding an additional bit of war story at the
end.
On Aug 24, 2009, at 11:16 AM, Gary Poster wrote:
Hi Tres
I made a 3.5.8 release of the zope.publisher 3.5 branch for a reason
unimportant
On Aug 24, 2009, at 5:27 PM, Tres Seaver wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Gary Poster wrote:
Hm. I sent this from the wrong account, so it didn't make it to the
zope-dev list. I'm also adding an additional bit of war story at the
end.
On Aug 24, 2009, at 11:16 AM
http://bugs.python.org/issue1817 gives you the information you
want?
Gary
___
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
Shameless plug: try z3c.recipe.filetemplate.
http://pypi.python.org/pypi/z3c.recipe.filetemplate
. Sounds like it does what you want out of the box.
Gary
On Aug 27, 2009, at 9:14 AM, Encolpe Degoute wrote:
Hello,
These last days I was using collective.recipe.template
have been taking too long and thought I'd at least send this out to
see if anyone has any thoughts. Otherwise, I'll look into it ASAP and
report back.
Thanks
Gary
___
Zope-Dev maillist - Zope-Dev@zope.org
https://mail.zope.org/mailman/listinfo
not to see a change,
with the usual associated costs of communication and check-in police.
That said, I don't this is worth a big argument, or even a big
discussion (or even this email? :-). If the Zope triumverate or
whatever it is these days changes the release document, so be it. :-)
Gary
another version
control system, the 0 policy wouldn't be much of a win anymore.
Perhaps
Gary can tell us whether this would work with bzr?
bzr supports a classic definition of tags--identifying a specific
revision. If it's of interest or help, I include the help text for
the tag command
Hi. pypi advertises http://pypi.python.org/pypi/zc.zservertracelog/1.2.0
but there is no download to be found! :-) Could whoever made the
release add the download?
Thanks
Gary
___
Zope-Dev maillist - Zope-Dev@zope.org
https://mail.zope.org
On Sep 11, 2009, at 4:57 PM, Alexander J Smith wrote:
On Fri, Sep 11, 2009 at 4:54 PM, Alexander J Smith a...@zope.com
wrote:
On Fri, Sep 11, 2009 at 4:44 PM, Marius Gedminas mar...@gedmin.as
wrote:
On Fri, Sep 11, 2009 at 03:51:30PM -0400, Gary Poster wrote:
Hi. pypi advertises http
package already advertises the ability to use an
external process for processing queued mail, but that appears to be an
aspect of the design and the interfaces rather than in the
implementation.
For this particular problem I faced, though, sticking with threads was
easier for now.
Gary
that Bzr/Launchpad were alone in
supporting this, but they are the only ones I can vouch for. For
instance, I'm almost positive that github also allows you to have
multiple committers to a single branch, though I don't remember the
mechanism.
Gary
On Sep 15, 2009, at 7:59 AM, Wichert Akkerman wrote:
On 9/15/09 13:56 , Gary Poster wrote:
2) Our current arrangement, as well as many others, can be
accomplished
with a DVCS. Launchpad + Bzr definitely support this. You would
have a
Launchpad team of committers, with managed
something Gary has touched recently.
Meh, yes indeed--for all but one failure (see below).
The Ubuntu one should be easy to fix.
The Windows ones may be tied up with \n \r fun. It should be trivial
too, though I'll need to get a Windows VM back up--or request aid from
Sidnei. ;-)
I'll address
as coherent as possible, and
avoid bitrot by focusing on the packages which are in active use by
more than one project.
Sounds interesting.
Do you happen to have a list of packages that would be affected by
these rules?
Gary
___
Zope-Dev maillist
Hi. I didn't get it done on the 17th, but I did just make a release
with the necessary fixes (or, the tests pass for me on Windows and
Ubuntu, at least; they already were passing for me on Ubuntu, but I
made the pertinent test somewhat less fragile).
Gary
On Sep 16, 2009, at 3:39 AM
On Sep 14, 2009, at 2:02 PM, Gary Poster wrote:
Once Bzr 2.0 comes out (in less than a month AIUI), I'll at least
send out a link to it and point out some changes made that
specifically address concerns raised by Zope Foundation members when
I raised Launchpad's/Canonical's offer before
On Nov 3, 2009, at 4:48 PM, Chris McDonough wrote:
Gary Poster wrote:
...
It is an advocacy piece only in the sense that we are saying that,
by-and-large, we like what the packages give us, but it is more
challenging than that. It's an interesting pairing to Jeff Shell's
invited
of an advocacy/tutorial perspective. I was honestly a bit surprised
that mine was accepted when Jeff's was already scheduled, but maybe
mine is the dark side version of his talk. :-)
Gary
On Nov 3, 2009, at 2:13 PM, Chris McDonough wrote:
So were any Zope talks/tutorials accepted?
FWIW, Tres had
On Nov 3, 2009, at 3:28 PM, Lennart Regebro wrote:
2009/11/3 Gary Poster gary.pos...@gmail.com:
I had a rethinking interfaces talk accepted. It's about the
positives and negatives of zope.interface and zope.component, driven
primarily from the perspective and experience of the Launchpad
before
PyCon.
If other folks want to run on without me, I can at least point to the slides
for the OSCON talk I gave with the Canonical/Launchpad feedback if you are
interested.
Gary
___
Zope-Dev maillist - Zope-Dev@zope.org
https://mail.zope.org
.
That was discussed and rejected near the very beginning of the Z3 effort, in my
memory. They are too different. Our use of adapters generally involves
looking something up and automatically calling it. Our use of utilities
generally involves simply looking something up and returning it.
Gary
On Nov 25, 2009, at 11:34 AM, Thomas Lotze wrote:
Gary Poster wrote:
On Nov 25, 2009, at 11:17 AM, Thomas Lotze wrote:
What about a simple and consistent API for all components including
utilities, adapters and multiadapters:
IFoo()
IFoo(x)
IFoo(x, y)
I seem to remember
On Nov 25, 2009, at 11:54 AM, Chris McDonough wrote:
Gary Poster wrote:
FWIW, I'm saying that utilities and adapters are different. I share
your/Martijn's/other people's general thoughts about merging adapters and
multiadapters in the interface __call__ syntax.
There might should
not of a lot of interest to me. I'm interested in changing things
at a lower level. However that works, if I manage to build zope.component
backwards compatibility as an add-on then I'll have to worry about all of the
bits in zope.component, not just this.
Gary
, in this particular usage, ``IPublishTraverse(self,
request)`` would do what you want.
Gary
___
Zope-Dev maillist - Zope-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zope-dev
** No cross posts or HTML encoding! **
(Related lists -
https://mail.zope.org
of thing driven by who wants to do the work.
Gary
___
Zope-Dev maillist - Zope-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zope-dev
** No cross posts or HTML encoding! **
(Related lists -
https://mail.zope.org/mailman/listinfo/zope-announce
On Nov 30, 2009, at 11:51 AM, Chris McDonough wrote:
Tres Seaver wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Gary Poster wrote:
On Nov 27, 2009, at 6:32 AM, Martijn Faassen wrote:
Utility lookups versus adapter lookups
--
There was some
make utility registrations more powerful in a way that some people seem
to have been missing. It also makes things parallel with creation.
Gary
___
Zope-Dev maillist - Zope-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zope-dev
** No cross posts
On Nov 30, 2009, at 11:47 AM, Martijn Faassen wrote:
Hey,
Gary Poster wrote:
On Nov 27, 2009, at 6:32 AM, Martijn Faassen wrote:
...snipping here and elsewhere without further warning...
Utility lookup:
IFoo()
Named utility lookup:
IFoo(name=foo)
Utility lookup with a default
On Nov 30, 2009, at 3:49 PM, Charlie Clark wrote:
Am 30.11.2009, 20:24 Uhr, schrieb Gary Poster gary.pos...@gmail.com:
1) I very much like the idea of some helpers hanging around. However,
my current belief is that the factory methods ought to be callable
objects that allow
On Nov 30, 2009, at 4:13 PM, Zvezdan Petkovic wrote:
On Nov 30, 2009, at 4:05 PM, Zvezdan Petkovic wrote:
On Nov 30, 2009, at 2:24 PM, Gary Poster wrote:
3) I also think that utility is a bad name. Is singleton two letters
too long?
Yes and not because singleton is longer.
It just
On Nov 30, 2009, at 5:14 PM, Lennart Regebro wrote:
On Mon, Nov 30, 2009 at 22:40, Gary Poster gary.pos...@gmail.com wrote:
Then to the multiadapter concern I raised, all my real-world examples of
adapters are to adapt one object so it can be used in a certain way (to
integrate
* matter to a caller. You may not want the caller to need to care, and
it may be inconvenient to take into account circumstances where the caller
needs to care. But because this is Python, the caller still often does need
to
care.
Again, no surprise that I agree with this and following.
Gary
are nearing consensus on the variation of 3 that does
not include utilities.
Gary
___
Zope-Dev maillist - Zope-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zope-dev
** No cross posts or HTML encoding! **
(Related lists -
https://mail.zope.org
about singleton creation or
ownership of factory-returned objects, it can describe those
requirements using interfaces.
You are arguing for the unification of utilities and adapters?
Gary
___
Zope-Dev maillist - Zope-Dev@zope.org
https://mail.zope.org
On Dec 2, 2009, at 8:58 AM, Fred Drake wrote:
On Wed, Dec 2, 2009 at 8:42 AM, Gary Poster gary.pos...@gmail.com wrote:
You are arguing for the unification of utilities and adapters?
No. I'm arguing not to conflate utilities with the singleton pattern
or adaptation with ownership
...from my perspective.
= Things vaguely approaching consensus =
== General ==
There's a consensus that changes to the ZCA need to be backwards compatible.
The practical definition of that varies for different people.
== Syntactic ==
=== Tuple multi-adaptation ===
Example:
IFoo((bar,
the two reports from
the very small sample we have here of users.
I think it is unnecessarily risky for minimal gain, particularly when we have
another reasonable option.
= But Gary, I thought you didn't like ``adapt``? =
No, I don't. I think it is a hindrance to understanding, and I would
On Dec 2, 2009, at 11:09 PM, Martin Aspeli wrote:
Gary Poster wrote:
I think I could get fully behind the following proposal that others
have made (Shane I think was one of several?).
IFoo.adapt(...)
IFoo.utility(...)
I could get behind this too.
We'd need the current IFoo(context
chance of uptake in BFG.
I personally think these efforts do not make the potential consensus on
``adapt`` and ``utility`` methods any less interesting: they would be a
concrete win for my users.
Gary
___
Zope-Dev maillist - Zope-Dev@zope.org
https
On Dec 3, 2009, at 10:51 AM, Martijn Faassen wrote:
Gary Poster wrote:
[snip]
I personally think these efforts do not make the potential consensus
on ``adapt`` and ``utility`` methods any less interesting: they would
be a concrete win for my users.
I agree with much of what Gary
On Dec 3, 2009, at 12:08 PM, Martijn Faassen wrote:
Gary Poster wrote:
On Dec 3, 2009, at 10:51 AM, Martijn Faassen wrote:
Gary Poster wrote: [snip]
I personally think these efforts do not make the potential
consensus on ``adapt`` and ``utility`` methods any less
interesting: they would
for you. You could specify what parts you wanted help on.
Or would you prefer someone else to take charge?
Gary
___
Zope-Dev maillist - Zope-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zope-dev
** No cross posts or HTML encoding
it extends.
Then packages in the Zope world would start to use that Interface, I'd guess.
I don't know how I feel about it.
Gary
On Dec 17, 2009, at 11:51 AM, Chris McDonough wrote:
I'll throw out the obvious...
Why not subclass Interface in zope.component and make the required API
install and run?
Nominally, yes. If you are willing to let it have its way with your system.
Gary
___
Zope-Dev maillist - Zope-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zope-dev
** No cross posts or HTML encoding! **
(Related lists -
https
always the pre-2.5 icky __import__ hack for this if you need it. You
probably know it, or I can look it up if you want, but that's the only approach
I know of for this kind of issue in pre-2.5
Gary
___
Zope-Dev maillist - Zope-Dev@zope.org
https
.
Gary
___
Zope-Dev maillist - Zope-Dev@zope.org
https://mail.zope.org/mailman/listinfo/zope-dev
** No cross posts or HTML encoding! **
(Related lists -
https://mail.zope.org/mailman/listinfo/zope-announce
https://mail.zope.org/mailman/listinfo/zope )
is wildly nicer in the correct dvcs options
than svn.
The only limitation for bzr right now is that bzr doesn't handle svn externals.
That's slated to change this year, I think. If people are curious, Sidnei or
I could reach out and get more details of the timeline.
Gary
On Apr 15, 2010, at 1:27 PM, Tres Seaver wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Gary Poster wrote:
On Apr 15, 2010, at 12:51 PM, Sidnei da Silva wrote:
On Thu, Apr 15, 2010 at 12:41 PM, Leonardo Rochael Almeida
leoroch...@gmail.com wrote:
Thanks Tres and Sidnei,
My
at zc.buildout.recipe.egg (or whatever
we decide to call it). That solves that problem.
+1 from me. Graphs with cycles are pure evil.
I sure which my branches would land first, if they are ever to land. Any
changes to buildout are a pain. Big changes are a big pain.
Gary
On Jul 8, 2010, at 11:04 AM, Martijn Faassen wrote:
I propose the following adjustment:
try:
container = context.__parent__
except AttributeError:
container = ILocation(context).__parent__
+1
Gary
___
Zope-Dev maillist - Zope
? If you are, then this is a bug in
zc.recipe.egg (that I don't understand on the face of it; all tests pass, and
Options objects now have a query_bool method).
If you are not forced to use zc.buildout 1.5.0 somehow, I don't know what the
error there is.
Gary
On Aug 23, 2010, at 1:26 PM, Gary Poster wrote:
On Aug 23, 2010, at 12:36 PM, Andreas Jung wrote:
zc.recipe.egg 1.3.0 fails badly with
While:
Installing supervisor.
Traceback (most recent call last):
File
/Users/ajung/sandboxes/occ/eggs/zc.buildout-1.5.0-py2.6.egg/zc/buildout
On Aug 23, 2010, at 1:38 PM, Gary Poster wrote:
On Aug 23, 2010, at 1:26 PM, Gary Poster wrote:
On Aug 23, 2010, at 12:36 PM, Andreas Jung wrote:
zc.recipe.egg 1.3.0 fails badly with
While:
Installing supervisor.
Traceback (most recent call last):
File
/Users/ajung/sandboxes
On Aug 23, 2010, at 2:53 PM, Andreas Jung wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Gary Poster wrote:
1.3.1 has change and is released.
On it's failing in a different way:
An internal error occurred due to a bug in either zc.buildout or in a
recipe being used
On Aug 23, 2010, at 3:25 PM, Gary Poster wrote:
On Aug 23, 2010, at 2:53 PM, Andreas Jung wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Gary Poster wrote:
1.3.1 has change and is released.
On it's failing in a different way:
An internal error occurred due to a bug
the project so I could make a branch of it in Launchpad.
I'm neither the author nor the maintainer of the package. I'm happy to
transfer the Launchpad project to whomever makes sense.
Gary
___
Zope-Dev maillist - Zope-Dev@zope.org
https://mail.zope.org
101 - 195 of 195 matches
Mail list logo
