From tom_harris at aapl.com.au Fri Feb 10 02:09:47 2006 From: tom_harris at aapl.com.au (Tom Harris) Date: Fri, 10 Feb 2006 12:09:47 +1100 Subject: [py-dev] Is this a bug? Message-ID: <8C34B0527434E8419698286070B9A471040BD7@aaplcdex4.aapl.com.au> I found the following whilst testing a class with py.test with a broken __repr__. If I call py.test with the --showlocals flag it attempts to print the locals in a failing test function. If one of these locals has a broken __repr__ (in my case it was the tested class itself, no surprise there), then the test script exits with a broken traceback due to the repr_locals() function in py.test.terminal.TerminalSession class. The call to repr should (IMHO) catch any exception from repr and generate a default repr, say . Does this need fixing? Now I know about it, it's not really a problem but it would have confused me a bit if I hadn't just written the broken repr. I'll submit a patch with a test if you like. BTW, py.test is much cooler than unittest. Tom Harris - The contents of this email, and any attachments, are strictly private and confidential. - It may contain legally privileged or sensitive information and is intended solely for the individual or entity to which it is addressed. - Only the intended recipient may review, reproduce, retransmit, disclose, disseminate or otherwise use or take action in reliance upon the information contained in this email and any attachments, with the permission of Australian Arrow Pty. Ltd. - If you have received this communication in error, please reply to the sender immediately and promptly delete the email and attachments, together with any copies, from all computers. - It is your responsibility to scan this communication and any attached files for computer viruses and other defects and we recommend that it be subjected to your virus checking procedures prior to use. - Australian Arrow Pty. Ltd. does not accept liability for any loss or damage of any nature, howsoever caused, which may result directly or indirectly from this communication or any attached files. -------------- next part -------------- An HTML attachment was scrubbed... URL: From jan at balster.info Fri Feb 10 12:15:31 2006 From: jan at balster.info (Jan Balster) Date: Fri, 10 Feb 2006 12:15:31 +0100 Subject: [py-dev] Is this a bug? In-Reply-To: <8C34B0527434E8419698286070B9A471040BD7@aaplcdex4.aapl.com.au> References: <8C34B0527434E8419698286070B9A471040BD7@aaplcdex4.aapl.com.au> Message-ID: <43EC75D3.7030208@balster.info> Hi Tom, thank you for the report. I think, it needs fixing. Tom Harris wrote: > I'll submit a patch with a test if you like. Would be great! > BTW, py.test is much cooler than unittest. :-) Cheers, Jan From hpk at trillke.net Fri Feb 10 15:23:45 2006 From: hpk at trillke.net (holger krekel) Date: Fri, 10 Feb 2006 15:23:45 +0100 Subject: [py-dev] py lib / py.test sprint at pycon Message-ID: <20060210142345.GD23817@solar.trillke> Hi folks, We plan to do a py lib / py.test sprint as a track on the pypy sprint after PyCon 2006 from 27th February till 2nd March, current ideas are: * integrating doctests (finally!) * better test selection support * adding profiling * improving and refining reporting with py.test * discuss/refine py.test's architecture * whatever we come up with until then Apart from me, Jan Balster also Brian Dorsey will participate in the sprint. Would be great to have some more people showing up and moving py.test to the next steps! Please send a note to me if you want to come or follow the instructions further below. cheers, holger Post-PyCon PyPy Sprint: February 27th - March 2nd 2006 ============================================================ The next PyPy sprint is scheduled to take place right after PyCon 2006 in Dallas, Texas, USA. We hope to see lots of newcomers at this sprint, so we'll give friendly introductions. Note that during the Pycon conference we are giving PyPy talks which serve well as preparation. Goals and topics of the sprint ------------------------------ While attendees of the sprint are of course welcome to work on what they wish, we offer these ideas: - Work on an 'rctypes' module aiming at letting us use a ctypes implementation of an extension module from the compiled pypy-c. - Writing ctypes implementations of modules to be used by the above tool. - Experimenting with different garbage collection strategies. - Implementing Python 2.5 features in PyPy - Implementation of constraints solvers and integration of dataflow variables to PyPy. - Implement new features and improve the 'py' lib and py.test which are heavily used by PyPy (doctests/test selection/...). - Generally experiment with PyPy -- for example, play with transparent distribution of objects or coroutines and stackless features at application level. - Have fun! Location -------- The sprint will be held wherever the PyCon sprints end up being held, which is to say somewhere within the Dallas/Addison Marriott Quorum hotel. For more information see the PyCon 06 sprint pages: - http://us.pycon.org/TX2006/Sprinting - http://wiki.python.org/moin/PyCon2006/Sprints Exact times ----------- The PyPy sprint will from from Monday February 27th until Thursday March 2nd 2006. Hours will be from 10:00 until people have had enough. Registration, etc. ------------------ If you know before the conference that you definitely want to attend our sprint, please subscribe to the `PyPy sprint mailing list`_, introduce yourself and post a note that you want to come. Feel free to ask any questions or make suggestions there! There is a separate `PyCon 06 people`_ page tracking who is already planning to come. If you have commit rights on codespeak then you can modify yourself a checkout of http://codespeak.net/svn/pypy/extradoc/sprintinfo/pycon06/people.txt .. _`PyPy sprint mailing list`: http://codespeak.net/mailman/listinfo/pypy-sprint .. _`PyCon 06 people`: http://codespeak.net/pypy/extradoc/sprintinfo/pycon06/people.txt From mkc at mathdogs.com Tue Feb 28 20:25:11 2006 From: mkc at mathdogs.com (Mike Coleman) Date: Tue, 28 Feb 2006 13:25:11 -0600 (CST) Subject: [py-dev] execnet suggestion Message-ID: <15380.204.56.6.101.1141154711.squirrel@mail.panix.com> Hi, Execnet looks really cool. At first glance, though, having to put the code in a string seems kind of clunky. I'm wondering whether it wouldn't be possible to just define functions in the normal way and then export them. I'm not exactly sure how this would work, but it seems like there's some access to the bytecode via introspection, or something like that. Mike