From anto.cuni at gmail.com  Wed Jul  8 17:24:41 2009
From: anto.cuni at gmail.com (Antonio Cuni)
Date: Wed, 08 Jul 2009 17:24:41 +0200
Subject: [pypy-dev] [pypy-svn] r66150 - pypy/trunk/pypy/tool
In-Reply-To: <20090708152215.764C9168562@codespeak.net>
References: <20090708152215.764C9168562@codespeak.net>
Message-ID: <4A54BA39.8020805@gmail.com>

fijal at codespeak.net wrote:

>  try:
> -    BaseException
> +    BaseException = BaseException
>  except NameError:
>      BaseException = Exception

this clearly show that you didn't write a test (or you didn't run it, if it's 
already there).  Could you please try to follow tdd a bit more closely, 
especially on trunk?


From fijall at gmail.com  Wed Jul  8 18:02:11 2009
From: fijall at gmail.com (Maciej Fijalkowski)
Date: Wed, 8 Jul 2009 10:02:11 -0600
Subject: [pypy-dev] [pypy-svn] r66150 - pypy/trunk/pypy/tool
In-Reply-To: <4A54BA39.8020805@gmail.com>
References: <20090708152215.764C9168562@codespeak.net>
	<4A54BA39.8020805@gmail.com>
Message-ID: <693bc9ab0907080902q46e9f165ydf92a6a512ca2e7b@mail.gmail.com>

On Wed, Jul 8, 2009 at 9:24 AM, Antonio Cuni<anto.cuni at gmail.com> wrote:
> fijal at codespeak.net wrote:
>
>> ?try:
>> - ? ?BaseException
>> + ? ?BaseException = BaseException
>> ?except NameError:
>> ? ? BaseException = Exception
>
> this clearly show that you didn't write a test (or you didn't run it, if
> it's already there). ?Could you please try to follow tdd a bit more closely,
> especially on trunk?
>

It's about 2.4 vs 2.5. I have no clue how to test it correctly.


From holger at merlinux.eu  Wed Jul  8 21:15:55 2009
From: holger at merlinux.eu (holger krekel)
Date: Wed, 8 Jul 2009 21:15:55 +0200
Subject: [pypy-dev] [pypy-svn] r66150 - pypy/trunk/pypy/tool
In-Reply-To: <693bc9ab0907080902q46e9f165ydf92a6a512ca2e7b@mail.gmail.com>
References: <20090708152215.764C9168562@codespeak.net>
	<4A54BA39.8020805@gmail.com>
	<693bc9ab0907080902q46e9f165ydf92a6a512ca2e7b@mail.gmail.com>
Message-ID: <20090708191555.GN7437@trillke.net>

On Wed, Jul 08, 2009 at 10:02 -0600, Maciej Fijalkowski wrote:
> On Wed, Jul 8, 2009 at 9:24 AM, Antonio Cuni<anto.cuni at gmail.com> wrote:
> > fijal at codespeak.net wrote:
> >
> >> ?try:
> >> - ? ?BaseException
> >> + ? ?BaseException = BaseException
> >> ?except NameError:
> >> ? ? BaseException = Exception
> >
> > this clearly show that you didn't write a test (or you didn't run it, if
> > it's already there). ?Could you please try to follow tdd a bit more closely,
> > especially on trunk?
> >
> 
> It's about 2.4 vs 2.5. I have no clue how to test it correctly.

there is py.builtin.BaseException which maybe can help. 

holger


From fijall at gmail.com  Wed Jul  8 21:45:53 2009
From: fijall at gmail.com (Maciej Fijalkowski)
Date: Wed, 8 Jul 2009 13:45:53 -0600
Subject: [pypy-dev] [pypy-svn] r66150 - pypy/trunk/pypy/tool
In-Reply-To: <20090708191555.GN7437@trillke.net>
References: <20090708152215.764C9168562@codespeak.net>
	<4A54BA39.8020805@gmail.com>
	<693bc9ab0907080902q46e9f165ydf92a6a512ca2e7b@mail.gmail.com>
	<20090708191555.GN7437@trillke.net>
