Hey Armin,
On 28 August 2012 11:19, Armin Rigo wrote:
> Hi Mark,
>
> On Mon, Aug 27, 2012 at 3:09 PM, mark florisson
> wrote:
>> For this year's summer of code, and for my master dissertation, we
>> created a project to compile array expressions efficiently (Dag w
Hey,
For this year's summer of code, and for my master dissertation, we
created a project to compile array expressions efficiently (Dag was my
mentor, CCed), which can be found here:
https://github.com/markflorisson88/minivect , the thesis is under
subdirectory 'thesis'. It's currently integrated
On 15 May 2012 17:34, Armin Rigo wrote:
> Hi Yury,
>
> On Tue, May 15, 2012 at 5:56 PM, Yury Selivanov
> wrote:
>> While I don't like some design quirks of Cython, I think that it's far
>> better than any ffi or ctypes-like solution. Essentially, it's an ffi
>> merged with the language, not a s
On 15 May 2012 17:14, Stefan Behnel wrote:
> Maciej Fijalkowski, 15.05.2012 17:39:
>> On Tue, May 15, 2012 at 5:16 PM, Stefan Behnel wrote:
>>> Armin Rigo, 15.05.2012 16:23:
Fijal and me would like to raise interest among various groups of
people about building a better ctypes replacemen
On 14 February 2012 18:10, Antonio Cuni wrote:
> On 02/14/2012 06:56 PM, Stefan Behnel wrote:
>>
>> Ok, then I take it that this would be the preferred Python+FFI approach
>> for
>> interfacing, right? ctypes is out of the loop?
>
>
> note that there are at least two different levels to interface
On 14 February 2012 18:00, Maciej Fijalkowski wrote:
> On Tue, Feb 14, 2012 at 7:56 PM, Stefan Behnel wrote:
>> Amaury Forgeot d'Arc, 14.02.2012 18:45:
>>> 2012/2/14 Stefan Behnel
if PyPy can't come up with a fast way to
interface with C code, it's bound to die.
>>>
>>> But it certainly
On 14 February 2012 15:25, Martijn Faassen wrote:
> On Tue, Feb 14, 2012 at 4:19 PM, Armin Rigo wrote:
>> Hi Martijn,
>>
>> On Tue, Feb 14, 2012 at 14:47, Martijn Faassen
>> wrote:
>>> But Cython-based code does talk to C APIs, so there is a problem.
>>> Python code in PyPy needs to be able to
On 14 February 2012 15:12, Armin Rigo wrote:
> Hi Stefan,
>
> On Tue, Feb 14, 2012 at 14:12, Stefan Behnel wrote:
>> Hmm, if that is so, how would you ever want to make PyPy bidirectionally
>> interface with anything at all? How does ctypes even work in PyPy?
>
> I believe you are not understandi
On 14 February 2012 13:21, Maciej Fijalkowski wrote:
> On Tue, Feb 14, 2012 at 3:12 PM, Stefan Behnel wrote:
>> Armin Rigo, 14.02.2012 13:13:
>>> the main problem is that the RPython-to-C translation that we
>>> do is not just a one-format traduction. We need to tweak the
>>> intermediate code i
On 13 February 2012 23:04, Antonio Cuni wrote:
> On 02/13/2012 11:26 PM, Stefan Behnel wrote:
>>>
>>> > Last time I looked, Cython still generates code that PyPy cannot
>>> > handle:
>>> > for example, it explicitly messes with tstate->curexc_type&co,
>>> > Couldn't PyErr_Fetch() and PyErr_Rest
On 30 May 2011 23:31, Romain Guillebert wrote:
> Hi
>
> I've posted and article on my blog that explains what I've done during
> the community bonding period and the first week of the Google Summer of
> Code :
> http://rguillebert.blogspot.com/2011/05/cython-backend-aiming-pypy-week-1.html
>
> Che
11 matches
Mail list logo
