At one point, we had a style guide that recommended simple import
module import
statements for Zope code:
http://wiki.zope.org/zope3/ZopePythonStyleGuide
Today, I'm noticing a lot of commits with the change note Normalize
imports that
change all imports to from module import whatever, like
On Sat, Aug 18, 2012 at 6:46 AM, Wichert Akkerman wich...@wiggy.net wrote:
Doesn't the name zc.buildout imply that it is a Zope Corp project instead of
a Zope Foundation one? The author has also never been listed as the
foundation but Jim personally, which seems to imply zc.buildout never was
On Tue, Jun 5, 2012 at 10:00 AM, Jim Fulton j...@zope.com wrote:
I (and many people I know) find the interactive feature of
zdaemon annoying. I'd like to drop it, both to reduce annoyance
and to reduce the amount of code to maintain.
I've never found this a useful feature.
+1
--
Fred L.
On Tue, Mar 27, 2012 at 4:54 AM, Charlie Clark
charlie.cl...@clark-consulting.eu wrote:
We had bug reports about Web sites sending BOM different from the HTTP
header.
In other words... the web will continue to thrive on hacks and
sniffing data to
support users' expectations in spite of the
On Tue, Mar 27, 2012 at 6:36 AM, Charlie Clark
charlie.cl...@clark-consulting.eu wrote:
True but I think that the problem was largely of our own making in not
coming up with one, preferably only one way of handling this. Re-reading
Marius' post I was struck by the whole idea of the http-server
On Thu, Feb 23, 2012 at 2:54 AM, Miano Njoka mianonj...@gmail.com wrote:
Yes, this is true, but why strip out the meta tag from the resulting HTML?
Two reasons:
1. It may be incorrect.
2. If multiple templates are used to construct a response, different
values may be included from each
On Wed, Feb 22, 2012 at 10:28 AM, Miano Njoka mianonj...@gmail.com wrote:
meta http-equiv=content-type content=text/html;charset=UTF-8
/ tags were being stripped out from ZPT templates. Is there a reason
for this?
As I recall, the rationale goes like this:
1. We're sniffing the input encoding
On Fri, Jan 6, 2012 at 2:33 AM, Chris Withers ch...@simplistix.co.uk wrote:
if I implemented support for filters inside handler sections, would you
crank out a release?
I'd definitely consider it. Someone made a mess of the ZConfig build
(some silliness about using setup.py as a test driver),
On Thu, Jan 5, 2012 at 1:47 PM, Chris Withers ch...@simplistix.co.uk wrote:
Is there any way in ZConfig to allow a file that looks like this:
...
...or some other way of spelling multi-line values for a key?
Nope, sorry. I played with adding that at one point, but didn't have
enough time or
On Wed, Nov 9, 2011 at 3:57 AM, Chris Withers ch...@simplistix.co.uk wrote:
Is it Bejni's address, the email in question or that isn't coming from
server1.simplistix.co.uk?
Benji's email address is benji at benjiyork.com.
-Fred
--
Fred L. Drake, Jr. fred at fdrake.net
A storm broke
On Wed, Jun 29, 2011 at 7:57 AM, Hanno Schlichting ha...@hannosch.eu wrote:
Ideally I'd like to get avoid storing such information in the ZODB at
all and would much prefer a volatile attribute, a thread local or
something on the filesystem. But maybe I'm missing something here were
this
On Mon, Apr 11, 2011 at 8:02 AM, Sylvain Viollon sylv...@infrae.com wrote:
Or if you have a descent schema system that include this information.
No, this really has to do with the widgets. A widget may well use
Unicode data regardless of the expected result type. And most
interesting schema
The zope.lifecycleevent package provides a pile of events that are
generated in a lot of places. The implementation contains a single
helper function, modified(), that appears to be intended for public
consumption (it's not referenced in the package). However, it's not
mentioned in the
On Tue, Nov 30, 2010 at 3:12 AM, Adam GROSZER agros...@gmail.com wrote:
zope.testing tests fail on windows.
The blamelist might not be real, because this is the first build.
I think the blame-list is right. I think this requires an easy fix to
the test. Will do.
-Fred
--
Fred L. Drake,
On Wed, Nov 10, 2010 at 8:23 AM, I said:
There's a package called zc.signalhandler in the Zope Corporation
repository that I'll be open-sourcing.
This is now available on svn.zope.org. The tests pass with Python
2.4, 2.5, 2.6, and 2.7.
I've added a brief README.txt to show how it's used;
On Wed, Nov 10, 2010 at 2:47 AM, Christian Theune c...@gocept.com wrote:
We have a ZTK-based app and found that the server provides neither
signal handling to rotate logs nor a zopectl command. Does anybody
remember wether this was ever built?
Christian,
If you want size- or time-based
On Thu, Oct 7, 2010 at 8:21 AM, Charlie Clark
charlie.cl...@clark-consulting.eu wrote:
I was wondering whether it's possible to use callables for schema
vocabularies without registering them first?
...
I'm sure it should be possible but my weak and feeble brain has somehow
failed to solve the
On Thu, Oct 7, 2010 at 8:35 AM, Charlie Clark
charlie.cl...@clark-consulting.eu wrote:
I thought we were consolidating the mailing lists? It is a developer's
rather than a user's question but I would agree not related to ZTK
development.
Another consolidation? We already tossed the zope3-dev
On Thu, Oct 7, 2010 at 8:45 AM, Charlie Clark
charlie.cl...@clark-consulting.eu wrote:
This was the suggestion at the summit:
http://wiki.zope.org/ztk/ZopeSummit2010Summary
Interestingly, I can't find anything that suggests consolidation by
searching that page for mail or list. Was that what
On Tue, Jul 6, 2010 at 11:00 AM, Tres Seaver tsea...@palladion.com wrote:
Given that ZODB3 and zope.app.container are still non-optional
dependencies of the package, I can't see any reason not to restore those
base classes.
I mentioned it on IRC, but wanted to mention here as well for
On Fri, Jul 9, 2010 at 9:08 AM, Hanno Schlichting ha...@hannosch.eu wrote:
I think zope.dublincore causes the breakage in some zope.app packages.
This one's a sticking point for a large application here as well (one where
we're trying to move to the ZTK as the base). I think I'm sticking to
On Wed, Jun 30, 2010 at 3:47 PM, Hanno Schlichting ha...@hannosch.eu wrote:
On behalf of the Zope Toolkit release team and the Zope community, I'm
happy to announce the first 1.0 alpha release of the Zope Toolkit.
I've yet to hear any response to my post about non-backward-compatible classes:
Sorry for bring an old thread back up, but it's relevant.
On Tue, Jan 26, 2010 at 4:06 AM, Souheil CHELFOUH troll...@gmail.com wrote:
The tests pass and nothing has been changed but the imports.
Actually, the base classes for SessionCredentialsPlugin changed, and
no longer include these:
On Sat, May 29, 2010 at 1:36 AM, Christian Theune c...@gocept.com wrote:
So I hope to see many of you on Wednesday 2010-06-16.
I don't know who can add entries to the Google calendar with the weekly
IRC meeting, but it would be nice if bug days were also added to that.
-Fred
--
Fred L.
On Fri, Apr 30, 2010 at 3:57 PM, Hanno Schlichting ha...@hannosch.eu wrote:
If it is intended to be backwards compatible and seems to be so, I'd
say go with 1.3. It sounds like a new package dependency, like we have
had many others in minor releases.
Since when were new dependencies not
On Fri, Apr 30, 2010 at 4:10 PM, Hanno Schlichting ha...@hannosch.eu wrote:
Going from 1.2 to 1.3 is a minor new feature release.
Ok, if we're talking about changing the second number, this is fine.
The wording in a minor release didn't connote between minor
releases for me; I recognize I may
On Fri, Apr 23, 2010 at 3:08 PM, Tres Seaver tsea...@palladion.com wrote:
Done. The 3.6.3 release is up on PyPI:
I guess I should get out more; just noticed this thread.
Changing the stored permission names is a big deal. If a permission
gets stored with zope.dublincore 3.6.3, then an
On Tue, Apr 20, 2010 at 7:44 AM, Wichert Akkerman wich...@wiggy.net wrote:
You may want to move it outside the zope.* namespace to encourage that :)
People interested in interfaces or component architectures don't seem
to mind using zope.interface or zope.component; those get selected on
their
On Tue, Apr 20, 2010 at 2:58 PM, Christian Theune c...@gocept.com wrote:
zope.testing uses the attribute '__bases__' to store the information what
the base layers are. __*__ are supposedly Python internal attributes.
Specifically __bases__ is known to be used to store information which base
On Tue, Apr 20, 2010 at 3:47 PM, Christian Theune c...@gocept.com wrote:
I don't know (or at least can't remember) all of the history of the
discussion about that, but I wouldn't argue about following standard
protocols.
It *is* arguable that __name__ is a standard protocol. It's also not
On Tue, Apr 20, 2010 at 4:09 PM, Christian Theune c...@gocept.com wrote:
I think the two of us agreeing, right?
You I are. I think Jim's not (which is fine, of course).
-Fred
--
Fred L. Drake, Jr.fdrake at gmail.com
Chaos is the score upon which reality is written. --Henry Miller
On Fri, Apr 16, 2010 at 2:40 PM, Tres Seaver tsea...@palladion.com wrote:
:mod:`zope.testing.formparser`
Parses rendered HTML forms back to datastructures. Maybe useful
in tests which consume rendered output.
No ZTK tests use this module.
I believe this may be used in tests of some
On Fri, Apr 9, 2010 at 10:27 AM, Fred Drake fdr...@gmail.com wrote:
Setting the ZF as maintainer appears sufficient to appease the policy checker.
Or not. The fixer script won't edit this, but the checker script will
still whine about it.
Changing the author to the ZF really isn't a good thing
On Fri, Apr 9, 2010 at 10:43 AM, Tres Seaver tsea...@palladion.com wrote:
It seems reasonable to me that it *should* work, though I'm not sure how
to write the code which tests that.
See my later follow-up as well.
In particular, while it *may* be reasonable to set the ZF as
maintainer, it's
On Thu, Apr 8, 2010 at 8:24 AM, Christian Theune c...@gocept.com wrote:
Maybe a specialised part-name, like versions would be helpful so that
buildout could pre-populate that part during initialisation and then
allow configurations to override individual values.
It's probably worth mentioning
On Thu, Apr 8, 2010 at 9:03 AM, Christian Theune c...@gocept.com wrote:
The special that I was referring to was the fact that you don't have to
spell a recipe name for that section (like the buildout section).
There are many times you can have a section that isn't a part; the
buildout section
On Thu, Apr 8, 2010 at 1:13 PM, Tres Seaver tsea...@palladion.com wrote:
I expect to see the list of flagged projects drop significantly on the
next run.
Is this list available somewhere for us to review?
-Fred
--
Fred L. Drake, Jr.fdrake at gmail.com
Chaos is the score upon which
On Tue, Apr 6, 2010 at 10:25 PM, Martin Aspeli optilude+li...@gmail.com wrote:
So this is still in pyexpat C code as far as I can tell. :-(
This is saddening.
I've not managed a 64-bit sandbox, which I suspect is what I really
need to debug that. Will shoot for this weekend, since last didn't
On Wed, Apr 7, 2010 at 9:29 AM, Martin Aspeli optilude+li...@gmail.com wrote:
I have a slight suspicion that lxml is involved somewhere. I've managed
to make it crash reliably simply by doing a parse of an XML file, and I
think such a parse may be happening as a side effect of a module import
On Fri, Apr 2, 2010 at 10:51 AM, Marius Gedminas mar...@gedmin.as wrote:
Maybe it would make sense to add a command-line option for buildout to
override version pins?
bin/buildout -t 2 -c configfile --pin zc.buildout=1.4.3 \
--pin setuptools=0.9c11
with --pin zc.buildout=
On Thu, Apr 1, 2010 at 6:07 AM, Martin Aspeli optilude+li...@gmail.com wrote:
Any tips on how to debug or similar experiences would be appreciated!
If you're on some Unix flavor, you should be able to deconstruct the
return code from the runzope process to determine if the app was
killed by a
On Thu, Apr 1, 2010 at 7:29 AM, Martin Aspeli optilude+li...@gmail.com wrote:
I'm pretty sure it is. The pdb rabbit hole ended at pyexpat.c. I can't
see what's going on there, but when I did 'r' it blew up.
If you can point me at the ZCML file you were trying to parse (or
email it to me
On Thu, Apr 1, 2010 at 2:17 PM, Tres Seaver tsea...@palladion.com wrote:
/me is deeply suspicious of *any* distro-provided python, ever.
I'm also suspicious of 64-bit builds, given that I'm not using one on
my dev machine.
I've picked up the OpenSuSE installation ISOs; hopefully that's close
On Tue, Mar 9, 2010 at 10:53 AM, Baiju M mba...@zeomega.com wrote:
Any idea how difficult it is to create optional C extensions
for these packages:
zope.proxy will be fairly difficult to implement without C. Alternate
Python implementations may be able to use extensions written in other
On Tue, Mar 2, 2010 at 11:32 AM, Christian Theune c...@gocept.com wrote:
here's my first shot at a summary of today's meeting.
Thanks, Christian! I definitely appreciate this summary, since I was
visually impaired at the time of the meeting (and still am, but it's
returning...).
-Fred
--
On Wed, Jan 6, 2010 at 10:44 AM, Hermann Himmelbauer du...@qwer.tk wrote:
Microsoft, really? Interesting, I personally think about IBM (Big Blue)...
The Blue Screen of Death definitely signifies Microsoft to me!
That also qualifies as a serious bad-vibes indicator. ;-)
-Fred
--
Fred L.
On Tue, Dec 29, 2009 at 10:39 AM, Wichert Akkerman wich...@wiggy.net wrote:
It seems that you want to have a 'ZTK+' which aims to be backwards
compatible with Zope 3 but is somehow not Zope 3 itself. That is
something that not everybody appears to be interested in judging by the
lack of
On Tue, Dec 29, 2009 at 4:04 PM, Martijn Faassen faas...@startifact.com wrote:
But right now we need to provide some guidance for how people can move
away from these packages in a sane manner. And we should make sure we
continue to test the zope.app.* packages when we make ZTK changes, for
the
On Tue, Dec 29, 2009 at 4:19 PM, Martijn Faassen faas...@startifact.com wrote:
Let me sketch out some ideas for a plan:
Thankfully you started getting this done while I was distracted from
my email by a meeting. :-) I'll send this anyway, since there's
probably a few points of contention
On Tue, Dec 29, 2009 at 6:11 PM, Martijn Faassen faas...@startifact.com wrote:
* the ZTK is new, therefore the ZTK doesn't need to care about Zope 3 at
all.
I'm strongly in this camp. The other camps can readily be supported
on top of this view of the ZTK by providing new names for
Can someone set me up with PyPI privs for zope.contenttype?
Thanks!
-Fred
--
Fred L. Drake, Jr.fdrake at gmail.com
Chaos is the score upon which reality is written. --Henry Miller
___
Zope-Dev maillist - Zope-Dev@zope.org
On Mon, Dec 28, 2009 at 4:57 PM, Chris Withers ch...@simplistix.co.uk wrote:
I think if your development environment involves Windows checkouts, they
happen more often that you'd like, especially when a single Windows
developer doesn't have svn:eol-style set for all types that end up being
On Thu, Dec 24, 2009 at 10:52 AM, Zvezdan Petkovic zvez...@zope.com wrote:
Of course, it may be worth trying if there is a critical mass of supporters.
Alternately, there could be a way of extending the standard doctest to
achieve this feature without pushing it into the standard library.
I'm
On Wed, Dec 2, 2009 at 2:21 AM, Thomas Lotze t...@gocept.com wrote:
To be honest, I just don't see why this whole singleton business shouldn't
be orthogonal to the concepts of the component architecture.
Well said. If an application cares about singleton creation or
ownership of
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 of the resulting adaptation.
-Fred
--
Fred L. Drake,
On Tue, Dec 1, 2009 at 11:34 AM, Martin Aspeli optilude+li...@gmail.com wrote:
I think
that logically, these are two different concepts that meet two different
sets of use cases.
Agreed here. This is essential to this discussion.
I've been quite surprised that there are so many who argue to
On Mon, Nov 30, 2009 at 5:14 PM, Lennart Regebro rege...@gmail.com wrote:
True. For me utilities are tools. Like CMFs portal_whatever. But in
Zope3 even small stupid singleton objects are utilities in some cases,
and that is confusing for a beginner.
I wonder how many typical Python
On Wed, Oct 7, 2009 at 11:10 AM, Hanno Schlichting ha...@hannosch.eu wrote:
If someone would document srichter's magic grant-all-powerful PyPi
script, I'd run it :)
That's a horrible thing to do to somebody!
Note that I'm not smiling, either. It's too easy to grant people
access to way too
On Wed, Oct 7, 2009 at 11:27 AM, Thomas Lotze t...@gocept.com wrote:
OTOH, even with good usability I'd rather not have rights for packages I'm
not interested in, just to be able to deny responsibility if anything goes
wrong with one of them.
It's entirely reasonable for maintainers to have
On Fri, Sep 18, 2009 at 11:53 AM, Tres Seaver tsea...@palladion.com wrote:
- - Any package which depends on a zope.* package which is *not* part
of the ZTK should itself be removed from the ZTK.
+1
- - As a corollary, any package which depends on any other probationary
package is
On Fri, Sep 11, 2009 at 8:53 AM, Martijn Faassen faas...@startifact.com wrote:
So, could you please follow this policy for ZTK packages in SVN?
I suspect it would help if packages that are part of the ZTK have that
indicated somewhere convenient, like near where the version number is
specified
On Fri, Sep 11, 2009 at 10:30 AM, Gary Poster gary.pos...@gmail.com wrote:
Also, since I'm also in the setup.py should be able to specify
minimum versions camp (admittedly unlike others, such as Benji, to my
continued surprise)
I agree with you on this point; it's quite useful for setup.py to
On Wed, Sep 9, 2009 at 8:31 AM, Christian Theunec...@gocept.com wrote:
As a side effect this will also make svn/svn+ssh work in a nicer way
(IMHO) as the externals will follow the protocol of what you used for
checkout.
I like that externals to svn:... are read-only, though I don't know
The meta http-equiv=content-type content=... is used to identify
the encoding of the file providing the template.
This has nothing to do with the encoding of the output resource, which
is determined by the application. In the case of the Zope publisher,
Unicode output from the template is
2009/8/6 Fabio Tranchitella kob...@kobold.it:
Am I correct saying that your idea is to restrict the ZTK to the packages
defined as the intersection of the dependencies of zope2, zope3 and grok?
ZTK = intersection ( zope2-dependencies , zope3-dependencies, grok )
That's my understanding of
On Mon, Jul 13, 2009 at 3:36 PM, Marius Gedminasmar...@gedmin.as wrote:
Fortunately, the NotImplementedError in ZCMLLayer's tearDown is just a
precaution, 99% of the time it is sufficient to run CleanUp.tearDown
to get the global state restored to its pristine condition.
Keep in mind that a
I just released zope.interface 3.5.2, which adds only this bug fix:
- BaseAdapterRegistry.unregister, unsubscribe: Remove empty portions of
the data structures when something is removed. This avoids leaving
references to global objects (interfaces) that may be slated for
removal from the
On Wed, Jul 1, 2009 at 12:30 PM, Hanno Schlichtingha...@hannosch.eu wrote:
Just did that for Python 2.4 to 2.6.
Thanks, Hanno!
-Fred
--
Fred L. Drake, Jr.fdrake at gmail.com
Chaos is the score upon which reality is written. --Henry Miller
___
On Tue, May 12, 2009 at 10:56 AM, Wolfgang Schnerring w...@gocept.com wrote:
Looks good so far. Could someone do a release of zc.recipe.cmmi
(or grant 'wosc' pypi access so I can do it myself)?
Done.
-Fred
--
Fred L. Drake, Jr.fdrake at gmail.com
Chaos is the score upon which reality
On Fri, May 15, 2009 at 2:57 AM, Chris McDonough chr...@plope.com wrote:
It's a partial step towards getting rid of a dependency that zope.intid has on
zope.container. I'm thinking that maybe that IContained interface belongs in
some other package (e.g. maybe zope.contained). That Container
2009/4/2 Marius Gedminas mar...@gedmin.as:
looks like a mistaken assignment of a tuple to a name, while
setup(
many lines
foo=bar,
many more lines
)
looks like a function call.
Agreed; the common use of spaces around the equal signs in setup.py is
a holdover from Greg Ward's
On Wed, Mar 18, 2009 at 7:59 AM, Roger Ineichen d...@projekt01.ch wrote:
As far as I know it is valid to skip attributes for empty values
but for some attributes it is not valid to use empty values.
Let's not use the term valid in this context, as it's pretty overloaded here.
In the general
On Tue, Mar 10, 2009 at 9:08 AM, Malthe Borch mbo...@gmail.com wrote:
How do folks feel about changing this behavior in ``zope.pagetemplate``.
The change would need to be in zope.tal.
I'm ambivalent; while it makes sense to me in isolation, the affect on
existing templates is undesirable, and
On Thu, Mar 5, 2009 at 1:43 PM, Martijn Faassen faas...@startifact.com wrote:
* we shouldn't create any new extra dependencies from now on.
+1
* we should investigate ways to remove the need for 'extra' dependencies.
+1
I therefore think zope.app.testing is one package we should be looking
On Thu, Feb 19, 2009 at 11:03 AM, Jim Fulton j...@zope.com wrote:
BTW, I strongly discourage from imports. (I didn't always have this
opinion, but have seen the error of my ways. Thanks to Fred Drake for
nudging me in this direction.) IMO, this is wildly more important than
any of the issues
On Thu, Feb 5, 2009 at 12:52 PM, Tres Seaver tsea...@palladion.com wrote:
I'm fixing dependent packages broken by my changes: could you add me to
zope.app.container as well?
Done.
-Fred
--
Fred L. Drake, Jr.fdrake at gmail.com
Chaos is the score upon which reality is written. --Henry
On Thu, Jan 29, 2009 at 4:01 AM, Martijn Faassen faas...@startifact.com wrote:
I believe it'd be nicer to extract any ZCML related stuff from
zope.component at some point and put it into zope.componentzcml or
something like that. We could then decide to move the class and
module directives in
On Wed, Dec 17, 2008 at 6:36 PM, Tres Seaver tsea...@palladion.com wrote:
If we just leave the name importable from the old location, what is
hurt? The major downside is that people won't learn about the new
location. I consider this to be less an issue than the two problems I
outline above.
On Mon, Dec 8, 2008 at 10:56 AM, Benji York [EMAIL PROTECTED] wrote:
This setting apparently causes problems for people who use Emacs, so
for zope. and zc. packages at least, we don't use --auto-color.
I've been using this under Emacs for a while, and haven't experienced
any tool-related
On Fri, Nov 14, 2008 at 9:54 AM, Joachim König [EMAIL PROTECTED] wrote:
This is only required at runtime, so this is not a (circular) build or
install dependency,
but as the NetBSD-pkgsrc build infrastructure wants to generate the
.pyc/.pyo files
at installation time, I still have a problem
On Tue, Oct 7, 2008 at 11:00 AM, Zvezdan Petkovic [EMAIL PROTECTED] wrote:
However, are we _certain_ that the socket is closed after this?
smtplib does *not* close the client socket if there's an exception
while sending the quit message or processing the response. It could
be best if
On Tue, Sep 9, 2008 at 2:37 PM, Dieter Maurer [EMAIL PROTECTED] wrote:
The syntax would be a bit more cumbersome -- but on the other
hand, it would be more explicit :-)
Seems to me zope.component.getMultiAdapter(...) is sufficient as-is,
and shares the benefit of explicitness.
That's
On Sun, Sep 7, 2008 at 3:29 PM, Chris Withers [EMAIL PROTECTED] wrote:
I can't see any problems with this, can anyone else?
There's the backward-compatibility issue, which is a showstopper.
There's plenty of code that does this:
adapter = package.interfaces.IFoo(object, None)
Changing the
On Thu, Sep 4, 2008 at 8:16 AM, Martijn Faassen [EMAIL PROTECTED] wrote:
Does the hidden status explain it not being picked up by buildout?
Anyway, sorry for getting confused there.
No; the hidden bit only affects the normal PyPI user interface.
-Fred
--
Fred L. Drake, Jr. fdrake at
On Wed, Sep 3, 2008 at 1:47 PM, Benji York [EMAIL PROTECTED] wrote:
Maybe we should create a new namespace package for browser code.
How about zope.browser?
Heh. That's just sooo long. Perhaps it should be zobr. :-)
-Fred
--
Fred L. Drake, Jr. fdrake at gmail.com
Chaos is the score
On Sat, Aug 30, 2008 at 2:03 AM, Dieter Maurer [EMAIL PROTECTED] wrote:
However, I am not sure whether our observations for a single
large zip (in fact, we use two: one for our application, the other for
Python's
runtime library) is valid for the case of many small zipped eggs.
The
On Fri, Aug 29, 2008 at 5:13 PM, Malthe Borch [EMAIL PROTECTED] wrote:
Log message for revision 90599:
Move test-dependencies to 'extras'.
This is a controversial change; can we avoid making changes like this
until a policy is agreed upon?
The controversy surrounding this has been discussed
On Fri, Aug 29, 2008 at 5:26 PM, Malthe Borch [EMAIL PROTECTED] wrote:
I didn't know there was a controversy, but I do remember that there was
consensus that ``extras_require`` is not the most elegant solution.
Oh, there is!
If you can advise a different way to avoid pulling in
On Thu, Aug 21, 2008 at 8:45 AM, Thomas Lotze [EMAIL PROTECTED] wrote:
If someone gives me access to the package on PyPI (username: tlotze),
I can also upload it there.
Done.
-Fred
--
Fred L. Drake, Jr. fdrake at gmail.com
Chaos is the score upon which reality is written. --Henry Miller
On Sat, Aug 2, 2008 at 9:27 AM, Benji York [EMAIL PROTECTED] wrote:
Still, it's likely that someone was using it and their buildouts are now
broken. We should have instead generated a proper release with a higher
version number and left the dev release alone.
Yes.
It would be even better if
On Sat, Jul 26, 2008 at 7:36 AM, Hanno Schlichting [EMAIL PROTECTED] wrote:
Would someone (Jim, Philikon, Fred) be willing to do a new zope.interface
release or give me access rights on PyPi to do it myself?
I've added Stephan Richter and Andreas Jung to the project on PyPI,
since I could
I often find that I debug problems by inserting a pdb.set_trace() in
code, and then quitting the debugger with q once I've gathered
information I need to make code changes. This causes a BdbQuit
exception to be raised and propagated to the test runner. The
resulting traceback isn't actually
On Wed, Jul 16, 2008 at 10:45 AM, Stephan Richter
[EMAIL PROTECTED] wrote:
But I agree. The system supports simple type and that is one of the use cases.
While I originally wanted to add at least 2 of the events to the IAnnotations
adapter itself, I agree with you that the overhead penalty
On Wed, Jul 16, 2008 at 11:33 AM, Roger Ineichen [EMAIL PROTECTED] wrote:
Even worse, I store objects in the annotation wich are added to
a real IContainer as items somewhere else. This objects are created,
added etc. already in the other container and provide locations
from there.
Only the
On Wed, Jul 16, 2008 at 11:46 AM, Fred Drake [EMAIL PROTECTED] wrote:
I don't see any need for a way to suppress them, since they shouldn't
trigger any subscribers for the normal containment events.
Based on some discussion here, I realize that my position may not be
terribly clear. Just
On Wed, Jul 16, 2008 at 2:59 PM, Andreas Jung [EMAIL PROTECTED] wrote:
we maintain some modules that should work against different versions of
dependent module. E.g. my z3c.sqlalchemy module should work with
Sqlalchemy 0.3.X and zope.interface 3.0.X
or
SQLAlchemy =0.4.X and
On Tue, Jul 15, 2008 at 12:30 PM, Stephan Richter
[EMAIL PROTECTED] wrote:
Thus I propose:
- Add ObjectCreatedEvent event notification to zope.annotation factory call.
By this, I presume you mean the stuff in zope.annotation.factory; is that right?
In our group, we've decided to avoid that
On Tue, Jul 15, 2008 at 2:28 PM, Stephan Richter
[EMAIL PROTECTED] wrote:
Right, but annotations are still content in their own right. And we fire
events that are specific to annotations all the time, for example in workflow
instances.
I agree that it's reasonable to fire some event when an
Someone changed the ZCML that registers the gopherlib module (why???) to this:
!-- This package has been deprecated in Python 2.5; let's use a cheap way
of detecting Python 2.5 by checking whether the package regex exists,
which has been deleted in that version. --
module
On Thu, Jun 26, 2008 at 12:33 PM, Stephan Richter
[EMAIL PROTECTED] wrote:
I did as you were aware of. :-)
I wasn't, because I didn't look. Note also that I wasn't asking who;
I don't think that matters.
The gopherlib module was there before, I just shut up the deprecation warning.
Using
1 - 100 of 226 matches
Mail list logo
