Mailman 3 May 2005 - pypy-dev

coming to the Goteborg sprint
by Eric van Riet Paap 19 May '05

19 May '05

Hello all, I have booked my flight to Goteborg to attend my first sprint, I arrive on the 30th of june and depart on the 8th of july. So I would like to introduce myself in this email. My background is in the games industry. Instead of writing a nice story here, I will refrain myself to a list in chronological order. - BBS for C64 - Chess, checkers, Awari programs, mostly for dedicated (8 bit cpu) hardware. - Playstation one game called Dodgem Arena - Various webgames - Virtual reality software writting in C++ with OpenGL for graphics and Python for interaction in the 3d worlds - Custom-made CMS written in Python for Financial Times newspaper subscriptions - Fulltime dad for last 6 months best regards, Eric van Riet Paap Utrecht The Netherlands

2 1

Sprint (talks) movies
by Eric van Riet Paap 19 May '05

19 May '05

Hello, Are any off the talks about PyPy recorded? I seem to remember they were, but I can't find any reference of that. I would very much like to view them. If there are no objections, I would also like to host them on my server and create a torrent for them. best regards Eric van Riet Paap

2 1

Re: [pypy-svn] r12421 - in pypy/dist: . Pyrex pypy/module/builtin
by Ben.Young＠risk.sungard.com 19 May '05

19 May '05