Message-ID: <693bc9ab0907081245w6bd3c597y7d33774c5a2ecf93@mail.gmail.com>

On Wed, Jul 8, 2009 at 1:15 PM, holger krekel<holger at merlinux.eu> wrote:
> On Wed, Jul 08, 2009 at 10:02 -0600, Maciej Fijalkowski wrote:
>> On Wed, Jul 8, 2009 at 9:24 AM, Antonio Cuni<anto.cuni at gmail.com> wrote:
>> > fijal at codespeak.net wrote:
>> >
>> >> ?try:
>> >> - ? ?BaseException
>> >> + ? ?BaseException = BaseException
>> >> ?except NameError:
>> >> ? ? BaseException = Exception
>> >
>> > this clearly show that you didn't write a test (or you didn't run it, if
>> > it's already there). ?Could you please try to follow tdd a bit more closely,
>> > especially on trunk?
>> >
>>
>> It's about 2.4 vs 2.5. I have no clue how to test it correctly.
>
> there is py.builtin.BaseException which maybe can help.
>
> holger
>

ah cool. I was looking at py.compat and didn't find it. Cool, we can
remove it now :)


From tismer at stackless.com  Fri Jul 10 03:26:17 2009
From: tismer at stackless.com (Christian Tismer)
Date: Fri, 10 Jul 2009 03:26:17 +0200
Subject: [pypy-dev] py.path.svnwc stopped working for me
Message-ID: <4A5698B9.6080804@stackless.com>

def psycofiles():
     path = py.path.svnwc(os.pardir)
     for p in path.visit(lambda x: x.check(versioned=1)):
         if p.check(dir=1):
             print p
         else:
             yield p.relto(path).replace('\\', '/')

stopped working. I don't want to know why.
I'm upset by the fact that it stopped working, even if the
library is not guilty. Yes, I updated SVN.
But it is the library that pretends to be working for me.

and this is the reason why I hate libraries so much:

They pretend to solve a problem, and they do this for a while
(3 years in this case).
But the payload is not worth it, because in the end, the library
stops working. And the replies you will get are of the kind
"well, why did you not update X and Y, and read list Z?"

BECAUSE I HATE LIBRARIES!

Libraries are just another way to subordinate people.

I want a simple, readable piece of source code that I can
understand, when it crashes. Not when I'm recreated and
happy to read lots of twisted code. But right now, in a release
process, when I love nothing more than a trivial SVN script
that crashes, because it thinks it became important some time.

py.lib is one of these crappy things. GO AWAY, you are not helpful.
you are arrogant!

Why I dare to say this?
Code that makes me dependent, for the sake of saving a few lines,
but obfuscating what's going on in a way that I get lost right
before doing a release. That is crap. Holy shit! Arrogant code.
Evict this code till before the invention of computers, please!

I will stop using it, because it always has cost me a
multiple of the time that I would have used without it.
I hate libraries, and even more I hate unreadable libraries.
Have you ever tried to find out why py.lib stops working?

Do you always want to bend your head towards Mekka, thanking
Allah that you did not hit that new bug in the library, today?

Forget it! The only valid answer to arrogant code is
ignoring it. Be arrogant!

don't try to discuss that. I'm not going to be nice
-- 
Christian Tismer             :^)   <mailto:tismer at 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/


From cfbolz at gmx.de  Fri Jul 10 07:08:39 2009
From: cfbolz at gmx.de (Carl Friedrich Bolz)
Date: Fri, 10 Jul 2009 07:08:39 +0200
Subject: [pypy-dev] py.path.svnwc stopped working for me
In-Reply-To: <4A5698B9.6080804@stackless.com>
References: <4A5698B9.6080804@stackless.com>
Message-ID: <4A56CCD7.7080405@gmx.de>

