From holger at merlinux.de Fri Apr 6 19:32:16 2007 From: holger at merlinux.de (holger krekel) Date: Fri, 6 Apr 2007 19:32:16 +0200 Subject: [py-dev] py.test and twisted In-Reply-To: <932f8baf0702200120k2d55fc58kd23afd3f6ae4d36c@mail.gmail.com> References: <932f8baf0702200120k2d55fc58kd23afd3f6ae4d36c@mail.gmail.com> Message-ID: <20070406173216.GI18225@solar.trillke> Hi Ralf, sorry for missing out on answering. On Tue, Feb 20, 2007 at 10:20 +0100, Ralf Schmitt wrote: > Hi all, > > I've made py.test work with the twisted framework using greenlets to switch > between twisted's mainloop and py.test's "mainloop". (see attached file). > It currently uses monkeypatching to change py.test.Item's execute function. > Currently missing is the ability to return twisted deferreds from setup and > teardown methods. > I could monkeypatch py.test even more, but I'd rather have a method to hook > into py.test, and intercept any calls to user supplied functions (i.e. > teardown, setup, and test methods). Any chance to get such changes > integrated into py.test? I'd be willing to write them on my own and would > also be glad to have the py.test.twisted script be included into py.test. yes, let's consider how to integrate twisted support - however, from my side not much before May - i still need to recover from the recent PyPy release and report rushs ... best, holger From faassen at startifact.com Fri Apr 13 19:21:34 2007 From: faassen at startifact.com (Martijn Faassen) Date: Fri, 13 Apr 2007 19:21:34 +0200 Subject: [py-dev] unwedging the cheeseshop for py In-Reply-To: References: Message-ID: Martijn Faassen wrote: [snip] > I think Holger might be a good person to contact them, as luckily he's > listed as the author, so there's a good chance he'll be believed. > > I'd be nice if we could figure out who this 'rocky' person is... Any progress on this? Should I contact the cheeseshop myself? Holger, what's your cheeseshop username? Regards, Martijn From holger at merlinux.de Fri Apr 13 20:11:23 2007 From: holger at merlinux.de (holger krekel) Date: Fri, 13 Apr 2007 20:11:23 +0200 Subject: [py-dev] unwedging the cheeseshop for py In-Reply-To: References: Message-ID: <20070413181123.GM18225@solar.trillke> On Fri, Apr 13, 2007 at 19:21 +0200, Martijn Faassen wrote: > Martijn Faassen wrote: > [snip] > > I think Holger might be a good person to contact them, as luckily he's > > listed as the author, so there's a good chance he'll be believed. > > > > I'd be nice if we could figure out who this 'rocky' person is... > > Any progress on this? Should I contact the cheeseshop myself? Holger, > what's your cheeseshop username? no progress yet - if you can get py lib to be owned by "hpk at trillke.net" that would help (i just verified i can login). I'd prefer it to have multiple people be able to modify things - do you know if that is possible? thanks for caring, holger From ianb at colorstudy.com Fri Apr 13 20:14:51 2007 From: ianb at colorstudy.com (Ian Bicking) Date: Fri, 13 Apr 2007 13:14:51 -0500 Subject: [py-dev] unwedging the cheeseshop for py In-Reply-To: <20070413181123.GM18225@solar.trillke> References: <20070413181123.GM18225@solar.trillke> Message-ID: <461FC89B.8000609@colorstudy.com> holger krekel wrote: > On Fri, Apr 13, 2007 at 19:21 +0200, Martijn Faassen wrote: >> Martijn Faassen wrote: >> [snip] >>> I think Holger might be a good person to contact them, as luckily he's >>> listed as the author, so there's a good chance he'll be believed. >>> >>> I'd be nice if we could figure out who this 'rocky' person is... >> Any progress on this? Should I contact the cheeseshop myself? Holger, >> what's your cheeseshop username? > > no progress yet - if you can get py lib to be owned by "hpk at trillke.net" > that would help (i just verified i can login). I'd prefer it to have > multiple people be able to modify things - do you know if that is possible? Yes, once you login you can set up multiple owners or maintainers. You can also email catalog-sig or Richard Jones to fix a user/permission problem. -- Ian Bicking | ianb at colorstudy.com | http://blog.ianbicking.org | Write code, do good | http://topp.openplans.org/careers From holger at merlinux.de Sun Apr 15 20:48:31 2007 From: holger at merlinux.de (holger krekel) Date: Sun, 15 Apr 2007 20:48:31 +0200 Subject: [py-dev] unwedging the cheeseshop for py In-Reply-To: <461FC89B.8000609@colorstudy.com> References: <20070413181123.GM18225@solar.trillke> <461FC89B.8000609@colorstudy.com> Message-ID: <20070415184831.GA25045@solar.trillke> Hi Ian, On Fri, Apr 13, 2007 at 13:14 -0500, Ian Bicking wrote: > holger krekel wrote: > >On Fri, Apr 13, 2007 at 19:21 +0200, Martijn Faassen wrote: > >>Martijn Faassen wrote: > >>[snip] > >>>I think Holger might be a good person to contact them, as luckily he's > >>>listed as the author, so there's a good chance he'll be believed. > >>> > >>>I'd be nice if we could figure out who this 'rocky' person is... > >>Any progress on this? Should I contact the cheeseshop myself? Holger, > >>what's your cheeseshop username? > > > >no progress yet - if you can get py lib to be owned by "hpk at trillke.net" > >that would help (i just verified i can login). I'd prefer it to have > >multiple people be able to modify things - do you know if that is > >possible? > > Yes, once you login you can set up multiple owners or maintainers. You > can also email catalog-sig or Richard Jones to fix a user/permission > problem. thanks, did that and am now the maintainer ... didn't do anything yet with it. If anyone has an account and wants to co-maintain, please drop me a note, so i can add you (would be good to have more than one person having access there, i think). holger From holger at merlinux.de Fri Apr 20 07:46:20 2007 From: holger at merlinux.de (holger krekel) Date: Fri, 20 Apr 2007 07:46:20 +0200 Subject: [py-dev] [xoraxax@codespeak.net: [py-svn] r42188 - py/trunk/py/test] Message-ID: <20070420054620.GE25045@solar.trillke> Hi Alexander, (cc py-dev), if you want to revive this, then please also the test - and it's better to copy the old revision (svn cp can do that, i think) then to re-add it and loose all history. I am not sure, i am in favour of re-adding this, though. do you actually use it? holger ----- Forwarded message from xoraxax at codespeak.net ----- From: xoraxax at codespeak.net To: py-svn at codespeak.net Date: Fri, 20 Apr 2007 00:39:27 +0200 (CEST) Subject: [py-svn] r42188 - py/trunk/py/test X-Spambayes-Classification: ham; 0.00 Author: xoraxax Date: Fri Apr 20 00:39:27 2007 New Revision: 42188 Added: py/trunk/py/test/compat.py Log: Revive test/compat.py again, seems to work fine for me. Can be used by patching sys.modules["unittest"] in the conftest.py file. Added: py/trunk/py/test/compat.py ============================================================================== --- (empty file) +++ py/trunk/py/test/compat.py Fri Apr 20 00:39:27 2007 @@ -0,0 +1,59 @@ +import py +from py.__.test.outcome import Failed, Passed + + +class TestCaseUnit(py.test.collect.Function): + """ compatibility Unit executor for TestCase methods + honouring setUp and tearDown semantics. + """ + def execute(self, session): + boundmethod = self.obj + instance = boundmethod.im_self + instance.setUp() + try: + boundmethod() + finally: + instance.tearDown() + return Passed() + +class TestCase(object): + """compatibility class of unittest's TestCase. """ + Function = TestCaseUnit + + def setUp(self): + pass + + def tearDown(self): + pass + + def fail(self, msg=None): + """ fail immediate with given message. """ + raise Failed(msg=msg) + + def assertRaises(self, excclass, func, *args, **kwargs): + py.test.raises(excclass, func, *args, **kwargs) + failUnlessRaises = assertRaises + + # dynamically construct (redundant) methods + aliasmap = [ + ('x', 'not x', 'assert_, failUnless'), + ('x', 'x', 'failIf'), + ('x,y', 'x!=y', 'failUnlessEqual,assertEqual, assertEquals'), + ('x,y', 'x==y', 'failIfEqual,assertNotEqual, assertNotEquals'), + ] + items = [] + for sig, expr, names in aliasmap: + names = map(str.strip, names.split(',')) + sigsubst = expr.replace('y', '%s').replace('x', '%s') + for name in names: + items.append(""" + def %(name)s(self, %(sig)s, msg=""): + __tracebackhide__ = True + if %(expr)s: + raise Failed(msg=msg + (%(sigsubst)r %% (%(sig)s))) + """ % locals() ) + + source = "".join(items) + exec py.code.Source(source).compile() + +__all__ = ['TestCase'] _______________________________________________ py-svn mailing list py-svn at codespeak.net http://codespeak.net/mailman/listinfo/py-svn ----- End forwarded message ----- -- merlinux GmbH Steinbergstr. 42 31139 Hildesheim http://merlinux.de tel +49 5121 20800 75 (fax 77) From mailinglist at alexanderweb.de Fri Apr 20 18:28:36 2007 From: mailinglist at alexanderweb.de (Alexander Schremmer) Date: Fri, 20 Apr 2007 18:28:36 +0200 Subject: [py-dev] [xoraxax@codespeak.net: [py-svn] r42188 - py/trunk/py/test] In-Reply-To: <20070420054620.GE25045@solar.trillke> References: <20070420054620.GE25045@solar.trillke> Message-ID: <1177086516.29463.1.camel@tuxpaddy> Hi Holger, Am Freitag, den 20.04.2007, 07:46 +0200 schrieb holger krekel: > if you want to revive this, then please also the test - and it's > better to copy the old revision (svn cp can do that, i think) > then to re-add it and loose all history. Yes, I thought about that as well (too late, though :-)). > I am not sure, i am in favour of re-adding this, though. > do you actually use it? Yes, I am using it to run MoinMoin's legacy tests using py.test. I will try to find the test ... Kind regards, Alexander From holger at merlinux.de Fri Apr 20 18:39:56 2007 From: holger at merlinux.de (holger krekel) Date: Fri, 20 Apr 2007 18:39:56 +0200 Subject: [py-dev] [xoraxax@codespeak.net: [py-svn] r42188 - py/trunk/py/test] In-Reply-To: <1177086516.29463.1.camel@tuxpaddy> References: <20070420054620.GE25045@solar.trillke> <1177086516.29463.1.camel@tuxpaddy> Message-ID: <20070420163956.GM25045@solar.trillke> Hi Alexander, On Fri, Apr 20, 2007 at 18:28 +0200, Alexander Schremmer wrote: > Hi Holger, > > Am Freitag, den 20.04.2007, 07:46 +0200 schrieb holger krekel: > > > if you want to revive this, then please also the test - and it's > > better to copy the old revision (svn cp can do that, i think) > > then to re-add it and loose all history. > > Yes, I thought about that as well (too late, though :-)). no, it's not too late, just remove and do a proper copy :) otoh, if you are to "svn blame" for it all, that's not bad, either :) > > I am not sure, i am in favour of re-adding this, though. > > do you actually use it? > > Yes, I am using it to run MoinMoin's legacy tests using py.test. interesting that this works well enough. ok then - let's leave it in for now. I am just scared that people may want to have even more legacy support, i guess. Also it's not documented/advertised at all. > I will try to find the test ... it should be in py/test/testing/test_compat.py - maybe just check the "svn log -v" for when it got removed. best & thanks, holger From schmir at gmail.com Fri May 4 11:16:11 2007 From: schmir at gmail.com (Ralf Schmitt) Date: Fri, 4 May 2007 11:16:11 +0200 Subject: [py-dev] py.test and twisted In-Reply-To: <20070406173216.GI18225@solar.trillke> References: <932f8baf0702200120k2d55fc58kd23afd3f6ae4d36c@mail.gmail.com> <20070406173216.GI18225@solar.trillke> Message-ID: <932f8baf0705040216l60c8c8dbnf2315fc816adbb77@mail.gmail.com> On 4/6/07, holger krekel wrote: > > Hi Ralf, > > sorry for missing out on answering. no problem. On Tue, Feb 20, 2007 at 10:20 +0100, Ralf Schmitt wrote: > > Hi all, > > > > I've made py.test work with the twisted framework using greenlets to > switch > > between twisted's mainloop and py.test's "mainloop". (see attached > file). > > It currently uses monkeypatching to change py.test.Item's execute > function. > > Currently missing is the ability to return twisted deferreds from setup > and > > teardown methods. > > I could monkeypatch py.test even more, but I'd rather have a method to > hook > > into py.test, and intercept any calls to user supplied functions (i.e. > > teardown, setup, and test methods). Any chance to get such changes > > integrated into py.test? I'd be willing to write them on my own and > would > > also be glad to have the py.test.twisted script be included into py.test > . > > yes, let's consider how to integrate twisted support - however, > from my side not much before May - i still need to recover > from the recent PyPy release and report rushs ... Hope you recovered. Do you have time to discuss twisted support now? Regards, - Ralf -------------- next part -------------- An HTML attachment was scrubbed... URL: http://codespeak.net/pipermail/py-dev/attachments/20070504/49a48269/attachment.htm From holger at merlinux.de Fri May 4 12:25:37 2007 From: holger at merlinux.de (holger krekel) Date: Fri, 4 May 2007 12:25:37 +0200 Subject: [py-dev] py.test and twisted In-Reply-To: <932f8baf0705040216l60c8c8dbnf2315fc816adbb77@mail.gmail.com> References: <932f8baf0702200120k2d55fc58kd23afd3f6ae4d36c@mail.gmail.com> <20070406173216.GI18225@solar.trillke> <932f8baf0705040216l60c8c8dbnf2315fc816adbb77@mail.gmail.com> Message-ID: <20070504102537.GN25045@solar.trillke> On Fri, May 04, 2007 at 11:16 +0200, Ralf Schmitt wrote: > On 4/6/07, holger krekel wrote: > >> > >> I've made py.test work with the twisted framework using greenlets to > >switch > >> between twisted's mainloop and py.test's "mainloop". (see attached > >file). > >> It currently uses monkeypatching to change py.test.Item's execute > >function. > >> Currently missing is the ability to return twisted deferreds from setup > >and > >> teardown methods. > >> I could monkeypatch py.test even more, but I'd rather have a method to > >hook > >> into py.test, and intercept any calls to user supplied functions (i.e. > >> teardown, setup, and test methods). Any chance to get such changes > >> integrated into py.test? I'd be willing to write them on my own and > >would > >> also be glad to have the py.test.twisted script be included into py.test > > Hope you recovered. Do you have time to discuss twisted support now? rather sometime from mid may, i am afraid. thanks for your answer, holger From holger at merlinux.de Mon May 28 12:05:24 2007 From: holger at merlinux.de (holger krekel) Date: Mon, 28 May 2007 12:05:24 +0200 Subject: [py-dev] CFP 5th June for CC Camp [camp-orga@events.ccc.de: FINAL Call for Papers: Chaos Communication Camp 2007] Message-ID: <20070528100524.GB25045@solar.trillke> Hello all, below is an invitation and CFP for the Chaos Computer Camp in August 2007 around Berlin. (extended) deadline for proposals is 5th June. Maybe I submit a py.execnet/higher level networking talk ("building a flexible and fast platform for computer viruses" or so) and co-submit a "PyPy" one - question being: do some of us maybe want to meet up there and sprint a bit? Seems one is giving talks in airport hangars, btw, ... best, holger ----- Forwarded message from camp-orga at events.ccc.de ----- Date: Wed, 23 May 2007 22:38:53 +0200 From: camp-orga at events.ccc.de To: hpk at trillke.net Subject: FINAL Call for Papers: Chaos Communication Camp 2007 X-Spambayes-Classification: ham; 0.00 [snip personalized prae-ambel] FINAL Call for Papers: Chaos Communication Camp 2007, Berlin Chaos Communication Camp 2007 "In Fairy Dust We Trust!" August, 8th to 12th, 2007 Airport Museum Finowfurt (Finow Airport) near Berlin, Germany http://events.ccc.de/camp/2007/ Final Call for Paper Deadline: June 5th 2007, 23:59 CET =Overview= The Chaos Communication Camp is an international, five-day open-air event for hackers, builders, and makers organized by the Chaos Computer Club (CCC). The camp provides a relaxed atmosphere for free exchange of technical, social and political ideas. Discuss, sunbathe, and enjoy camping with some of the most interesting people you might ever meet. And all that with internet, power, an abundance of weird self-made gadgets, and people willing to explain them to you, right next to your tent. The Camp area is themed as a starship launch site and split into various thematic villages organized by participating groups from all over the world. Have a look at the incredible new location, right next to an old Russian military airfield (we'll launch drones and UFOs - no kidding!). All this together with vintage MiG fighter planes the Soviet airforce left there when they left East Germany and helicopters, oh my! Two huge main hangars (room for 400 people each) will feature conference tracks with lectures and presentations, while workshops will take place in a central workshop area and in the various villages. To get a first glimpse of what to expect have a look at our self-organizing participants at the Camp Wiki: http://events.ccc.de/camp/2007/Villages. Furthermore there will be a hangar for not-so-lonely hacking nights and days together with hundreds of others, and a hangar featuring art and beauty created with or without a computer. Of course there will also be a lounge with nice electronic music, German beer, great food, and a choice of caffeinated hacker drinks. The conference languages are English and German. Don't worry about language issues though - the Camp is a truly international event! Everyone will be happy to communicate with you in the languages of the Internet - broken English and 1337speak. =Topics= In general, lectures and workshops dealing with technology, ethics, science, security, art, philosophy, politics, culture and cooking are welcome. The main theme of this year's camp is the world we want to live in tomorrow. Any cool tech, research, ideas, and presentations interesting to our audience, are interesting to us. And even beyond the presentations, the camp lives from participation, so bring those gadgets, Go boards, webapps, p2p-simulators, knitted hardware protectors, drones, and lockpicking sets, and expect people to come to you wanting to learn more. =Travel= For this year's Camp there's a special travel opportunity. The Hacker Foundation (http://hackerfoundation.org) has put together a package of nothing less than legendary proportions. For US$1337 (roundtrip from the US and Canada) or ???1337 (roundtrip from Europe) you get admission to both the Camp and the Defcon hacker conference in Las Vegas just a few days before the Camp, a flight from Defcon to Frankfurt (Germany) and from there directly to Finow Airfield on a specially chartered "Hackers on a Plane" flight. This offer includes optional accomodation at the Camp. See for yourself: http://www.hackersonaplane.info/ For general travel Information see http://events.ccc.de/camp/2007/Getting_there =Lecture Requirements= Lectures are expected to be highly relevant in practice or better be darn funny. Sales droids and PR-people have been known to disappear without traces on past events. Interactive workshops are welcome. Hands-on anything are even more welcome. Final presentations for talks should be up to 60 minutes, for workshops up to 60 or 120 minutes long. Additionally, a question-and-answer period will be provided. Follow-up discussions and hands-on workshops are strongly encouraged, there will be space for such activities available outside the main lecture shelters (if you don't prefer a nice sit-in on the grass in the sun). Audio and video recordings of the lectures will be published online in various formats. All material will be available under a Creative Commons licence allowing free non-commercial redistribution of the material as long as the original credit to authors and publishers is retained. =Submissions= All proposals MUST be submitted online using our lecture submission system at https://pentabarf.cccv.de/submission/Camp+2007 . Please follow the instructions given there. You can provide papers and slides for the digital conference pack upon submission. Please make sure your submission contains all information we need to review your talk and send us everything in one go. If you have any questions regarding your submission, feel free to contact us at camp-content at cccv.de but do NOT submit your lecture via e-mail. Accepted speakers are asked to hand in slides used in their talks. Please use a well-known format for your slides. =Dates and deadlines= We've already finished our first CFP. We offer a scheduled second deadline till June, 5th. Submissions received before June 5th, 23:59 CET, will be allocated to remaining slots. Notification of acceptance will be sent by June, 27th, or earlier. Early submissions will be treated with higher priority. ----- End forwarded message ----- -- merlinux GmbH Steinbergstr. 42 31139 Hildesheim http://merlinux.de tel +49 5121 20800 75 (fax 77)