Re: [Zope-dev] Re: getting RestrictedPython working on Python 2.5
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., 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 ___ Zope-Dev maillist - Zope-Dev@zope.org 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 )
Re: [Zope-dev] Re: getting RestrictedPython working on Python 2.5
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! ___ Zope-Dev maillist - Zope-Dev@zope.org 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 )
Re: [Zope-dev] Re: getting RestrictedPython working on Python 2.5
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 ___ Zope-Dev maillist - Zope-Dev@zope.org 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 )
Re: [Zope-dev] Re: getting RestrictedPython working on Python 2.5
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 ___ Zope-Dev maillist - Zope-Dev@zope.org 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 )
Re: [Zope-dev] Re: getting RestrictedPython working on Python 2.5
- 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 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. May be we can add it to top-level README.txt of all packages. Regards, Baiju M ___ Zope-Dev maillist - Zope-Dev@zope.org 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 )