Christian Tismer wrote:
> def psycofiles():
>      path = py.path.svnwc(os.pardir)
>      for p in path.visit(lambda x: x.check(versioned=1)):
>          if p.check(dir=1):
>              print p
>          else:
>              yield p.relto(path).replace('\\', '/')
> 
> stopped working.

1. This is the wrong mailing list to discuss this. use py-dev instead
2. "stopped working" is not exactly a useful error description. what did 
you expect to happen, what happened instead, which py-lib version are 
you using?

> I don't want to know why.

then why are you sending a mail at all?

[vitriolic rant snipped]

Carl Friedrich


From tismer at stackless.com  Fri Jul 10 15:35:42 2009
From: tismer at stackless.com (Christian Tismer)
Date: Fri, 10 Jul 2009 15:35:42 +0200
Subject: [pypy-dev] py.path.svnwc stopped working for me
In-Reply-To: <4A56CCD7.7080405@gmx.de>
References: <4A5698B9.6080804@stackless.com> <4A56CCD7.7080405@gmx.de>
Message-ID: <4A5743AE.8070400@stackless.com>

On 7/10/09 7:08 AM, Carl Friedrich Bolz wrote:
> Christian Tismer wrote:
>> def psycofiles():
>>       path = py.path.svnwc(os.pardir)
>>       for p in path.visit(lambda x: x.check(versioned=1)):
>>           if p.check(dir=1):
>>               print p
>>           else:
>>               yield p.relto(path).replace('\\', '/')
>>
>> stopped working.
>
> 1. This is the wrong mailing list to discuss this. use py-dev instead

Sorry

> 2. "stopped working" is not exactly a useful error description. what did
> you expect to happen, what happened instead, which py-lib version are
> you using?

I thought this is obvious enough.
The visit() crashes suddenly on files which are not versioned.
I upgraded to the latest SVN version, yesterday (by chance, was
forced by Tortoise SVN). Also updated the py-lib trunk yesterday.
The problem is on Windows, when unversioned files exist, like .pyc
files.

Wondering how this can be, and nobody else complained, yet,
or no test has found that.

>> I don't want to know why.
>
> then why are you sending a mail at all?

Well, because I wanted to question the use of libraries in cases
where it would be easy to write a few lines yourself, without
creating those dependencies.
Yes, I was very upset.

-- 
Christian Tismer             :^)   <mailto:tismer at 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/


From tismer at stackless.com  Fri Jul 17 04:49:20 2009
From: tismer at stackless.com (Christian Tismer)
Date: Fri, 17 Jul 2009 04:49:20 +0200
Subject: [pypy-dev] ANN: psyco V2
Message-ID: <4A5FE6B0.8070500@stackless.com>

Announcing Psyco V2 source release
----------------------------------

This is the long awaited announcement of Psyco V2.

Psyco V2 is a continuation of the well-known psyco project,
which was called finished and was dis-continued by its author
Armin Rigo in 2005, in favor of the PyPy project.

This is a new project, using Psyco's code base with permission
of Armin. Questions and complaints should go to me
(tismer at stackless.com) or the mailing list
(psyco-devel at lists.sourceforge.net);
Armin is explicitly not in charge of (t)his project any longer!

As one of the founders and an active member of the PyPy
project, I was very happy to be invited to work on Psyco
V2, by FATTOC, LLC. Psyco V2 tries to extend on the original Psyco
approach "an extension module that just makes Python faster".

Psyco is a just-in-time compiler that accelerates arbitrary
Python code by specialization. We believe that Psyco's approach
can be carried out much further than it was tried so far, when
it's first version was abandoned.

This first V2 release is source-only. There is no web-site, yet,
and there are no binaries for download. These will be available
in a few days on http://www.psyco.org .

For the time being, please stick with subversion access,
building the extension module from source code. The repository
is here:

     http://codespeak.net/svn/psyco/v2/dist