Hi, You can remove me from the list. I only did a bit of fiddling a few months ago! In case this is needed: I hereby grant the pypy developers all copyright to any work I have done on the pypy source code. Cheers, Ben pypy-svn-bounces(a)codespeak.net wrote on 17/05/2005 21:32:38: > Author: hpk > Date: Tue May 17 22:32:38 2005 > New Revision: 12421 > > Added: > pypy/dist/LICENSE > pypy/dist/Pyrex/LICENSE > Modified: > pypy/dist/pypy/module/builtin/app_help.py > Log: > issue52 testing > > Added a first draft for a top-level LICENSE files, where the copyrights > got computed by examining all committers (via svn log) on the pypy and > py directories. The list is currently ordered by number of commits. > If desired i could extend the script and let it try to run "svn blame". > It probably would give a somewhat more appropriate picture. > > Additionally i put a pseudo-LICENSE into the Pyrex directory > (it was the only notice i could find from the Pyrex author). > > So the questions are (apart from the minor ordering issue): > > - do we want to reduce the list of PyPy copyright holders > somehow? > > - are there any no included sub-projects that miss copyright > statements or a LICENSE file? > > > > Added: pypy/dist/LICENSE > ============================================================================== > --- (empty file) > +++ pypy/dist/LICENSE Tue May 17 22:32:38 2005 > @@ -0,0 +1,96 @@ > +License for files in the pypy and py directory > +============================================== > + > +Except when otherwise stated (look for LICENSE files in directories or > +information at the beginning of each file) all software and > +documentation in the 'pypy' and 'py' directories is licensed as follows: > + > + The MIT License > + > + Permission is hereby granted, free of charge, to any person > + obtaining a copy of this software and associated documentation > + files (the "Software"), to deal in the Software without > + restriction, including without limitation the rights to use, > + copy, modify, merge, publish, distribute, sublicense, and/or > + sell copies of the Software, and to permit persons to whom the > + Software is furnished to do so, subject to the following conditions: > + > + The above copyright notice and this permission notice shall be included > + in all copies or substantial portions of the Software. > + > + THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS > + OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF > MERCHANTABILITY, > + FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL > + THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, > DAMAGES OR OTHER > + LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING > + FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER > + DEALINGS IN THE SOFTWARE. > + > + > +PyPy Copyright holders 2003-2005 > +==================================================== > + > +Except when otherwise stated (look for LICENSE files or information at > +the beginning of each file) the files in the 'pypy' directory are each > +copyrighted by one or more of the following people and organizations: > + > + Armin Rigo <arigo(a)tunes.org> > + Samuele Pedroni <pedronis(a)strakt.com> > + Holger Krekel <hpk(a)trillke.net> > + Michael Hudson <mwh(a)python.net> > + Christian Tismer <tismer(a)tismer.com> > + Seo Sanghyeon <sanxiyn(a)gmail.com> > + Alex Martelli <aleaxit(a)yahoo.com> > + Stefan Schwarzer <sschwarzer(a)sschwarzer.de> > + Patrick Maupin <pmaupin(a)speakeasy.net> > + Carl Friedrich Bolz <cfbolz(a)gmx.de> > + Bob Ippolito <bob(a)redivi.com> > + Anders Chrigstrom <ac(a)strakt.com> > + Jacob Hallen <jacob(a)strakt.com> > + Marius Gedminas <mgedmin(a)b4net.lt> > + Laura Creighton <lac(a)strakt.com> > + Guido Van Rossum <guido(a)python.org> > + Richard Emslie <rxe(a)ukshells.co.uk> > + Ludovic Aubry <ludovic.aubry(a)logilab.fr> > + Adrien Di Mascio <adim(a)logilab.fr> > + Stephan Diehl <> > + Dinu Gherman <gherman(a)darwin.in-berlin.de> > + Guenter Jantzen <Guenter.Jantzen(a)t-mobile.de> > + Anders Lehmann <serendipity-soft(a)get2net.dk> > + Rocco Moretti <roccomoretti(a)hotpop.com> > + Olivier Dormond <olivier.dormond(a)gmail.com> > + Brian Dorsey <briandorsey(a)gmail.com> > + Jonathan David Riehl <jriehl(a)spaceship.com> > + Andreas Friedge <andreas(a)trillke.net> > + Jens-Uwe Mager <jum(a)anubis.han.de> > + Alan McIntyre <alan.mcintyre(a)esrgtech.com> > + Lutz Paelike <lutz_p(a)gmx.net> > + Jacek Generowicz <jacek.generowicz(a)cern.ch> > + Ben Young <ben(a)transversal.com> > + Michael Chermside <mcherm(a)mcherm.com> > + > + Heinrich-Heine University, Germany > + AB Strakt, Sweden > + merlinux GmbH, Germany > + tismerysoft GmbH, Germany > + Logilab Paris, France > + DFKI GmbH, Germany > + > + > +py lib Copyright holders, 2003-2005 > +========================================== > + > +Except when otherwise stated (look for LICENSE files or information at > +the beginning of each file) the files in the 'py' directory are > +copyrighted by one or more of the following people and organizations: > + > + Holger Krekel <hpk(a)trillke.net> > + merlinux GmbH, Germany <office(a)merlinux.de> > + Armin Rigo <arigo(a)tunes.org> > + Jan Balster <jan(a)balster.info> > + > +Contributors include:: > + > + Ian Bicking <ianb(a)colorstudy.com> > + Grig Gheorghiu <grig(a)gheorghiu.net> > + Bob Ippolito <bob(a)redivi.com> > > Added: pypy/dist/Pyrex/LICENSE > ============================================================================== > --- (empty file) > +++ pypy/dist/Pyrex/LICENSE Tue May 17 22:32:38 2005 > @@ -0,0 +1,13 @@ > +Copyright stuff: Pyrex is free of restrictions. You > +may use, redistribute, modify and distribute modified > +versions. > + > +The latest version of Pyrex can be found here: > + > +http://www.cosc.canterbury.ac.nz/~greg/python/Pyrex/ > + > +Greg Ewing, Computer Science Dept, +--------------------------------------+ > +University of Canterbury, | A citizen of NewZealandCorp, a | > +Christchurch, New Zealand | wholly-owned subsidiary of USA Inc. | > +greg(a)cosc.canterbury.ac.nz > + > > Modified: pypy/dist/pypy/module/builtin/app_help.py > ============================================================================== > --- pypy/dist/pypy/module/builtin/app_help.py (original) > +++ pypy/dist/pypy/module/builtin/app_help.py Tue May 17 22:32:38 2005 > @@ -17,7 +17,7 @@ > def license(): > print \ > """ > -Copyright (c) <2003-2004> <Pypy development team> > +Copyright (c) <2003-2005> <Pypy development team> > > Permission is hereby granted, free of charge, to any person > obtaining a copy of this software and associated documentation files > (the "Software"), to deal in the Software without restriction, > including without limitation the rights to use, copy, modify, merge, > publish, distribute, sublicense, and/or sell copies of the Software, > and to permit persons to whom the Software is furnished to do so, > subject to the following conditions: > > _______________________________________________ > pypy-svn mailing list > pypy-svn(a)codespeak.net > http://codespeak.net/mailman/listinfo/pypy-svn >

3 2

llvm install documenation
by Eric van Riet Paap 19 May '05

19 May '05

Hi, In the getting_started docs it is mentioned where llvm can found. It does not mention what version of llvm to use. Version 1.5 came out yesterday. With the eminent PyPy 0.6 I think it would be good if everyone uses llvm 1.5 so we can better reproduce any errors. - Eric

1 0

Remove your .pyc files :-)
by Armin Rigo 18 May '05

18 May '05

Hi, Warning, the current changes tend to break already-checked-out working copies because of .pyc files staying behind. If you get import errors, deleting all the .pyc files! (You might want to delete the directory pypy/_cache also, as it might grow over time and be only very occasionally purged automatically.) Armin

1 0

Re: [pypy-dev] Re: [pypy-svn] r12394 - pypy/dist/pypy/documentation
by Laura Creighton 17 May '05

