On Wednesday 05 December 2007, Stephan Richter wrote:
> On Unix-like systems, we can use `os.fork()`. The advantage of this
> approach is that I can use OS system calls to kill the process. However,
> ZODB database storages cannot be shared between processes. Nikolay Kim has
> done some preliminary
> On Unix-like systems, we can use `os.fork()`. The advantage of this approach
> is that I can use OS system calls to kill the process. However, ZODB database
> storages cannot be shared between processes. Nikolay Kim has done some
> preliminary experiments and found that `db.open()` locks the
- "Benji York" <[EMAIL PROTECTED]> wrote:
> Philipp von Weitershausen wrote:
> > On 5 Dec 2007, at 15:46 , Chris Withers wrote:
> >>> The neat thign about the buildout way is that
> >>> - it's an absolute no-brainer
> >> If you know what magic to incant ;-)
> >
> > All you have to remember is
Hi everyone,
I have a problem and I am hoping that it has been solved already by someone or
that I will get some input on at least.I apologize for the lengthy E-mail in
advance, but I wanted to provide a detailed discussion as a starting point.
Zope is designed to have very short-lived transact
Philipp von Weitershausen wrote:
On 5 Dec 2007, at 15:46 , Chris Withers wrote:
The neat thign about the buildout way is that
- it's an absolute no-brainer
If you know what magic to incant ;-)
All you have to remember is python boostrap.py and bin/buildout. Not
very hard. The advantage is t
On 5 Dec 2007, at 15:46 , Chris Withers wrote:
There's python setup.py develop, which will also install the
checked out thing as a development egg,
What does that mean? Which python files would I edit to make changes
in this case?
The ones you checked out. This isn't rocket science, you kn
Philipp von Weitershausen wrote:
($z refers to svn+ssh://svn.zope.org/repos/main on my system)
Where does this put the code that I'd be changing?
Uh, you checked it out (first line: svn co).
Sorry, I'm used to things like "python setup.py install" putting all
manner of things in all manner
Summary of messages to the zope-tests list.
Period Tue Dec 4 13:00:00 2007 UTC to Wed Dec 5 13:00:00 2007 UTC.
There were 5 messages: 5 from Zope Unit Tests.
Tests passed OK
---
Subject: OK : Zope-2.7 Python-2.3.6 : Linux
From: Zope Unit Tests
Date: Tue Dec 4 20:54:03 EST 2007
URL
Christian Theune wrote:
> IMHO we should assume whatever is given to us was unpacked by the
> container format and is intended to be a valid MIME type. Meaning we
> should not strip it.
OK, then we agree. Good that I did zc.resourcelibrary 0.8, not 1.0
yesterday ;o)
--
Thomas
___
Am Mittwoch, den 05.12.2007, 11:22 +0100 schrieb Thomas Lotze:
> Christian Theune wrote:
>
> > That depends on the container format and therefore it's the responsibility
> > of the container (e.g. a HTTP header) to remove the whitespace.
> >
> > Note that AFAICT RFC 2045 section 5.1 (that's what
Chris Withers wrote:
Philipp von Weitershausen wrote:
$ svn co $z/RestrictedPython/trunk RestrictedPython (or a branch)
$ cd RestrictedPython
$ /your/development/python bootstrap.py
$ bin/buildout
$ bin/test
($z refers to svn+ssh://svn.zope.org/repos/main on my system)
Where does this put
Philipp von Weitershausen wrote:
$ svn co $z/RestrictedPython/trunk RestrictedPython (or a branch)
$ cd RestrictedPython
$ /your/development/python bootstrap.py
$ bin/buildout
$ bin/test
($z refers to svn+ssh://svn.zope.org/repos/main on my system)
Where does this put the code that I'd be c
Chris Withers wrote:
Hi All,
I'm looking to get RestrictedPython working in Python 2.5.
Has any work been done on this so far?
My first question is about the "right" way to get a checkout that I can
develop in now. In years gone by, I would have created a branch of the
whole of zope 3, checke
Hi All,
I'm looking to get RestrictedPython working in Python 2.5.
Has any work been done on this so far?
My first question is about the "right" way to get a checkout that I can
develop in now. In years gone by, I would have created a branch of the
whole of zope 3, checked it out and then star
Christian Theune wrote:
> That depends on the container format and therefore it's the responsibility
> of the container (e.g. a HTTP header) to remove the whitespace.
>
> Note that AFAICT RFC 2045 section 5.1 (that's what you're referring to
> AFAICT) defines the MIME type specification as done w
Am Mittwoch, den 05.12.2007, 10:20 +0100 schrieb Thomas Lotze:
> Fred Drake wrote:
>
> > On Dec 4, 2007 5:55 PM, Thomas Lotze <[EMAIL PROTECTED]> wrote:
> >> It wasn't even about whitespace around the / but leading whitespace in
> >> front of the major type.
> >
> > Wow. It probably didn't occu
Fred Drake wrote:
> On Dec 4, 2007 5:55 PM, Thomas Lotze <[EMAIL PROTECTED]> wrote:
>> It wasn't even about whitespace around the / but leading whitespace in
>> front of the major type.
>
> Wow. It probably didn't occur to me that would be screwed up.
I've now looked up RfC 2045 which states th
17 matches
Mail list logo