Check-out the repository, and run the setup.py script,
given that you have access to a C compiler.

Psyco V2 will run on X86 based 32 bit Linux, 32 bit Windows,
and Mac OS X. Psyco is not supporting 64 bit, yet. But it
is well being considered.

The current improvements are, shortly:

   - Support for Python 2.4, 2.5 and 2.6
   - a lot of new builtins
   - generators, fast and fully supported.

More information is coming soon on http://www.psyco.org .

This is the beginning of a series of new Psyco versions.
Many more improvements are prepared and about to be published,
soon, starting with the current version 2.0.0 .

Stay tuned, this is just the beginning of psyco's re-birth!

For questions about Psyco V2, please join the mailing list

     psyco-devel at lists.sourceforge.net

or contact me on IRC:

     #psyco on irc.freenode.net .

Psyco V2 is fundamentally supported by FATTOC, LLC.
See http://www.fattoc.com .

Without their continuous support, this work would not have
been possible at all. I wish to express my deepest thanks
to FATTOC, for allowing me to continue on Psyco with all the
energy that this ambitious project needs, and will need.

Further special thanks are going to
Armin Rigo, John Benediktsson, David Salomon, Miki Tebeka,
Raymond Hettinger, Fabrizio Milo, Michael Foord,
Dinu Gherman, Stephan Diehl, Laura Creighton and Andrea Tismer,
for all the support and discussions.

Looking forward to a great future of Psyco!

July 17, 2009
-- 
Christian Tismer             :^)   <mailto:tismer at 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/


From santagada at gmail.com  Mon Jul 20 05:44:32 2009
From: santagada at gmail.com (Leonardo Santagada)
Date: Mon, 20 Jul 2009 00:44:32 -0300
Subject: [pypy-dev] How to make a pypy distribution?
Message-ID: <92C9FF4D-570C-46AC-A064-3CA2EB36D0B0@gmail.com>

I want to make binaries to pypy and distribute but I don't know how.  
The biggest problem is that I didn't find were I can change the 2  
hardcoded sys.path entries (lib python and modified lib python). I  
would like it to look to a relative dir from where pypy-c is, or at  
least be able to hardcode it to something sensible (not my wc dir).  
Here is the scenario that I want to address:

A self contained pypy, with pypy-c in pypy/bin and libs in pypy/lib or  
maybe pypy/lib/pypy (so instead of on its on directory it can be  
easily moved to /usr/local for example).

I want to start to distribute a compiled version of pypy for macs  
(based on trunk). For people to have the biggest set of package to  
test on I am translating with this command line:

./translate.py --thread --stackless --gc=hybrid  
targetpypystandalone.py  --allworkingmodules

Do anyone think that there is a better set of options? (maybe -- 
gc=hybrid is not needed but I want to be sure never to try to use boehm)


--
Leonardo Santagada
santagada at gmail.com





From anto.cuni at gmail.com  Mon Jul 20 10:11:21 2009
From: anto.cuni at gmail.com (Antonio Cuni)
Date: Mon, 20 Jul 2009 10:11:21 +0200
Subject: [pypy-dev] How to make a pypy distribution?
In-Reply-To: <92C9FF4D-570C-46AC-A064-3CA2EB36D0B0@gmail.com>
References: <92C9FF4D-570C-46AC-A064-3CA2EB36D0B0@gmail.com>
Message-ID: <4A6426A9.2030802@gmail.com>

Hi Leonardo,

Leonardo Santagada wrote:
> I want to make binaries to pypy and distribute but I don't know how.  
> The biggest problem is that I didn't find were I can change the 2  
> hardcoded sys.path entries (lib python and modified lib python). I  
> would like it to look to a relative dir from where pypy-c is, or at  
> least be able to hardcode it to something sensible (not my wc dir).  
> Here is the scenario that I want to address:
> 
> A self contained pypy, with pypy-c in pypy/bin and libs in pypy/lib or  
> maybe pypy/lib/pypy (so instead of on its on directory it can be  
> easily moved to /usr/local for example).

