Europe late afternoon = EST morning
How would 1700 UTC (GMT) be for most people?
People generally asleep between 12am and 6am.
Therefore the best time is logically 2am or so central Pacific time
(affecting very few)
This is corresponds to 2pm GMT, 9am US EST, etc
Adam
FYI, everyone who's following this: I have hijacked
http://dev.zope.org/Wikis/DevSite/Proposals/InstallationAndConfiguration
for this purpose. :-)
Awesome. Exactly how I'd like the default zope install to be structured.
:-)
Adam
___
Zope-Dev
Hi Martijn,
We're basically just trying to construct traps to try to identify a
smoking gun. The upside is, if it works, we'll be able to fix the bug
very quickly. However, its based on assumptions about the exact nature
of the bug -- so each trap I write essentially is making a hypothesis
I don't think we can do the geographic coverage without making it too
painful. We should split bug days in half; a few hours in the morning
and a few hours in the afternoon.
--Paul
Brian Lloyd wrote:
Hi all -
In an effort to better keep up with the collector, I'd like
to throw out the
You told us that you will be refining Zope 2.6 plan.
ProposedFeatures table contains an Implement links
(object references) entry by Mario Valente. I've created
SoftLink proposal in ProposalsWiki . These works appear
related. We (Mario and me) discussed and decided that
we can
but gotta dive in and make some changes to this menu.
It depends on what type of change you want to make.
This menu does not exist in it's finished form anywhere in the code, but it
it's contents are created each time you view it, and modified depending on
several parameters. So modifying it is
On Fri, 2002-03-15 at 08:19, Martijn Jacobs wrote:
Hello Leo, Matt, Brian,
I'm on it. Will send results when they're available. If anyone wants
to talk to me during the period, I'll be on IRC.
If you need any assistance for anything, I'm at your service
Which channel/server are
Tim Peters reports on comp.lang.python:
[Martin v. Loewis]
The garbage collector runs while having the GIL, so it does not need
to be thread-safe.
There's still a vulnerability here: gc *assumes* the GIL is held when
_PyObject_GC_Malloc gets called, and doesn't verify that the GIL
Christian Theune wrote:
Hmm. Is it possible to implement some option to turn this off?
I just checked in the ability to use HTTP_TRACEBACK_STYLE to control the
appearance of tracebacks in non-debug mode errors:
'' (default): Place it in an HTML comment
'none': Omit it
'plain': Include it as
