Baiju M wrote:
- Benji York [EMAIL PROTECTED] wrote:
Maybe we should have a default GETTING-STARTED.txt that goes along
with
bootstrap.py.
May be we can add it to top-level README.txt of all packages.
The good thing about a single file is that we can treat it like
bootstrap.py. I.e.,
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, checked
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
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
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
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
- 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 python boostrap.py
