Leonardo Rochael Almeida [EMAIL PROTECTED] writes:
Hi Syver,
Please add this issue to the Collector, including the test (prefereably
without the twisted bits)
Eh, what is the Collector?
___
Zope-Dev maillist - [EMAIL PROTECTED]
Jim Fulton wrote:
I'm working on the cvs to subversion conversion for the ZODB, Zope 2, and
Zope 3 projects. I'm currently doing the conversion of the full history
with
tags and branches. This is taking a long time and creating a huge
repository, which is OK, but, do we really need that much
[Leonardo Rochael Almeida]
Please add this issue to the Collector, including the test
(prefereably without the twisted bits)
[Syver Enstad]
Eh, what is the Collector?
The zope.org Collectors are here:
http://www.zope.org/Collectors/
and you want the Zope Collector:
Kapil Thangavelu wrote:
sigh.. debating over what the book says isn't very productive. my
conclusions at the end of my previous email, namely that what this
layout will accomplish for the zopeorg repository in terms of avoiding
renames of checkouts will likely be fairly limited in pratice, still
[Kapil Thangavelu]
[snip debating over what the book says]
sigh.. debating over what the book says isn't very productive.
That's for sure wink.
my conclusions at the end of my previous email, namely that what this
layout will accomplish for the zopeorg repository in terms of avoiding
Yeah, this is exactely what I would need. Maybe I could ask someone to install
this for me. Mmmhh, ...
Hi Stephan.. I'll look into installing it on zopewiki for experiments.
If someone wants to enable it on zope.org as well I will support.
___
+1
___
Zope-Dev maillist - [EMAIL PROTECTED]
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 )
[Jim Fulton]
The Zope project includes a number of interrelated subprojects,
such as:
- Zope 2
- Zope 3
- ZODB
- ZConfig
Software from the ZODB and ZConfig projects are shared by Zope 2
and Zope 3.
Note that ZODB also depends on ZConfig.
We want this sharing to be very
Tomorrow, as planned. I'm going to move the main development branches for
Zope 2, Zope 3, and ZODB to subversion. I will start the move at 10am
US/Eastern time tomorrow. I plan to be done before 5pm US/Eastern time.
During this time, I ask that no one make checkins to the CVS head for
those
On Tuesday 27 April 2004 14:42, Simon Michael wrote:
Yeah, this is exactely what I would need. Maybe I could ask someone to
install this for me. Mmmhh, ...
Hi Stephan.. I'll look into installing it on zopewiki for experiments.
If someone wants to enable it on zope.org as well I will
greetings,
I read somewhere that each zope thread acquires the global python
interpreter lock before processing a request and until it releases it
the other zope threads are essentially locked out. Does that mean zope
threads are eventually serialized and there are no benefits to be gained
here's the patch I'd have attached to
http://zope.org/Collectors/Zope/1217
if the collector could collect
--
Jamie Heilman http://audible.transient.net/~jamie/
Paranoia is a disease unto itself, and may I add, the person standing
next to you may not be who they appear to be,
On Tue, 2004-04-27 at 10:27, Martijn Faassen wrote:
Kapil Thangavelu wrote:
sigh.. debating over what the book says isn't very productive. my
conclusions at the end of my previous email, namely that what this
layout will accomplish for the zopeorg repository in terms of avoiding
Jim Fulton wrote:
Tomorrow, as planned. I'm going to move the main development branches for
Zope 2, Zope 3, and ZODB to subversion. I will start the move at 10am
US/Eastern time tomorrow. I plan to be done before 5pm US/Eastern time.
During this time, I ask that no one make checkins to the CVS
[Jamie Heilman]
here's the patch I'd have attached to
http://zope.org/Collectors/Zope/1217
if the collector could collect
FYI, I attached the patch to the collector report (nothing magical -- it
just worked for me).
___
Zope-Dev maillist - [EMAIL
greetings,
I read somewhere that each zope thread acquires the global python
interpreter lock before processing a request and until it releases it
the other zope threads are essentially locked out. Does that mean zope
threads are eventually serialized and there are no benefits to be gained
greetings,
I read somewhere that each zope thread acquires the global python
interpreter lock before processing a request and until it releases it
the other zope threads are essentially locked out. Does that mean zope
threads are eventually serialized and there are no benefits to be gained
[sathya]
I read somewhere that each zope thread acquires the global python
interpreter lock before processing a request and until it releases it
the other zope threads are essentially locked out.
The Python GIL (global interpreter lock) affects all code written in Python:
only one thread at a
Tim Peters wrote:
tim thanks much for the explanation. some points below.
[sathya]
I read somewhere that each zope thread acquires the global python
interpreter lock before processing a request and until it releases it
the other zope threads are essentially locked out.
[tim]
No. The GIL
[Jim Fulton]
...
You will be able to do read-only anonymous checkouts like so:
svn co svn://svn.zope.org/repos/main/project/trunk
For example:
svn co svn://svn.zope.org/repos/main/ZConfig/trunk
FYI, I tried that on Windows (XP), and it worked fine.
One glitch, which may be all over
On Wed, 2004-04-28 at 03:41, sathya wrote:
[sathya]
great ! If I understand correctly, if we had a zope process running on
an smp linux machine and doing lots of RDBMS calls we would not be
limited by the GIL. In essence threads running on multiple cpus would
probably not have to wait on
21 matches
Mail list logo
