On Sun, Apr 1, 2012 at 3:51 PM, Stefan Behnel wrote:
> Stefan Behnel, 01.04.2012 15:04:
>> Armin Rigo, 01.04.2012 12:31:
>>> Hi Stefan,
>>>
>>> Done in 623bcea85df3.
>>
>> Thanks, Armin!
>>
>> Would have taken me a while to figure these things out.
>>
>> I'll give it a try with the next nightly.
>
On Sun, Apr 1, 2012 at 3:48 PM, Stefan Behnel wrote:
> Maciej Fijalkowski, 01.04.2012 15:42:
>> On Sun, Apr 1, 2012 at 3:25 PM, Maciej Fijalkowski wrote:
>>> On Sun, Apr 1, 2012 at 3:04 PM, Stefan Behnel wrote:
Armin Rigo, 01.04.2012 12:31:
> Hi Stefan,
>
> Done in 623bcea85df3.
>
Stefan Behnel, 01.04.2012 15:04:
> Armin Rigo, 01.04.2012 12:31:
>> Hi Stefan,
>>
>> Done in 623bcea85df3.
>
> Thanks, Armin!
>
> Would have taken me a while to figure these things out.
>
> I'll give it a try with the next nightly.
Hmm, looks broken:
http://buildbot.pypy.org/builders/pypy-c-ji
Maciej Fijalkowski, 01.04.2012 15:42:
> On Sun, Apr 1, 2012 at 3:25 PM, Maciej Fijalkowski wrote:
>> On Sun, Apr 1, 2012 at 3:04 PM, Stefan Behnel wrote:
>>> Armin Rigo, 01.04.2012 12:31:
Hi Stefan,
Done in 623bcea85df3.
>>>
>>> Thanks, Armin!
>>>
>>> Would have taken me a while to f
On Sun, Apr 1, 2012 at 3:25 PM, Maciej Fijalkowski wrote:
> On Sun, Apr 1, 2012 at 3:04 PM, Stefan Behnel wrote:
>> Armin Rigo, 01.04.2012 12:31:
>>> Hi Stefan,
>>>
>>> Done in 623bcea85df3.
>>
>> Thanks, Armin!
>>
>> Would have taken me a while to figure these things out.
>>
>> I'll give it a tr
On Sun, Apr 1, 2012 at 3:04 PM, Stefan Behnel wrote:
> Armin Rigo, 01.04.2012 12:31:
>> Hi Stefan,
>>
>> Done in 623bcea85df3.
>
> Thanks, Armin!
>
> Would have taken me a while to figure these things out.
>
> I'll give it a try with the next nightly.
>
> Stefan
>
> ___
Armin Rigo, 01.04.2012 12:31:
> Hi Stefan,
>
> Done in 623bcea85df3.
Thanks, Armin!
Would have taken me a while to figure these things out.
I'll give it a try with the next nightly.
Stefan
___
pypy-dev mailing list
pypy-dev@python.org
http://mail.py
Hi Stefan,
Done in 623bcea85df3.
Armin
___
pypy-dev mailing list
pypy-dev@python.org
http://mail.python.org/mailman/listinfo/pypy-dev
Armin Rigo, 21.03.2012 17:55:
> On Mon, Mar 19, 2012 at 09:11, Maciej Fijalkowski wrote:
The (trivial) implementation of the two functions is at the end of this
file:
http://bugs.python.org/file24613/exc_info_capi.patch
Could you add them to PyPy?
>
> The new functio
Hi,
On Mon, Mar 19, 2012 at 09:11, Maciej Fijalkowski wrote:
>>> The (trivial) implementation of the two functions is at the end of this
>>> file:
>>>
>>> http://bugs.python.org/file24613/exc_info_capi.patch
>>>
>>> Could you add them to PyPy?
The new functions make sense to me. Anyone with cp
On Mon, Mar 19, 2012 at 8:44 AM, Stefan Behnel wrote:
> Stefan Behnel, 26.02.2012 20:54:
>> Amaury Forgeot d'Arc, 18.02.2012 15:41:
>>> 2012/2/18 Stefan Behnel
Here's an example.
Python code:
def print_excinfo():
print(sys.exc_info())
Cython code:
Stefan Behnel, 26.02.2012 20:54:
> Amaury Forgeot d'Arc, 18.02.2012 15:41:
>> 2012/2/18 Stefan Behnel
>>> Here's an example.
>>>
>>> Python code:
>>>
>>> def print_excinfo():
>>> print(sys.exc_info())
>>>
>>> Cython code:
>>>
>>> from stuff import print_excinfo
>>>
>>> try:
>>> raise T
Amaury Forgeot d'Arc, 18.02.2012 15:41:
> 2012/2/18 Stefan Behnel
>> Here's an example.
>>
>> Python code:
>>
>> def print_excinfo():
>> print(sys.exc_info())
>>
>> Cython code:
>>
>> from stuff import print_excinfo
>>
>> try:
>> raise TypeError
>> except TypeError:
>> print_exci
Stefan Behnel, 22.02.2012 21:39:
> adding to the list.
>
>> Some more errors that I see in the logs up to that point, which all hint at
>> missing bits of the C-API implementation:
>>
>> specialfloatvals.c:490: error: ‘Py_HUGE_VAL’ undeclared
>
> CPython simply defines this as
>
> #ifndef Py_HUG
Hi,
adding to the list.
Stefan Behnel, 19.02.2012 12:10:
> Some more errors that I see in the logs up to that point, which all hint at
> missing bits of the C-API implementation:
>
> specialfloatvals.c:490: error: ‘Py_HUGE_VAL’ undeclared
CPython simply defines this as
#ifndef Py_HUGE_VAL
#d
Amaury Forgeot d'Arc, 19.02.2012 23:10:
> 2012/2/19 Stefan Behnel
>
>> That's different for PyComplexObject, which allows direct unboxed access to
>> the real and imaginary number fields. Cython makes use of that for
>> interfacing between C/C++ complex and Python complex.
>
> Why don't you use P
2012/2/19 Stefan Behnel
> That's different for PyComplexObject, which allows direct unboxed access to
> the real and imaginary number fields. Cython makes use of that for
> interfacing between C/C++ complex and Python complex.
>
Why don't you use PyComplex_AsCComplex or other similar API for thi
Amaury Forgeot d'Arc, 19.02.2012 18:04:
> 2012/2/19 Stefan Behnel
>> bufaccess.c:22714: error: ‘PyBoolObject’ undeclared
>>
>> bufaccess.c:22715: error: ‘PyComplexObject’ undeclared
>
> Why are these structures needed? Would Cython allow them to be
> only aliases to PyObject?
Not sure about the P
Stefan Behnel, 18.02.2012 11:20:
> Amaury Forgeot d'Arc, 18.02.2012 10:08:
>> I made some modifications to pypy, cython and lxml,
>> and now I can compile and install cython, lxml, and they seem to work!
>>
>> For example::
>> html = etree.Element("html")
>> body = etree.SubElement(html, "b
2012/2/19 Stefan Behnel
> bufaccess.c:22714: error: ‘PyBoolObject’ undeclared
>
> bufaccess.c:22715: error: ‘PyComplexObject’ undeclared
>
Why are these structures needed? Would Cython allow them to be
only aliases to PyObject?
--
Amaury Forgeot d'Arc
__
Amaury Forgeot d'Arc, 18.02.2012 21:20:
> 2012/2/18 Stefan Behnel
>
>> And now the question is: how do I debug into PyPy? From the nightly build,
>> I don't get any debugging symbols in gdb, just a useless list of call
>> addresses (running the ref-counting related "arg_incref" test here):
>>
>> "
Amaury Forgeot d'Arc, 18.02.2012 15:41:
> 2012/2/18 Stefan Behnel
>> Here's an example.
>>
>> Python code:
>>
>> def print_excinfo():
>> print(sys.exc_info())
>>
>> Cython code:
>>
>> from stuff import print_excinfo
>>
>> try:
>> raise TypeError
>> except TypeError:
>> print_exci
2012/2/18 Stefan Behnel
> And now the question is: how do I debug into PyPy?
Part of the answer:
I never debug pypy. Even with debug symbols, the (generated)
code is so complex that most of the time you cannot get anything
interesting beyond the function names.
But pypy is written in RPython,
On Sat, Feb 18, 2012 at 3:24 PM, Stefan Behnel wrote:
> Amaury Forgeot d'Arc, 18.02.2012 21:20:
> > 2012/2/18 Stefan Behnel
> >
> >> And now the question is: how do I debug into PyPy? From the nightly
> build,
> >> I don't get any debugging symbols in gdb, just a useless list of call
> >> address
Amaury Forgeot d'Arc, 18.02.2012 21:20:
> 2012/2/18 Stefan Behnel
>
>> And now the question is: how do I debug into PyPy? From the nightly build,
>> I don't get any debugging symbols in gdb, just a useless list of call
>> addresses (running the ref-counting related "arg_incref" test here):
>>
>> "
2012/2/18 Stefan Behnel
> And now the question is: how do I debug into PyPy? From the nightly build,
> I don't get any debugging symbols in gdb, just a useless list of call
> addresses (running the ref-counting related "arg_incref" test here):
>
> """
> #0 0x00ef93ef in ?? ()
> #1 0x000
Hey,
On Sat, Feb 18, 2012 at 11:20 AM, Stefan Behnel wrote:
> Amaury Forgeot d'Arc, 18.02.2012 10:08:
>> I made some modifications to pypy, cython and lxml,
>> and now I can compile and install cython, lxml, and they seem to work!
>>
>> For example::
>> html = etree.Element("html")
>> bod
Stefan Behnel, 18.02.2012 16:29:
> Stefan Behnel, 18.02.2012 09:48:
>> Once we have the test suite runnable, we can set up a PyPy instance on our
>> CI server to get feed-back on any advances.
>>
>> https://sage.math.washington.edu:8091/hudson/
>
> I've set up a build job for my development branch
Stefan Behnel, 18.02.2012 09:48:
> Once we have the test suite runnable, we can set up a PyPy instance on our
> CI server to get feed-back on any advances.
>
> https://sage.math.washington.edu:8091/hudson/
I've set up a build job for my development branch here:
https://sage.math.washington.edu:8
2012/2/18 Stefan Behnel
> Here's an example.
>
> Python code:
>
> def print_excinfo():
> print(sys.exc_info())
>
> Cython code:
>
> from stuff import print_excinfo
>
> try:
> raise TypeError
> except TypeError:
> print_excinfo()
>
> With the code removed, Cython will not store
Amaury Forgeot d'Arc, 18.02.2012 15:18:
> 2012/2/18 Stefan Behnel
>
>> I couldn't find the PyWeakref_LockObject() function anywhere. That's a
>> PyPy-only thing, right? I aliased it to (NULL) when compiling for CPython.
>>
>
> Yes, this function is PyPy-only, to fix a flaw of PyWeakref_GetObject:
2012/2/18 Stefan Behnel
> I couldn't find the PyWeakref_LockObject() function anywhere. That's a
> PyPy-only thing, right? I aliased it to (NULL) when compiling for CPython.
>
Yes, this function is PyPy-only, to fix a flaw of PyWeakref_GetObject:
it returns a borrowed reference, which is very da
Amaury Forgeot d'Arc, 18.02.2012 14:52:
> 2012/2/18 Stefan Behnel
>
>> The exception handling code that you deleted in __Pyx_GetException(), that
>> which accesses exc_type and friends, is actually needed for correct
>> semantics of Cython code and Python code. Basically, it implements the part
>>
2012/2/18 Stefan Behnel
> The exception handling code that you deleted in __Pyx_GetException(), that
> which accesses exc_type and friends, is actually needed for correct
> semantics of Cython code and Python code. Basically, it implements the part
> of the except clause that moves the hot except
2012/2/18 Stefan Behnel
> The weakref changes are really unfortunate as they appear in one of the
> most performance critical spots of lxml's API: on-the-fly proxy creation.
>
> I can understand why the original code won't work as is, but could you
> elaborate on why the weak references are neede
Amaury Forgeot d'Arc, 18.02.2012 10:08:
> 2012/2/18 Stefan Behnel
> I made some modifications to pypy, cython and lxml,
> and now I can compile and install cython, lxml, and they seem to work!
>
> Here are the changes I made, some parts are really hacks and should be
> polished:
> lxml: http://pas
Martijn Faassen, 18.02.2012 14:11:
> For some insight of why people want would lxml, there's an interesting
> discussion on google app engine's bug tracker about it.
>
> http://code.google.com/p/googleappengine/issues/detail?id=18
>
> This type of discussion is instructive as PyPy's barriers to p
Hi there,
On Sat, Feb 18, 2012 at 10:56 AM, Maciej Fijalkowski wrote:
> I somehow doubt it's possible to make this run fast using cpyext
> (although there are definitely some ways). Maybe speeding up
> ElementTree would be the way if all we want to get is a fast XML
> processor? I doubt this is
Amaury Forgeot d'Arc, 18.02.2012 10:08:
> I made some modifications to pypy, cython and lxml,
> and now I can compile and install cython, lxml, and they seem to work!
>
> For example::
> html = etree.Element("html")
> body = etree.SubElement(html, "body")
> body.text = "TEXT"
> br
Maciej Fijalkowski, 18.02.2012 10:56:
> On Sat, Feb 18, 2012 at 11:48 AM, Stefan Behnel wrote:
>> Maciej Fijalkowski, 18.02.2012 10:35:
>>> On Sat, Feb 18, 2012 at 11:27 AM, Stefan Behnel wrote:
Given that XML processing is currently slower in PyPy than in CPython, I
don't think that's al
Maciej Fijalkowski, 18.02.2012 10:56:
> On Sat, Feb 18, 2012 at 11:48 AM, Stefan Behnel wrote:
>> Maciej Fijalkowski, 18.02.2012 10:35:
>>> On Sat, Feb 18, 2012 at 11:27 AM, Stefan Behnel wrote:
Given that XML processing is currently slower in PyPy than in CPython, I
don't think that's al
Amaury Forgeot d'Arc, 18.02.2012 10:08:
> I made some modifications to pypy, cython and lxml,
> and now I can compile and install cython, lxml, and they seem to work!
>
> For example::
> html = etree.Element("html")
> body = etree.SubElement(html, "body")
> body.text = "TEXT"
> br
On Sat, Feb 18, 2012 at 11:48 AM, Stefan Behnel wrote:
> Maciej Fijalkowski, 18.02.2012 10:35:
>> On Sat, Feb 18, 2012 at 11:27 AM, Stefan Behnel wrote:
>>> Given that XML processing is currently slower in PyPy than in CPython, I
>>> don't think that's all that bad. Users can still switch their im
Maciej Fijalkowski, 18.02.2012 10:35:
> On Sat, Feb 18, 2012 at 11:27 AM, Stefan Behnel wrote:
>> Given that XML processing is currently slower in PyPy than in CPython, I
>> don't think that's all that bad. Users can still switch their imports to
>> ElementTree if they only want to push XML out and
On Sat, Feb 18, 2012 at 11:27 AM, Stefan Behnel wrote:
> Amaury Forgeot d'Arc, 18.02.2012 10:08:
>> 2012/2/18 Stefan Behnel
>>> Stefan Behnel, 15.02.2012 12:32:
http://wiki.cython.org/enhancements/pypy
>>>
>>> So, any volunteers or otherwise interested parties to help in getting this
>>> to w
Amaury Forgeot d'Arc, 18.02.2012 10:08:
> 2012/2/18 Stefan Behnel
>> Stefan Behnel, 15.02.2012 12:32:
>>> http://wiki.cython.org/enhancements/pypy
>>
>> So, any volunteers or otherwise interested parties to help in getting this
>> to work? Anyone in for financial support?
>
> Actually I spent seve
Hi,
2012/2/18 Stefan Behnel
> Stefan Behnel, 15.02.2012 12:32:
> > The current state of the discussion seems to be that PyPy provides ways
> to
> > talk to C code, but nothing as complete as CPython's C-API in the sense
> > that it allows efficient two-way communication between C code and Python
Stefan Behnel, 15.02.2012 12:32:
> The current state of the discussion seems to be that PyPy provides ways to
> talk to C code, but nothing as complete as CPython's C-API in the sense
> that it allows efficient two-way communication between C code and Python
> objects. Thus, we need to either impro
Hey,
http://wiki.cython.org/enhancements/pypy
Nice overview of the discussion so far as far I could follow it. I
hope others contribute!
Regards,
Martijn
___
pypy-dev mailing list
pypy-dev@python.org
http://mail.python.org/mailman/listinfo/pypy-dev
Hi,
I'm breaking out of the thread where this topic was started ("offtopic,
ontopic, ...") because it is getting too long and unfocussed to follow.
The current state of the discussion seems to be that PyPy provides ways to
talk to C code, but nothing as complete as CPython's C-API in the sense
th
50 matches
Mail list logo