look at this:
http://codespeak.net/pypy/dist/pypy/doc/getting-started-python.html#installation

basically, you could do something like this:

/opt/pypy/bin/pypy-c
/opt/pypy/lib-python/...
/opt/pypy/pypy/lib/...

or like this:

/usr/local/bin/pypy
/usr/local/share/pypy-1.1/lib-python/...
/usr/local/share/pypy-1.1/pypy/lib/...

ciao,
Anto


From santagada at gmail.com  Mon Jul 20 14:59:54 2009
From: santagada at gmail.com (Leonardo Santagada)
Date: Mon, 20 Jul 2009 09:59:54 -0300
Subject: [pypy-dev] How to make a pypy distribution?
In-Reply-To: <4A6426A9.2030802@gmail.com>
References: <92C9FF4D-570C-46AC-A064-3CA2EB36D0B0@gmail.com>
	<4A6426A9.2030802@gmail.com>
Message-ID: <2f2e5f950907200559m314edf59y5ec830e5300b384c@mail.gmail.com>

On Mon, Jul 20, 2009 at 5:11 AM, Antonio Cuni <anto.cuni at gmail.com> wrote:

> Hi Leonardo,
>
> Leonardo Santagada wrote:
>
>> I want to make binaries to pypy and distribute but I don't know how.  The
>> biggest problem is that I didn't find were I can change the 2  hardcoded
>> sys.path entries (lib python and modified lib python). I  would like it to
>> look to a relative dir from where pypy-c is, or at  least be able to
>> hardcode it to something sensible (not my wc dir).  Here is the scenario
>> that I want to address:
>>
>> A self contained pypy, with pypy-c in pypy/bin and libs in pypy/lib or
>>  maybe pypy/lib/pypy (so instead of on its on directory it can be  easily
>> moved to /usr/local for example).
>>
>
> look at this:
>
> http://codespeak.net/pypy/dist/pypy/doc/getting-started-python.html#installation
>
> basically, you could do something like this:
>
> /opt/pypy/bin/pypy-c
> /opt/pypy/lib-python/...
> /opt/pypy/pypy/lib/...
>
> or like this:
>
> /usr/local/bin/pypy
> /usr/local/share/pypy-1.1/lib-python/...
> /usr/local/share/pypy-1.1/pypy/lib/...
>
> ciao,
> Anto
>

I don't know how I missed that, thanks! I will do a fresh checkout and
build from it tonight.

-- 
Leonardo Santagada
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/pypy-dev/attachments/20090720/19a4e2eb/attachment.html>

From anto.cuni at gmail.com  Mon Jul 27 21:47:08 2009
From: anto.cuni at gmail.com (Antonio Cuni)
Date: Mon, 27 Jul 2009 21:47:08 +0200
Subject: [pypy-dev] [pypy-svn] r66656 -
	pypy/branch/pyjitpl5/pypy/jit/metainterp
In-Reply-To: <20090727190723.622B916C161@codespeak.net>
References: <20090727190723.622B916C161@codespeak.net>
Message-ID: <4A6E043C.5030807@gmail.com>

arigo at codespeak.net wrote:
> Author: arigo
> Date: Mon Jul 27 21:07:20 2009
> New Revision: 66656
> 
> Modified:
>    pypy/branch/pyjitpl5/pypy/jit/metainterp/history.py
>    pypy/branch/pyjitpl5/pypy/jit/metainterp/optimize.py
> Log:
> An RPython-friendly way to dump a loop.


in case you don't know, there is already code that serves this purpose, in 
backend.support.AbstractLogger (used by both x86 and cli backend); you can 
just set the PYPYJITLOG env variable and you get a .ops file containing a 
textual representation of the loop (btw, it would be nice to have a graphical 
viewer for it... hint hint :-)).



