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 started work. Since eggification, I'm not sure what to do... What I was planning on doing was creating a branch of RestrictedPython, checking that out and then manually checking out any dependencies from svn. Is there a "better" way to do this with easy_install or some such? cheers, Chris -- Simplistix - Content Management, Zope & Python Consulting - http://www.simplistix.co.uk
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 it out and then started work.
Since eggification, I'm not sure what to do... What I was planning on doing was creating a branch of RestrictedPython, checking that out and then manually checking out any dependencies from svn. Is there a "better" way to do this with easy_install or some such?
$ 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) Note that this procedure is the canonical one for all packages maintained in svn.zope.org nowadays.
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 changing? Are any dependencies brought out as svn checkouts or just got as stable releases?
Note that this procedure is the canonical one for all packages maintained in svn.zope.org nowadays.
OK, is there a non-buildout equivalent? cheers, Chris -- Simplistix - Content Management, Zope & Python Consulting - http://www.simplistix.co.uk
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 the code that I'd be changing?
Uh, you checked it out (first line: svn co).
Are any dependencies brought out as svn checkouts or just got as stable releases?
Dependencies will be downloaded from PyPI (or any other index you specify) as eggs.
Note that this procedure is the canonical one for all packages maintained in svn.zope.org nowadays.
OK, is there a non-buildout equivalent?
There's python setup.py develop, which will also install the checked out thing as a development egg, but it will try and install the dependencies in the site-packages of the 'python' you used to call it with. This usually means isntalling things globally (unless you use virtualenv). Also, you don't get a test runner this easily (though we should probably make python setup.py test work at some point, it currently doesn't work). The neat thign about the buildout way is that - it's an absolute no-brainer - it's completely self-contained (nothing is installed outside that one directory, unless you explicitly allow that).
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 of weird places ;-)
Dependencies will be downloaded from PyPI (or any other index you specify) as eggs.
Cool.
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?
Also, you don't get a test runner this easily (though we should probably make python setup.py test work at some point, it currently doesn't work).
I might be interested in making that happen ;-) What still needs to be done? I'm imagining just plumbing the 'test' action through to running the zope.testing testrunner, or is there more to it than that?
The neat thign about the buildout way is that
- it's an absolute no-brainer
If you know what magic to incant ;-)
- it's completely self-contained (nothing is installed outside that one directory, unless you explicitly allow that).
This *is* a good thing :-) cheers, Chris -- Simplistix - Content Management, Zope & Python Consulting - http://www.simplistix.co.uk
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 know :).
Also, you don't get a test runner this easily (though we should probably make python setup.py test work at some point, it currently doesn't work).
I might be interested in making that happen ;-)
Cool.
What still needs to be done? I'm imagining just plumbing the 'test' action through to running the zope.testing testrunner, or is there more to it than that?
No idea. You'll presumably have to deal with the tests_require thing as well.
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 that every single sandbox can be set up like this. I deploy all my sites like this now, be it Grok, Zope 3 or even Plone: checkout the project from SVN and enter the two command - done!
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 that every single sandbox can be set up like this. I deploy all my sites like this now, be it Grok, Zope 3 or even Plone: checkout the project from SVN and enter the two command - done!
Maybe we should have a default GETTING-STARTED.txt that goes along with bootstrap.py. -- Benji York Senior Software Engineer Zope Corporation
----- "Benji York" <benji@zope.com> 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 and bin/buildout. Not
very hard. The advantage is that every single sandbox can be set up
done!
like this. I deploy all my sites like this now, be it Grok, Zope 3 or even Plone: checkout the project from SVN and enter the two command
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. Regards, Baiju M
Baiju M wrote:
----- "Benji York" <benji@zope.com> 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., just have one file that is used everywhere, no editing or making sure the content stays up to date (other than updating the files wholesale when needed). -- Benji York Senior Software Engineer Zope Corporation
participants (4)
-
Baiju M -
Benji York -
Chris Withers -
Philipp von Weitershausen