', 'FAILURE', or 'UNKNOWN' (a checkout or build failure), and names
the "configuration" being tested.
[1] https://mail.zope.org/mailman/listinfo/zope-tests
> BTW I'm a volunteer.
Thank you very much for your efforts!
Tres.
- --
=
; changes are impossible.
We still mostly treat them as off-limits, even the three years after we
started the effort to break the monolith apart. That change should have
made it technically feasible to do backward-incompatible changes, but we
haven't yet worked out how to make tha
objects to this change, then I'll commit
> it to the trunk.
If the tests all pass, then I would say go ahead and commit it now, but
add tests to verify that the new feature works as you expect.
Tres.
- --
=======
Tres Seave
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
yuppie wrote:
> Tres Seaver wrote:
>> Chris Withers wrote:
>>> By all means, document virtualenv as an option, but blessing it as "the
>>> one true way" is a bit much...
>
> I'm also surprised tha
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Chris Withers wrote:
> Tres Seaver wrote:
>> Installing Zope
>> -===
>> +---
>>
>> -Unless using buildout to build a zope instance as described
>> -:ref:`below `, you will need to inst
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Marius Gedminas wrote:
> On Sun, Feb 28, 2010 at 05:05:51PM +0100, Wichert Akkerman wrote:
>> On 2010-2-26 18:25, Tres Seaver wrote:
>>> Wichert Akkerman wrote:
>>>> I see this as naming confusion. In this day and age ev
ill both a moderator role and have my own stakes in
> the topics, so please bear with me if I'm struggling balancing that.
Sounds good -- I'll try to be there. It might be helpful to send out a
reminder a bit earlier in the day, so that those of us still in a
caffeine-deplete
None)
> +return getattr(context, '__name__', None)
>
> def breadcrumbs(self):
> context = self.context
Kettle to pot: Did you add a test?
Tres.
- --
===
Tres Seaver +1 540-429-0999
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Wichert Akkerman wrote:
> On 2/25/10 17:08 , Tres Seaver wrote:
>> -BEGIN PGP SIGNED MESSAGE-
>> Hash: SHA1
>>
>> Adam GROSZER wrote:
>>> Hello,
>>>
>>> Looks like zope.publisher burps on
ASCII, with other characters encoded[1]. IRIs and IRLs are
a different thing altogether.
- - Headers in responses must *not* be Unicode.
Your application needs to make the URL header-safe before calling
redirect, likely by using 'urlencode'.
[1] http://tools.ietf.org/html/rfc1738#se
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hanno Schlichting wrote:
> On Tue, Feb 23, 2010 at 1:26 AM, Tres Seaver wrote:
>> Hanno Schlichting wrote:
>>> -2.12.1 (unreleased)
>>> +2.13.0 (unreleased)
>>> ---
>>>
>>> +-
.
I foresee problems there: the __init__ imports stuff from the modules
which use MessageFactory.
Tres.
- --
===
Tres Seaver +1 540-429-0999 tsea...@palladion.com
Palladion Software "Excellence b
Objections?
Tres.
- --
===
Tres Seaver +1 540-429-0999 tsea...@palladion.com
Palladion Software "Excellence by Design"http://palladion.com
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (GNU/Linu
ot to defeat the ZODB persistent
> + reference optimization. Refs https://bugs.launchpad.net/zope2/+bug/143657.
Is this really worth treating as a new major version? There is no API
change involved, right? Just faster?
Tres.
- --
===
Tres Seaver
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Sylvain Viollon wrote:
> On Sat, 06 Feb 2010 02:14:07 -0500
> Tres Seaver wrote:
>
>Hello,
>
>> There was never any guarantee that Globals would be fully popluated
>> before the start of product initialization:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Wichert Akkerman wrote:
> On 2010-2-8 22:38, Tres Seaver wrote:
>> In the mean time, you could patch the file in via your debian/ control
>> stuff, I guess. The Ubuntu / Debian interpretation of "legality of
>> distri
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Gediminas Paulauskas wrote:
> 2010/2/8 Tres Seaver :
>> -BEGIN PGP SIGNED MESSAGE-
>> Hash: SHA1
>>
>> Gediminas Paulauskas wrote:
>>> Hello Zope Developers,
>>>
>>> I am packagin
.
>
> Who will add a copy of the license to each package in Zope SVN? When?
$ wget \
http://pypi.python.org/packages/source/Z/Zope2/Zope2-2.12.3.tar.gz
$ tar tzf Zope2-2.12.3.tar.gz | grep -i license
Zope2-2.12.3/src/ZServer/medusa/dist/license.html
Zope2-2.12.3/ZopePublicLic
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Andreas Jung wrote:
> Charlie Clark wrote:
>> Am 06.02.2010, 21:56 Uhr, schrieb Tres Seaver
>> :
>
>>> You aren't ever going to get ZSQL "migrated" to use ZPT. ZPT is
>>> a really poor fit for
Folks writing
"modern" apps tend to favor non-dynamic SQL anyway (using "placeholder
variables") and so would just not use ZSQL.
Tres.
- --
===
Tres Seaver +1 540-429-0999 tsea...@palladion.com
Palladion
from App.config import getConfiguration
config = getConfiguration()
if config.debug_mode:
....
Tres.
- --
===
Tres Seaver +1 540-429-0999 tsea...@palladion.com
Palladion Software "Excellence by Des
e code to other parts of the codebase to
make that easy, even assuming it were desirable.
Tres.
- --
===
Tres Seaver +1 540-429-0999 tsea...@palladion.com
Palladion Software "Excellence by Design"http://palladion.com
-BEGIN PGP SIGNATURE-
Version: GnuPG v
ing out DTML support for
applications, however.
Tres.
- --
=======
Tres Seaver +1 540-429-0999 tsea...@palladion.com
Palladion Software "Excellence by Design"http://palladion.com
-BEGIN PGP SIGNATURE-
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Baiju M wrote:
> On Tue, Jan 26, 2010 at 11:08 PM, Tres Seaver wrote:
>> -BEGIN PGP SIGNED MESSAGE-
>> Hash: SHA1
>>
>> Baiju M wrote:
>>
>>> What about committing SVG (source) file, so that others
ved works" (and
therefore must be GPL'ed), unless the "derived work" is covered by the
font exception.
Tres.
- --
=======
Tres Seaver +1 540-429-0999 tsea...@palladion.com
Palladion Software &quo
ot;document" (an image) doesn't "embed" the font itself,
but merely contains pixels generated by rendering the font. In
copyright terms, this is no different than ink on paper printed from
metal type: the font author has no claim on the ink / paper as a
"derived work" un
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Baiju M wrote:
> On Mon, Jan 25, 2010 at 5:14 AM, Tres Seaver wrote:
>> -BEGIN PGP SIGNED MESSAGE-
>> Hash: SHA1
>>
>> Christophe Combelles wrote:
>>> Jens Vagelpohl a écrit :
>>> On 1/24/10 1
font you use). Or ask for a more
permissive (non-copyleft) licence, such as one of the Creative Commons
licenses. If neither of those options is available, then I would ask
the foundation board for permission to check in the image.
[1] http://www.fsf.org/blogs/licensing/20050425novalis
[2] http://www.g
the right
thing to do: suppose the user reloads the login form for some reason
(maybe their browser crashes, whatever).
Tres.
- --
=======
Tres Seaver +1 540-429-0999 tsea...@palladion.com
Palladion Software &q
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Wichert Akkerman wrote:
> On 2010-1-22 18:41, Tres Seaver wrote:
>> -BEGIN PGP SIGNED MESSAGE-
>> Hash: SHA1
>>
>> Wichert Akkerman wrote:
>>> On 1/22/10 14:46 , Lennart Regebro wrote:
>>>> * B
oyed ones do use some ZTK packages beyond the bare ZCA parts. e.g.
the catalog code, SMTP integration, etc.
Tres.
- --
===
Tres Seaver +1 540-429-0999 tsea...@palladion.com
Palladion Software "Excellence by
ting/
References
- --
[1] http://foundation.zope.org/bylaws/zope_foundation_bylaws.pdf
[2] http://stv.sourceforge.net/aboutopenstv
[3] http://stv.sourceforge.net/votingmethods/meek
Tres.
- --
=======
Tres Seaver +1 540-429-0
d what that
> really is :-)
I argued early on that there were actually multiple Zope Toolkits, so I
am very much in favor of identifying coherent subsets, particularly if
that makes it easier to identify the folks / communities of interest
attached to them.
Tres.
- --
===
f formal recognition to the
"ZCA" / "bicycle seat toolkit" subset, in that those packages are
supposed to try harder to keep compatibility with Python 2.4 than the
larger set which is the ZTK proper. This de facto recognition is
precisely because the ZCA pacakges are already in w
gly referred to it in the
past as the "bicycle seat toolkit."
Tres.
- --
=======
Tres Seaver +1 540-429-0999 tsea...@palladion.com
Palladion Software "Excellence by Design"http://palladion.com
dencies).
Its notions of a view is radically different than a Zope3 view, for
instance: in BFG, a view is nearly always just a function or other
callable, and only rarely (primarily in migrated code) a class / factory
taking context and request and returning a "view object."
In 2010, *none*
ould prefer bluebr...@zope.org
> And I would prefer the mailman admin user as mbaiju AT zeomega.com
Done: you are good to go.
Tres.
- --
=======
Tres Seaver +1 540-429-0999 tsea...@palladion.com
Palladion Software "Exc
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Tres Seaver wrote:
> Charlie Clark wrote:
>> Am 14.01.2010, 17:12 Uhr, schrieb Hanno Schlichting :
>
>>> I meant to upload a new egg for that myself, but got into problems
>>> with my new build box and pywin32. I
2 egg: you are going to get "latest" packages instead of the
ones tracked by the KGS if you just 'easy_install Zope2'.
Tres.
- --
===
Tres Seaver +1 540-429-0999 tsea...@palladion.com
Palladion Software "
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Fabio Tranchitella wrote:
> Hello,
>
> * 2010-01-13 01:41, Tres Seaver wrote:
>> The 3.7.0 version breaks Zope 2.12, which still expects to be able to
>> import QueueProcessorThread from the old location. I worked around t
made only on the Python Package
Index server, aka "PyPI" or "the Cheeseshop."
Tres.
- --
===
Tres Seaver +1 540-429-0999 tsea...@palladion.com
Palladion Software "Excellence by Design"http://palladion.com
-BEGIN
ProcessorThread from the old location. I worked around the
problem for the moment by pinning 'zope.sendmail<3.7.0', but it seems to
me that the BBB import should be kept (likely forever).
Tres.
- --
===
Tres Seaver
was trying really hard back in 1996. ;)
> but so long as the exception is actually called NotModified, it
> works. Setting it explicitly doesn't, since it gets overridden.
You can "lock" the status and body of the response, which causes
subsequent attempts to set them to fail silent
m_self is None:
> -im_self, args = args[0], args[1:]
> +im_self = im_self
> else:
> im_self = aq_base(self.im_self)
> if IAcquirer.providedBy(im_self):
That can't be right: the if clause is a no-op. And
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Tres Seaver wrote:
> Maurits van Rees wrote:
>> Log message for revision 107689:
>> Fixed possible TypeError while sending multipart emails.
>
>> Changed:
>> U Zope/branches/2.12/doc/CHANGES.rst
>> U Zope
st.py
> U Zope/branches/2.12/src/Products/MailHost/tests/testMailHost.py
Is this fix already on the trunk?
Tres.
- --
=======
Tres Seaver +1 540-429-0999 tsea...@palladion.com
Palladion Software "Exc
e watchman on the battlements: seeing
something break in its daily summary mail is usually the first warning I
have that a checkin broke something. I would be glad to see other
configurations sending their test results to that list, so that
everybody gets notified about breakage.
Tres.
-
zope.exceptions only make sense if you are checking the exception
> type importing its interface from the zope.exceptions package, and thus
> depending on it, I see no risk in such a change.
>
> Thoughts? Comments?
+1. I wouldn't have thought zope.security useful elsewhere, b
oolkit. I never said that I wouldn't listen to
feedback from consumers of zopeapp who discovered a problem introduced
by a change in the ZTK. In fact, I have said repeatedly that I want
real users report such problems, and would gladly help those developers
deal with them. What I don&
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Martijn Faassen wrote:
> Hey Tres,
>
>
> Tres Seaver wrote:
>
>> You're kidding, right?
> [snip]
>> My self-interest? Not really: you are appealing to my altruism, in the
>> fact that I care about the *br
think we have a buildbot for it.
>
> http://dev.thehealthagency.com/buildbot/waterfall
>
> But I do see that Python 2.4 has a failed test, so we do need to fix that.
Which job? There are a bunch of red ones, as well as a bunch of
offlines. A waterfall which doesn't stay
any part of framework code by itself. All the framework
> code will be in "zope" and "zope.app" namespaces.
I like it! I only wish we'd thought of it eight years ago, when we
first started hacking on the thing we mistakenly called "Zope 3".
Tres.
- --
s (e.g., Baiju's BlueBream takes off, or
if another Z3-based app ports to using it), that will make supporting
zopeapp's needs a reasonable request, simliar to supporting Plone via
Zope2. Until people organize such a community of interest around the
zopeapp set (or some other grouping), we don
Five/browser/resource.py
> +
> +
>Zope 2.10.10 (2009/12/22)
No fix for this issue has landed yet on the 2.10 branch.
Tres.
- --
===
Tres Seaver +1 540-429-0999 tsea...@palladion.com
Palladion Software
branches/2.11/lib/python/Products/Five/browser/resource.py
What, no test? How do you know you got the speling right? And why use
'request.environ.get()' instead of the original OFS.Image spelling,
'request.get_header()'?
Tres.
- --
===
ly timeline that's needed is the order of the commits.
>
> If there's anyone who wants to maintain the new bastard-stepchild,
> they're free to step forward. There's no obligation on the part of
> the ZTK maintainers to do that, nor should there be.
>
> That'
ing to this group, and will likely only
be maintained by this group.
- - Potential future users of the zope.app packages? Removing them from
the ZTK is actually beneficial to those users, because it signals
their relatively narrow focus and usefulness, as well as removing any
implied pr
(nonsensical) BBB for nameless
users, I would be in favor of just copying Hanno's version of the ZTK
config into the Zope2 tree and have Zope2 ignore the ZTK per-se.
Tres.
- --
===
Tres Seaver +1 540-429-0999 tsea...@palladion.com
Palladion Software "Excellence by
that at all.
You seem to be worried that the removed packages will bitrot because
they aren't part of the ZTK: going forward, that may in fact be so, but
*only if they aren't being used by people who also track the ZTK*, in
which case their removal has harmed no one.
Tres.
- --
==
ason for you not to do that. But it should separate from
> the ZTK.
+1.
Tres.
- --
===
Tres Seaver +1 540-429-0999 tsea...@palladion.com
Palladion Software "Excellence by Design"http://palladion.com
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (GNU/Li
ges
>> to a top-level namespace package. I mean something similar to:
>> "zope.app.*", "grokcore.*", "repoze.bfg.*" ?
>
> One more example: "plone.app.""
No, it would not be useful. The BBB damage would be catastrophic.
Tres.
going to add the zope.app.* packages back to the
> ZTK until we've had a proper discussion about how, as a Zope community,
> we go forward with this. Delegating this responsibility *separately* to
> sub projects is just plain silly.
You are treading on very dangerous ground h
adication in Zope2, as well.
CMF is nearly zope.app free (one remaining testing dependency).
Tres.
- --
===
Tres Seaver +1 540-429-0999 tsea...@palladion.com
Palladion Software "Excellence by Design"htt
" crew to keep using it, while not taxing the
mainstream (and the core developers) to support them. Given that 2.13
is unlikely to be out before Q3 of 2010, how hard is it going to be for
folks to catch up, anyway? Plone 4 will ship on top of 2.12, Plone 5 is
already a more radical
DTML). Or just put it in
a module / package in the Zope2 distribution's 'src' directory.
While we're at it, the circular import between ZServer and ZPublisher is
insane, too.
Tres.
- --
===
Tres Seaver +1 54
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hanno Schlichting wrote:
> On Sun, Dec 27, 2009 at 6:55 AM, Tres Seaver wrote:
>> Hanno Schlichting wrote:
>>> Log message for revision 107134:
>>> Moved zope.formlib / zope.app.form integration into a separate packa
o.
Tres.
- --
=======
Tres Seaver +1 540-429-0999 tsea...@palladion.com
Palladion Software "Excellence by Design"http://palladion.com
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://
e more useful if there is one canonical
>> implementation that "everyone" can depend on - if different consumers
>> of the ZTK end up inventing their own approach to this use case, that
>> will likely detract from cross-framework reuse
>
> Sure. It should be
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Martin Aspeli wrote:
> Tres Seaver wrote:
>
>> After a question on the repoze list about running Zope 2.12.x behind a
>> WSGI server, I went to try that out. I came up with a minimal .wsgi
>> file to run behind mod_wsgi::
l stack" behavior (error handling,
transaction / retry integration) to middleware. The guts of this
can be lifted from repoze.zope2.z2bob. Document using this lighter-
weight publisher.
Tres.
- --
===
Tres Seaver
me
day. As a side deficit, using the C proxy totally wrecks ano chance of
using the package on non CPython.
Tres.
- --
=======
Tres Seaver +1 540-429-0999 tsea...@palladion.com
Palladion Software "Excellence by
.org/pypi/zLOG
Network burp?
Tres.
- --
===
Tres Seaver +1 540-429-0999 tsea...@palladion.com
Palladion Software "Excellence by Design"http://palladion.com
-BEGIN PGP SIGNATURE-
Version: GnuP
data so that you can correlate with the
traced requests.
Tres.
- --
=======
Tres Seaver +1 540-429-0999 tsea...@palladion.com
Palladion Software "Excellence by Design"http://palladion.com
-BEGIN PGP S
Corporation and contributors, not adding
on a new one: they have transferred all those copyrights to the
foundations. We also want to leave the dates alone (dates should only
change when separately-copyrightable changes are made to the module).
Tres.
- --
======
e by far:
> "you probably want to plug in a real implementation here." Then if
> there is a need for the proposed default implementation, it can be
> provided as a plugin by some other package, right?
The same argument applies in your case: you could plug in your own
wrapper
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Martijn Faassen wrote:
> Hey,
>
> Tres Seaver wrote:
> [let's not suddenly change the behavior of __call__ for backwards
> compatibility reasons]
>
>> If so, that code is already broken: it depends on an undocumented
&
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Thomas Lotze wrote:
> Martijn Faassen wrote:
>
>> Hey,
>>
>> Tres Seaver wrote:
>> [snip]
>>> Any code today which wants a utility is calling 'getUtilty' (if it
>>> *knows* the utility must b
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Martijn Faassen wrote:
> Tres Seaver wrote:
>> -BEGIN PGP SIGNED MESSAGE-
>> Hash: SHA1
>>
>> Martin Aspeli wrote:
>>> Tres Seaver wrote:
>>>
>>>> In either case, I think TypeError (or
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Martin Aspeli wrote:
> Tres Seaver wrote:
>
>> In either case, I think TypeError (or maybe LookupError) is the *right*
>> choice: we don't want to "hide" zope.component's API functions and then
>
he
packages we make can be installed on all supported platforms.
Tres.
- --
===
Tres Seaver +1 540-429-0999 tsea...@palladion.com
Palladion Software "Excellence by Design"http://palladion.com
-BEGIN PGP SIGNATURE-
Version: GnuPG
body else, the distinction is meaningless.
Tres.
- --
=======
Tres Seaver +1 540-429-0999 tsea...@palladion.com
Palladion Software "Excellence by Design"http://palladion.com
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (GNU/Linux)
Com
ng
>> that is sneaking from zope.component into zope.component.
>
> Let's deprecate 'alternate' and introduce 'default' then. Might actually
> make the deprecation more easy..
Note that Interface.__call__ is not documented at all as an API::
$ grep __call
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Martin Aspeli wrote:
> Tres Seaver wrote:
>> Martin Aspeli wrote:
>>> zope.component raises TypeError if you can't adapt. It raises
>>> ComponentLookupError it can't find a utility.
>> Not so: see $Z
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Martin Aspeli wrote:
> Tres Seaver wrote:
>
>>>> * The hook invokes the `query*` functions to play nice with any other
>>>>component hooks and the interface methods raise a TypeError if all of
>>>> th
> ClientForm = 0.2.10
> +distribute = 0.6.10
> docutils = 0.5
> infrae.subversion = 1.4.5
> Jinja2 = 2.1.1
I'm not so sure that we want to push distribute into the ZTK
dependencies: can you explain that more clearly?
Tres.
- --
====
int of view.
>>
>> What do people think of this?
>
> I'm +1 on this general approach. Implementation in zope.component, and
> inject it into zope.interface during import time.
Not at import time, please: better to have this happen during startup
(e.g., just before bootstrappi
ally contemplated replacing the current adapter hook with a
more generic hook: the __call__ of interface would delegate to this hook
for its semantics.
Given that the choice to use __call__ is not widely enough accepted, I
think something like your solution makes sense. I'm not sure th
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Tres Seaver wrote:
> Tres Seaver wrote:
>> There used to be a section in the "Advanced Zope Scripting" chapter
>> which documented using External Methods: why is it gone now?
>
> Looks like Hanno did this in r9656
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Tres Seaver wrote:
> There used to be a section in the "Advanced Zope Scripting" chapter
> which documented using External Methods: why is it gone now?
Looks like Hanno did this in r96569, 2009-02-15. I'm planning to revert
the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
There used to be a section in the "Advanced Zope Scripting" chapter
which documented using External Methods: why is it gone now?
Tres.
- --
===
Tres Seaver +1 54
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Martin Aspeli wrote:
> On 13/12/09 16:49, Martin Aspeli wrote:
>> On 13/12/09 10:52, Tres Seaver wrote:
>>
>>> Doesn't smell like a regression to me: the code there hasn't changed in
>>> a good long while.
17, in __call__
>Module Products.PageTemplates.Expressions, line 127, in _eval
>Module zope.tales.expressions, line 124, in _eval
>Module Products.PageTemplates.Expressions, line 76, in
> boboAwareZopeTraverse
>Module OFS.Traversable, line 312, in restrictedTrav
or 12 or 18 months
> later. :)
>
> Cc:ing zope-dev for opinions.
+1 in general to the idea: we should be able to put together a
"buildcompat"-style buildout which would be autoamatable under buildbot.
Tres.
- --
=========
7 beta is out now, so it's pretty urgent.
Its an alpha, not a beta. http://www.python.org/download/releases/2.7/
says: "Python 2.7 alpha 1 was released on December 5th, 2009."
Tres.
- --
===
Tres Seaver
Has somebody been doing nasty stuff like removing releases on PyPI?
Tres.
- --
===
Tres Seaver +1 540-429-0999 tsea...@palladion.com
Palladion Software "Excellence by Design"http://palladion.com
-BEGIN PGP SIG
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Ross Patterson wrote:
> Tres Seaver writes:
>
>> Are you using try:...finally:... inside your testcase methods? If so,
>> why not just move the cleanup invocation into your 'tearDown' for the
>> testcase class:
for the
testcase class: at that point, the '-D' option to the testrunner will
stop you at the error, with the tearDown not yet called.
Or are you doing this in doctests? If so, move the code you are testing
into a real testing framework. ;)
Tres.
- --
=
instance
> somewhere so that I can use it from any module in my zope product.
I disagree on the need to use a global: you should just be able to call
'logging.getLogger("yourapp")' and use the instance which comes back.
Tres.
- --
object: if it implements (rather than provides) the interface, then
call it, otherwise just return it. Folks who use factories which don't
declare what they implement would need to adjust if we adopt this approach.
Tres.
- --
===
Tres Seave
red
as utilities from ZCML / imperative code: even that term is inaccurate
once persistent objects get registered.
[1] See the description of the Singleton pattern in the
mother-of-all-wikis: http://www.c2.com/cgi/wiki?SingletonPattern
Tres.
- --
==
701 - 800 of 1808 matches
Mail list logo