From arigo at tunes.org  Tue Jul 28 11:45:30 2009
From: arigo at tunes.org (Armin Rigo)
Date: Tue, 28 Jul 2009 11:45:30 +0200
Subject: [pypy-dev] [pypy-svn] r66656 -
	pypy/branch/pyjitpl5/pypy/jit/metainterp
In-Reply-To: <4A6E043C.5030807@gmail.com>
References: <20090727190723.622B916C161@codespeak.net>
	<4A6E043C.5030807@gmail.com>
Message-ID: <20090728094530.GA31766@code0.codespeak.net>

Hi Anto,

On Mon, Jul 27, 2009 at 09:47:08PM +0200, Antonio Cuni wrote:
> in case you don't know, there is already code that serves this purpose, in 
> backend.support.AbstractLogger (used by both x86 and cli backend);

Right, I kind of forgot.  My purpose here was to dump the loop *before*
it goes through optimization, but I guess I could just have imported
from backend.support.

> (btw, it would be nice to have a graphical 
> viewer for it... hint hint :-)).

You may know about backend.x86.viewcode, but this one is only a
graphical viewer for the other log file produced by x86, i.e. the
assembler.  So, yes :-)


A bientot,

Armin.


From vincent.legoll at gmail.com  Wed Jul 29 16:38:55 2009
From: vincent.legoll at gmail.com (Vincent Legoll)
Date: Wed, 29 Jul 2009 16:38:55 +0200
Subject: [pypy-dev] supporting new libraries
Message-ID: <4727185d0907290738x7f8b4d7cy8ab580204b46ce7f@mail.gmail.com>

Hello,

I would like to know how hard it is to support new libraries,
for example (probably far from the simplest, but would certainly
be cool to have - kind) pygtk (+pygobject, etc...)

Could someone help in finding what would be needed to get
that one(s) working ? Maybe with an approximate estimation
of the difficulty of each step, or what kind of required knowledge
to have.

In case it would be too early to attempt such project, a slight
explanation of what are the blocking points.

That kind of information could (should ?) be added to wiki or FAQ,
as a honey-pot for new contributors...

The help could simply be a pointer to the obvious documentation
that I managed to miss

user at host:~/repo/svn/pypy-trunk/pypy/translator/goal$ ./pypy-c -c 'import pygtk'
Traceback (most recent call last):
  File "?", line 33, in run_toplevel
  File "?", line 349, in run_it
  File "<string>", line 1, in <module>
ImportError: No module named pygtk

-- 
Vincent Legoll


From list-sink at trainedmonkeystudios.org  Thu Jul 30 02:59:13 2009
From: list-sink at trainedmonkeystudios.org (Terrence Cole)
Date: Wed, 29 Jul 2009 17:59:13 -0700
Subject: [pypy-dev] supporting new libraries
In-Reply-To: <4727185d0907290738x7f8b4d7cy8ab580204b46ce7f@mail.gmail.com>
References: <4727185d0907290738x7f8b4d7cy8ab580204b46ce7f@mail.gmail.com>
Message-ID: <1248915553.14892.10.camel@localhost>

On Wed, 2009-07-29 at 16:38 +0200, Vincent Legoll wrote:
> Hello,
> 
> I would like to know how hard it is to support new libraries,
> for example (probably far from the simplest, but would certainly
> be cool to have - kind) pygtk (+pygobject, etc...)

I think that pygtk/pygobject are generated mostly automatically through
glib introspect scripts.  If so, it would be on the easy side of a hard
problem.

> Could someone help in finding what would be needed to get
> that one(s) working ? Maybe with an approximate estimation
> of the difficulty of each step, or what kind of required knowledge
> to have.

> In case it would be too early to attempt such project, a slight
> explanation of what are the blocking points.
> 
> That kind of information could (should ?) be added to wiki or FAQ,
> as a honey-pot for new contributors...
> 
> The help could simply be a pointer to the obvious documentation
> that I managed to miss

