Mailman 3 July 2006 - pytest-dev

[py-dev] Greenlet module appears to be rebuilt on every import
by Benno Rice July 23, 2006

July 23, 2006

Hi, I'm running into an odd problem trying to use greenlets on Mac OS X 10.4.7 with Python 2.4 built from DarwinPorts and the py lib from subversion as of 23 July 2006. Whenever I try to import greenlets I get the following: Python 2.4.3 (#1, Apr 20 2006, 12:04:55) [GCC 4.0.0 (Apple Computer, Inc. build 5026)] on darwin Type "help", "copyright", "credits" or "license" for more information. >>> from py.magic import greenlet Traceback (most recent call last): File "<stdin>", line 1, in ? File "/opt/local/Library/Frameworks/Python.framework/Versions/2.4/ lib/python2.4/site-packages/py/initpkg.py", line 180, in __getattr__ result = self.__package__._resolve(extpy) File "/opt/local/Library/Frameworks/Python.framework/Versions/2.4/ lib/python2.4/site-packages/py/initpkg.py", line 68, in _resolve implmodule = self._loadimpl(fspath[:-3]) File "/opt/local/Library/Frameworks/Python.framework/Versions/2.4/ lib/python2.4/site-packages/py/initpkg.py", line 98, in _loadimpl return __import__(modpath, None, None, ['__doc__']) File "/opt/local/Library/Frameworks/Python.framework/Versions/2.4/ lib/python2.4/site-packages/py/magic/greenlet.py", line 5, in ? greenlet = path.getpymodule().greenlet File "/opt/local/Library/Frameworks/Python.framework/Versions/2.4/ lib/python2.4/site-packages/py/path/local/local.py", line 404, in getpymodule mod = make_module_from_c(self) File "/opt/local/Library/Frameworks/Python.framework/Versions/2.4/ lib/python2.4/site-packages/py/misc/buildcmodule.py", line 37, in make_module_from_c lib.remove() File "/opt/local/Library/Frameworks/Python.framework/Versions/2.4/ lib/python2.4/site-packages/py/path/local/posix.py", line 111, in remove self._callex(os.remove, self.strpath) File "/opt/local/Library/Frameworks/Python.framework/Versions/2.4/ lib/python2.4/site-packages/py/path/common.py", line 227, in _callex raise cls, value py.error.EACCES: [Permission denied]: remove('/opt/local/Library/ Frameworks/Python.framework/Versions/2.4/lib/python2.4/site-packages/ py/c-extension/greenlet/greenlet.so',) I've checked this out and it looks like something in the import logic wants to compile the greenlet module every time I import it. This leads to two questions: 1) Shouldn't the greenlet module get built when I run the build target of the setup.py script? 2) Isn't this a rather large bug in normal operation since the site- packages directory should be owned by root? Is there a way to have the greenlet module be built once during the build phase of setup.py and then just used statically after that? -- Benno Rice benno(a)jeamland.net http://jeamland.net/

1 0

[py-dev] Import problems
by Maciek Fijalkowski July 14, 2006

July 14, 2006

I want to make py.execnet import remotely. So what I perform: - make new __import__ hook, so we can try local import or ask for sources from server (via some channel), sources are got by py.code.Source() but... There are problems with importing py lib itself. For some modules it tells that there are builtin modules (py modules), because of import hooks. On the other hand copying py.lib is not what I want to achieve. Any clue?

2 1

Re: [py-dev] license
by Bryan Weingarten July 13, 2006

July 13, 2006

hi jan, thanks for replying. actually, we just added subversion (webDAV) capability this week. webDAV uses commands that are extensions to the http protocol which was just added to the firewall proxy. the code is checked in, so it should be available on the engineering firewall whenever they do the next major upgrade. py.test is working out really well for us. I've made it the standard python unittest framework here and it's working well for everyone, nothing but compliments. so thanks for a great product. today I was customizing our embedded version of python that we will eventually deliver with our products, adding and deleting files and packages including py.lib. so unless I remove py.lib for some reason (and my company doesn't go out of business :), py.lib should eventually be installed on 10's of thousands of computers. I plan to attend pycon 2007, so I'll see you again if you make it. bryan -----Original Message----- From: Jan Balster [mailto:jan@balster.info] Sent: Thursday, July 13, 2006 2:20 PM To: Bryan Weingarten Cc: py lib developers Subject: Re: [py-dev] license Hey Bryan! Nice to see you! Still no subversion hole in the firewall? ;) You are finally using it your product? cool :) py.lib is licensed under the MIT license. If the license file is not in the tarball, you can find it in the subversion repository: http://codespeak.net/svn/py/dist/py/LICENSE best, Jan Bryan Weingarten wrote: > I can't seem to find the license for py.lib (py.test) at the web site or > in the py-0.8.0-alpha2 package. My company requires that we maintain a > reference to this before we can use it in our product. So any pointers > to the license would be helpful. > > Thanks, > > bryan > _______________________________________________ > py-dev mailing list > py-dev(a)codespeak.net > http://codespeak.net/mailman/listinfo/py-dev >

1 0

[py-dev] license
by Bryan Weingarten July 13, 2006

July 13, 2006

I can't seem to find the license for py.lib (py.test) at the web site or in the py-0.8.0-alpha2 package. My company requires that we maintain a reference to this before we can use it in our product. So any pointers to the license would be helpful. Thanks, bryan

2 1

[py-dev] Fwd: [py-svn] r29699 - in py/dist/py/test: . testing
by Brian Dorsey July 7, 2006

July 7, 2006

---------- Forwarded message ---------- > From: hpk(a)codespeak.net <hpk(a)codespeak.net> <snip> > Log: > refine recursive and file filters for directories. > follow the documentaiton (thanks to Fijal for pointing > at the documentation inconsistency, i think that > the 'whatever_test.py' convention is not actually used much) Hmm... I use the 'whatever_test.py' format for all of my tests. I admit, that I'm a bit strange, but somehow I like having the test files right next to the module files since I always edit them in pairs. Using the test_whatever.py format, all of the tests get sorted together rather than right next to the files they are actually a test of. But, like I said, I'm a bit strange... I think most people like to keep their tests in a separate directory? Take care, -Brian

2 2

[py-dev] requiring options; handling crashes
by Nicholas Riley July 2, 2006

July 2, 2006

Hi, I am starting a new project and and am attempting to give this test-development development thingy a try, so I am starting to use py.test. So far I'm finding it really natural and easy to understand - especially compared with my short but unhappy experiences with unittest writing tests for the Metakit Python binding. I have a few questions. First, is there a way to enforce options? For some of the tests I am using Psyco, which does not play happily with py.test without --nomagic, so I would like to require this option. I have tried something like this in conftest.py: import py py.test.Config.parse(['--nomagic', '--nocapture', '--exitfirst']) but that doesn't seem to work, and I'm not sure if there is supposed to be a way. Second, some of my tests crash the interpreter, so I'd prefer to test every file individually (it's fine if no more tests run after the crash :). Is there a sensible way to nest py.test invocations such that the results are aggregated? If the above aren't possible at the moment, I would be interested in implementing them; any hints as to a good design or where the code should go would be appreciated. -- Nicholas Riley <njriley(a)uiuc.edu> | <http://www.uiuc.edu/ph/www/njriley>

2 1