Mailman 3 February 2011 - pypy-dev

Re: [pypy-dev] implementing the additional repo migrations
by Laura Creighton 26 Feb '11

26 Feb '11

In a message of Sat, 26 Feb 2011 10:25:45 +0100, Jacob Hallén writes: <snip> >While I am fine with dropping older revisions of just about everything in >extradoc, I wonder if it wouldn't be better better for the future to keep >this repository in svn format. That way you will only get one copy of >everything when cloning the repository. > >Jacob I'm not fine with the dropping of older revisions. One of the chief benefits for me of moving to a version control system was that I could feel comfortable ruthlessly condensing my writing, knowing that if I ever wanted this stuff later -- say to use in a different document, I could always go back and get the old revision that contained the wonderful words or diagrams I now propose to cut. And this has happened in the past, where early versions of things I wrote ended up raised out of the grave of the repository to live on as part of completely different documents. I'm not going to be comfortable deleting stuff this if I think that the grim reaper is out there, just waiting to purge all my earlier attempts once some document is deemed to be 'final'. So I either won't delete stuff, or I will go back to my old practice of having dozens of versions around 'just in case'. I'm fine with continuing to have the extradoc managed by svn, though I really want a script that runs nightly looking for things in extradoc that have a mimetype of binary and complains about this. Laura

2 1

Re: [pypy-dev] implementing the additional repo migrations
by Laura Creighton 26 Feb '11

26 Feb '11

In a message of Fri, 25 Feb 2011 22:36:16 +0100, Ronny Pfannschmidt writes: >hi, > >this night i started taking a look at the extra repos that need to be >migrated. > >many of them contain reconstructible, but large pdf files, that i'd like >to kill off for saving space. Why should we ever care about space? >this shouldn't be a problem as long as the svn that many people link to >stays available read-only, but it would need a bit of a plan if that >goes as well. > >im currently investigating what parts of extradoc are reconstructible I don't think that much (or maybe any) reconstruction is necessary. The things in extradoc really are the tex files, pdfs and what-have-you that you would expect from their filename extensions. The problem is that codespeak improperly serves them up as binary files. So no reconstruction needed. Just serve them properly. Laura <snip> >regards Ronny

4 3

further pypy repo migrations
by holger krekel 24 Feb '11

24 Feb '11

hi all, i'd like to continue consolidation of PyPy repositories (and more generally pypy services but that in a separate mail). Thanks to Ronny Pfannschmidt, sponsorship from merlinux (my company), and work from Armin, Anto and others the main PyPy development repository has been migrated to mercurial on Bitbucket. Btw, we just asked and Bitbucket nicely upgraded the PyPy project account to become an unlimited one, thanks! Now we still have some more repositories on codespeak svn. One is "extradoc" which contains a lot of talk, sprint, misc infos and the "pypy.org" website content. We can either move this wholesale to an "extradoc" one on bitbucket or split it maybe into "pypy.org" and "extradoc". Note that the old codespeak.net subversion URLs will remain valid for quite some time so any cleanup/removal of dirs should better happen in the new mercurial repo. Another repo is "pypy-z", maybe not known to most. It is a repository where core project members keep information about more internal bits, like our previous contracts with Google, the European Union and some un-named entities (ask your favourite PSU representative for more info). I suggest we move this to become a "private" mercurial repo on bitbucket. Any more pypy related repositories that need migration or any notes/comments? best holger --

5 9

Writing Mixed Modules for MacOS
by Dan Colish 23 Feb '11

23 Feb '11

I've been working on porting the OSX specific libraries in CPython to PyPy and I'm running into issues. The shape of many fundamental data structures used in the CoreFoundation libraries are not available to me. I was hoping to just fudge it by using a ptr to that structure, but it is not working out as I had hoped. Here is a terribly incorrect sample of what I've been hacking on: http://paste.pocoo.org/show/yENK4gE11yRM9i6p46Ra and here is the corresponding osx documentation: http://goo.gl/i6mYD. I was looking at the approach taken for windows, but it is not clear to me where the fundamental structures for windows lie outside of the win32 specific bits in pypy.rpython.lltypesystem.module.ll_os. For the most part they seem to be defined in the modules where they will be used, so it is difficult for me to understand how it all fits together. In general, a higher level description of how to handle data types which you cannot openly declare would be very helpful. Thanks in advance. -- Dan

3 3

Couple of questions...
by Luke Taylor 23 Feb '11

23 Feb '11