I think pypy/doc/rffi.txt is what you are looking for, but I could be
completely off base since I have not done anything like this myself as
of yet.

> user at host:~/repo/svn/pypy-trunk/pypy/translator/goal$ ./pypy-c -c 'import pygtk'
> Traceback (most recent call last):
>   File "?", line 33, in run_toplevel
>   File "?", line 349, in run_it
>   File "<string>", line 1, in <module>
> ImportError: No module named pygtk
> 

Terrence



From mellerf at netvision.net.il  Thu Jul 30 12:02:24 2009
From: mellerf at netvision.net.il (Yosef Meller)
Date: Thu, 30 Jul 2009 13:02:24 +0300
Subject: [pypy-dev] Fix for build problem in Hebrew locales
Message-ID: <4A716FB0.90109@netvision.net.il>

Hi all,

I'm in the process of doing my first translation of pypy-c, and have 
encountered a problem in running the translation. The issue is that 
Subversion automatically replaces the string $LastChanged$ with a date, 
and in Hebrew locales that date includes an apostrophe, while the string 
  in the code is also delimited with apostrophes. The attached patch 
solves this by delimiting with quotation marks instead.

Yours,
Yosef.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: allow_hebrew.patch
Type: text/x-diff
Size: 563 bytes
Desc: not available
URL: <http://mail.python.org/pipermail/pypy-dev/attachments/20090730/e525c628/attachment.patch>

From arigo at tunes.org  Thu Jul 30 16:18:45 2009
From: arigo at tunes.org (Armin Rigo)
Date: Thu, 30 Jul 2009 16:18:45 +0200
Subject: [pypy-dev] Fix for build problem in Hebrew locales
In-Reply-To: <4A716FB0.90109@netvision.net.il>
References: <4A716FB0.90109@netvision.net.il>
Message-ID: <20090730141844.GA11398@code0.codespeak.net>

Hi Yosef,

On Thu, Jul 30, 2009 at 01:02:24PM +0300, Yosef Meller wrote:
> Index: py/__init__.py

If it's in the "py" subdirectory, then it's in the py lib, not (strictly
speaking) in pypy.  The py lib is an independent project.  You should in
the future report the issue and the fix to py-dev at codespeak.net.  BTW, I
looked in the py lib and it seems that the current trunk version no
longer uses $LastChangedDate at all, so there should not be any problem
left; it's just that pypy uses a (slightly) older version.


Thanks,

Armin


From arigo at tunes.org  Fri Jul 31 14:04:37 2009
From: arigo at tunes.org (Armin Rigo)
Date: Fri, 31 Jul 2009 14:04:37 +0200
Subject: [pypy-dev] supporting new libraries
In-Reply-To: <1248915553.14892.10.camel@localhost>
References: <4727185d0907290738x7f8b4d7cy8ab580204b46ce7f@mail.gmail.com>
	<1248915553.14892.10.camel@localhost>
Message-ID: <20090731120437.GA15676@code0.codespeak.net>

Hi Vincent,

On Wed, Jul 29, 2009 at 05:59:13PM -0700, Terrence Cole wrote:
> > I would like to know how hard it is to support new libraries,
> > for example (probably far from the simplest, but would certainly
> > be cool to have - kind) pygtk (+pygobject, etc...)
> 
> I think pypy/doc/rffi.txt is what you are looking for, but I could be
> completely off base since I have not done anything like this myself as
> of yet.

That's an entry point, yes.  We have an "internal sprint" in August
where we will meet each other (as opposed to now where everybody is on
its own side and on vacation anyway).  We could, and indeed should,
discuss the topic at the sprint a bit more.


A bientot,

Armin.


From vincent.legoll at gmail.com  Fri Jul 31 14:14:17 2009
From: vincent.legoll at gmail.com (Vincent Legoll)
Date: Fri, 31 Jul 2009 14:14:17 +0200
Subject: [pypy-dev] supporting new libraries
In-Reply-To: <20090731120437.GA15676@code0.codespeak.net>
References: <4727185d0907290738x7f8b4d7cy8ab580204b46ce7f@mail.gmail.com>
	<1248915553.14892.10.camel@localhost>
	<20090731120437.GA15676@code0.codespeak.net>
