[Repoze-dev] [issue138] Running BFG with mod_wsgi and ipython installed
New submission from Jasper Op de Coul jas...@infrae.com: Hi, I'm having trouble running bfg with mod_wsgi in Apache. In paster.py the following code tries to import IPython shell if this is available: try: from IPython.Shell import IPShell # pragma: no cover except ImportError: IPShell = None # pragma: no cover I have ipython installed, but importing fails because sys.stdin is not available in mod_wsgi/apache: File /home/jasper/wip/repub_eur/eggs/repoze.bfg-1.2-py2.6.egg/repoze/bfg/paster.py, line 13, in module from IPython.Shell import IPShell # pragma: no cover File /var/lib/python-support/python2.6/IPython/__init__.py, line 58, in module __import__(name,glob,loc,[]) File /var/lib/python-support/python2.6/IPython/ipstruct.py, line 22, in module from IPython.genutils import list2dict2 File /var/lib/python-support/python2.6/IPython/genutils.py, line 55, in module from IPython.Itpl import Itpl,itpl,printpl File /var/lib/python-support/python2.6/IPython/Itpl.py, line 101, in module itpl_encoding = sys.stdin.encoding or 'ascii' ConfigurationExecutionError: type 'exceptions.IOError': sys.stdin access restricted by mod_wsgi -- messages: 371 nosy: JasperOC priority: bug status: unread title: Running BFG with mod_wsgi and ipython installed __ Repoze Bugs b...@bugs.repoze.org http://bugs.repoze.org/issue138 __ ___ Repoze-dev mailing list Repoze-dev@lists.repoze.org http://lists.repoze.org/listinfo/repoze-dev
[Repoze-dev] [issue138] Running BFG with mod_wsgi and ipython installed
Tres Seaver tsea...@agendaless.com added the comment: Apparently IPython is doing something nasty at import time. I just checked in a change which delayed BFG's import until actually needed, which should prevent the import-time side effect from hurting under mod_wsgi. Please verify and close. -- assignedto: - JasperOC status: unread - chatting __ Repoze Bugs b...@bugs.repoze.org http://bugs.repoze.org/issue138 __ ___ Repoze-dev mailing list Repoze-dev@lists.repoze.org http://lists.repoze.org/listinfo/repoze-dev
Re: [Repoze-dev] Build failed in Hudson: repoze.bfg #17
Chris McDonough wrote: Please bear with us... we need to get a separate list set up for this and bug tracker stuff. Is there any documentation on how you've set this up? - What are you using for test reporting? collective.xmltestreport or something else? - How did you get Cobertura integration going? I've been using z3c.coverage + the NCover plugin, but yours looks nicer. Martin -- Author of `Professional Plone Development`, a book for developers who want to work with Plone. See http://martinaspeli.net/plone-book ___ Repoze-dev mailing list Repoze-dev@lists.repoze.org http://lists.repoze.org/listinfo/repoze-dev
Re: [Repoze-dev] Build failed in Hudson: repoze.bfg #17
On 3/3/10 9:52 PM, Martin Aspeli wrote: Chris McDonough wrote: Please bear with us... we need to get a separate list set up for this and bug tracker stuff. Is there any documentation on how you've set this up? No, sorry. - What are you using for test reporting? collective.xmltestreport or something else? Here's the set of commands that get run to test e.g. repoze.bfg: /opt/Python-2.6.4/bin/virtualenv --no-site-packages r$SVN_REVISION/ r$SVN_REVISION/bin/easy_install nose coverage nosexcover cd repoze.bfg-trunk ../r$SVN_REVISION/bin/python setup.py develop ../r$SVN_REVISION/bin/python setup.py nosetests --with-xunit \ --with-xcoverage - How did you get Cobertura integration going? I've been using z3c.coverage + the NCover plugin, but yours looks nicer. Vis nosexcover and using nose to run the tests (that's the --with-xunit and --with-xcoverage hair), then choosing Publish Cobertura Coverage Report in the configuration. - C ___ Repoze-dev mailing list Repoze-dev@lists.repoze.org http://lists.repoze.org/listinfo/repoze-dev
Re: [Repoze-dev] Build failed in Hudson: repoze.bfg #17
Chris McDonough wrote: Here's the set of commands that get run to test e.g. repoze.bfg: /opt/Python-2.6.4/bin/virtualenv --no-site-packages r$SVN_REVISION/ r$SVN_REVISION/bin/easy_install nose coverage nosexcover No sex cover, ey? That sounds like an STD risk. cd repoze.bfg-trunk ../r$SVN_REVISION/bin/python setup.py develop ../r$SVN_REVISION/bin/python setup.py nosetests --with-xunit \ --with-xcoverage Cool. I guess there's a standard there somewhere that both Cobertura and nose adheres to. I wonder how hard it is to run Zope/Plone tests through nose in this way. I'm guessing quite. - How did you get Cobertura integration going? I've been using z3c.coverage + the NCover plugin, but yours looks nicer. Vis nosexcover and using nose to run the tests (that's the --with-xunit and --with-xcoverage hair), then choosing Publish Cobertura Coverage Report in the configuration. Yeah, makes sense. Martin -- Author of `Professional Plone Development`, a book for developers who want to work with Plone. See http://martinaspeli.net/plone-book ___ Repoze-dev mailing list Repoze-dev@lists.repoze.org http://lists.repoze.org/listinfo/repoze-dev
Re: [Repoze-dev] Build failed in Hudson: repoze.bfg #17
On 3/3/10 10:46 PM, Martin Aspeli wrote: Chris McDonough wrote: Here's the set of commands that get run to test e.g. repoze.bfg: /opt/Python-2.6.4/bin/virtualenv --no-site-packages r$SVN_REVISION/ r$SVN_REVISION/bin/easy_install nose coverage nosexcover No sex cover, ey? That sounds like an STD risk. Ha! cd repoze.bfg-trunk ../r$SVN_REVISION/bin/python setup.py develop ../r$SVN_REVISION/bin/python setup.py nosetests --with-xunit \ --with-xcoverage Cool. I guess there's a standard there somewhere that both Cobertura and nose adheres to. I think Ned B. added Cobertura-compat output to coverage.py for just this purpose (and it's exposed via nose by --with-xcoverage). I wonder how hard it is to run Zope/Plone tests through nose in this way. I'm guessing quite. I suspect it would be a project. At one point, though, I made the ZODB tests runnable via setup.py test however (previously they were hardwired to be run via bin/test in a buildout), so it is possible to do. Might be better though to try to convince zope.testing's coverage support to output a coverage.xml file. That's really all that's necessary; I forgot to mention that in the Cobertura xml report pattern box in the Hudson UI, we have **/coverage.xml. - C ___ Repoze-dev mailing list Repoze-dev@lists.repoze.org http://lists.repoze.org/listinfo/repoze-dev