Hi everybody, I'm not a developer but I'm a keen fan of pypy and I have been watching the project for about 6 months now. I'm interested to know.. if there are any plans to make PyPy implement Python 3.x ? Why don't extension modules for Python with bits written in C (eg. SciPy) work with PyPy? Thanks for your time, Luke

3 2

Re: [pypy-dev] further pypy repo migrations
by Laura Creighton 22 Feb '11

22 Feb '11

Holger Krekel is the person to talk with. But he hasn't been around for a few days. I think he is on vacation. Laura

1 0

CfP: ICOOOLPS 2011
by Carl Friedrich Bolz 18 Feb '11

18 Feb '11

Hi all, I think we should consider sending a paper to ICOOOLPS this year again, see call for papers below. Carl Friedrich -- Call For Papers for the sixth annual workshop on Implementation, Compilation, Optimization of Object-Oriented Languages, Programs and Systems (ICOOOLPS) to be held at ECOOP 2011 in Lancaster, UK on July 26th 2011 http://www.icooolps.info/ Overview: Computer programming languages, especially Object-Oriented languages, are pervasive and play a significant role in computer science and engineering life and sometime appear as ubiquitous and completely mature. However, despite a large number of works, there still is a clear need for solutions for efficient implementation and compilation of OO languages in various application domains ranging from embedded and real-time systems to desktop systems. The ICOOOLPS workshop thus aims to address this crucial issue of optimization, mainly but not only in OO languages, programs and systems. It intends to do so by bringing together researchers and practitioners working in the field of implementation and optimization of programming languages. Its main goals are identifying fundamental bases and key current issues pertaining to the efficient implementation, compilation and optimization of OO languages, and outlining future challenges and research directions. An expected output of this workshop is a synthesis identifying fundamental bases and key current issues pertaining to the efficient implementation and compilation of OO languages, in order to spread them further amongst the various computing systems. It is also intended to extend this synthesis to encompass future challenges and research directions in the field of OO languages implementation and optimization, as well as non-OO languages. Important Dates: Workshop paper submission: April 15, 2011 Workshop paper acceptance: May 20, 2011 Workshop: July 26, 2011 Program Committee: Mark van den Brand TU Eindhoven, The Netherlands Peter Dickman Google, Switzerland Roland Ducournau LIRMM, France M. Anton Ertl Technical University of Vienna (TU Wien), Austria Remi Forax University of Marne-la-Vallée, France Björn Franke University of Edinburgh, UK Andreas Gal Mozilla Corporation, USA Kevin Hammond University of St Andrews, UK Tim Harris Microsoft Research, UK Michael Haupt Hasso-Plattner-Institut, Germany Eric Jul (co-chair) DIKU, The University of Copenhagen, Denmark Tomas Kalibera The University of Kent, UK Stein Krogdahl University of Oslo, Norway Francis Chi Moon Lau The University of Hong Kong, Hong Kong Ian Rogers (chair) Azul Systems, USA Jennifer Sartor Ecole Polytechnique Federale de Lausanne, Switzerland Manuel Serrano INRIA, France Mario Wolczko Oracle Labs, USA Olivier Zendra (co-chair) INRIA/LORIA, France

2 1

Re: [pypy-dev] further pypy repo migrations
by Laura Creighton 18 Feb '11

18 Feb '11

In a message of Thu, 17 Feb 2011 15:23:06 +0100, holger krekel writes: >Any more pypy related repositories that need migration >or any notes/comments? > >best >holger I just found a surprising number (at least it surprised me) of references in my own stuff to /svn/user/arigo/hack/<somethings> Laura

2 1

Re: [pypy-dev] European sprints?
by Laura Creighton 16 Feb '11

16 Feb '11

In a message of Tue, 15 Feb 2011 02:57:21 CST, "Stephen Simmons" writes: >Hi... > >I have just started following the PyPy mailing list and am interested in >getting involved in some small way. > >Are there any European sprints planned in the coming few months? > >Thanks >Stephen I want to have one in Göteborg some time after PyCON. That's about as far as this discussion has got so far. Laura

4 5

Separate compilation and friends
by Maciej Fijalkowski 16 Feb '11

16 Feb '11

Hi. There is growing interest about PyPy and especially about extension modules. Apparently there are some people (like Alex) that are willing to write modules in RPython that should not go to the main tree. Since separate compilation is considered hard, how hard would it be to provide separate loading? This would mean you still compile the whole interpreter, but you can load the module from a compiled PyPy that didn't have this option on. Cheers, fijal

6 9