Message-ID: <4727185d0907310514u75326721jf4eab60abd1d0b10@mail.gmail.com>

On Fri, Jul 31, 2009 at 2:04 PM, Armin Rigo<arigo at tunes.org> wrote:
> On Wed, Jul 29, 2009 at 05:59:13PM -0700, Terrence Cole wrote:
>> > I would like to know how hard it is to support new libraries,
>> > for example (probably far from the simplest, but would certainly
>> > be cool to have - kind) pygtk (+pygobject, etc...)
>>
>> I think pypy/doc/rffi.txt is what you are looking for, but I could be
>> completely off base since I have not done anything like this myself as
>> of yet.
>
> That's an entry point, yes. ?We have an "internal sprint" in August
> where we will meet each other (as opposed to now where everybody is on
> its own side and on vacation anyway). ?We could, and indeed should,
> discuss the topic at the sprint a bit more.

I've read the rffi.txt but it's not sufficient for me to understand
what would be needed to start working on this. I'll try to look
harder though.

I'm curious, were would that August sprint take place ?

-- 
Vincent Legoll


From arigo at tunes.org  Fri Jul 31 15:06:33 2009
From: arigo at tunes.org (Armin Rigo)
Date: Fri, 31 Jul 2009 15:06:33 +0200
Subject: [pypy-dev] supporting new libraries
In-Reply-To: <4727185d0907310514u75326721jf4eab60abd1d0b10@mail.gmail.com>
References: <4727185d0907290738x7f8b4d7cy8ab580204b46ce7f@mail.gmail.com>
	<1248915553.14892.10.camel@localhost>
	<20090731120437.GA15676@code0.codespeak.net>
	<4727185d0907310514u75326721jf4eab60abd1d0b10@mail.gmail.com>
Message-ID: <20090731130633.GA20493@code0.codespeak.net>

Hi Vincent,

On Fri, Jul 31, 2009 at 02:14:17PM +0200, Vincent Legoll wrote:
> I've read the rffi.txt but it's not sufficient for me to understand
> what would be needed to start working on this. I'll try to look
> harder though.

There is also a FAQ entry "How do I write extension modules for PyPy?".

> I'm curious, were would that August sprint take place ?

It's taking place in Gothenburg, Sweden.  It's an internal sprint on the
topic of the JIT, so even if I guess that we are not strictly closed to
everybody else, it's not the best place to get lots of support on a
different topic like writing extension modules.  (We might discuss the
current status of the topic as a one-hour "extra" though.)

We have vague plans for a public sprint around october in D?sseldorf,
Germany, which would probably be a better place to be in :-)


A bientot,

Armin.


From theller at ctypes.org  Fri Jul 31 18:27:22 2009
From: theller at ctypes.org (Thomas Heller)
Date: Fri, 31 Jul 2009 18:27:22 +0200
Subject: [pypy-dev] supporting new libraries
In-Reply-To: <20090731130633.GA20493@code0.codespeak.net>
References: <4727185d0907290738x7f8b4d7cy8ab580204b46ce7f@mail.gmail.com>	<1248915553.14892.10.camel@localhost>	<20090731120437.GA15676@code0.codespeak.net>	<4727185d0907310514u75326721jf4eab60abd1d0b10@mail.gmail.com>
	<20090731130633.GA20493@code0.codespeak.net>
Message-ID: <h4v615$gds$1@ger.gmane.org>

Armin Rigo schrieb:
> 
> We have vague plans for a public sprint around october in D?sseldorf,
> Germany, which would probably be a better place to be in :-)
> 

That would be interesting to me!  Are you doing your sprints over weekends, or
in the week?

-- 
Thanks,
Thomas