17 May '05

In a message of Tue, 17 May 2005 15:23:54 +0200, Carl Friedrich Bolz writes: >> Instead of just removing it, can you make it into its own page and >> give a link to it. > >I did exactly that. See >http://codespeak.net/pypy/index.cgi?doc/svn-help.html > >Carl Friedrich Thanks very much. Laura

1 0

PyPy issue tracker
by Laura Creighton 17 May '05

17 May '05

When I went to https://codespeak.net/issue/pypy-dev/ and searched for issue 66 expecting the mail that holger just sent, I instead got a 404 not found. It's looking for Message: /pypy-dev/issue66 not https://codespeak.net/issue/pypy-eu/issue66 is this correct? Laura

4 4

Re: [pypy-svn] r12394 - pypy/dist/pypy/documentation
by Laura Creighton 17 May '05

17 May '05

In a message of Tue, 17 May 2005 00:34:26 +0200, hpk(a)codespeak.net writes: >Author: hpk >Date: Tue May 17 00:34:26 2005 >New Revision: 12394 > >Modified: > pypy/dist/pypy/documentation/getting_started.txt >Log: >issue37 in-progress > >introduced the 0.6 release and according explanations into the getting >started document. Basically i try to make downloading/unpacking the >upcoming 0.6 release an alternative to using an 'svn co' line. >Also i tried to avoid all the duplicate information we have everywhere. > >Somehow i don't like the very detailed subversion steps anymore. People >who don't have subversion are likely to just use the tar/zip files and >the others could be pointed to some official subversion documentation. >So I think we should further refactor the getting started document >accordingly and remove subversion details. This part of the documentation >stems from a time where almost nobody had subversion installed except us >:-) Instead of just removing it, can you make it into its own page and give a link to it. The problem is that our documentation on how to install subversion is _better_ than the one at the subversion site (unless that has changed recently). Every time I go someplace that doesn't have subversion, I go to their site, try their instructions, have it _fail_, remember, oh, yes, that's right and then go back to your instructions on how to get subversion which works. I can see the point of simplifying, but if other people have as much trouble as I do installing subversion from sourcen on a site that doesn't have a package manager, they may need our instructions. Laura

2 1

Re: [pypy-svn] r12320 - pypy/dist/pypy/documentation
by Christian Tismer 15 May '05

15 May '05

hpk(a)codespeak.net wrote: > Author: hpk > Date: Sun May 15 19:57:58 2005 > New Revision: 12320 > > Modified: > pypy/dist/pypy/documentation/getting_started.txt > Log: > i am unsure what to do about things > such as t.view() which start a full gui. > > commenting t.view() out for now > to stop the tests opening pygame-windows Oops! > >>> t = Translator(test.is_perfect_number) > - >>> t.view() > + >>> #t.view() You mean for testing the embedded example? Well, but without the t.view(), the rest of the text makes no sense, too. Maybe we should put a flag somewhere else that certain things should be deactivated, at least in some batch testing we would not want any interactivity I guess. ciao - chris -- Christian Tismer :^) <mailto:tismer@stackless.com> tismerysoft GmbH : Have a break! Take a ride on Python's Johannes-Niemeyer-Weg 9A : *Starship* http://starship.python.net/ 14109 Berlin : PGP key -> http://wwwkeys.pgp.net/ work +49 30 802 86 56 mobile +49 173 24 18 776 fax +49 30 80 90 57 05 PGP 0x57F3BF04 9064 F4E1 D754 C2FF 1619 305B C09C 5A3B 57F3 BF04 whom do you want to sponsor today? http://www.stackless.com/

1 0

polishing / pypy-dev tracker
by hpk＠trillke.net 15 May '05

15 May '05

Hi pypy-dev, two notes: - Is everybody who is interested aware that we want to meet at 11am tomorrow (sunday, 15th May) for the PyPy release-polishing session? - i am finalizing & testing the new PyPy development tracker and am interested in comments and people trying it out a bit. It's currently located here: https://codespeak.net/issue/pypy-dev/ almost all people that ever commited to the PyPy code base should be able to use their normal codespeak login (svn/shell/pypy-eu/pypy-dev logins are all unified for PyPy). One of the new tracker features is that it's connected to svn checkins (based on Richard Jones's new integration code). If you commit to svn/pypy/dist with a a log message like: issue40 resolved This fixes a long standing issues blablabla then this message will show up in the tracker, get send to subscribers and will mark the issue as resolved. Another feature is that each user can edit a field 'notify on new issues' in his 'Details' and will then receive notification email on each newly created issue in that tracker (even if you are not on the nosy list). I am still randomly re-initializing the tracker database for testing purposes. I'll send a public note when the new tracker goes into production. Comments already welcome, though. cheers & see you, holger

5 5