pinterface

Thanks for bringing this question up. b-b occupies enough space in my mind to periodically surface in an "Oh man, I need to work on that!" sort of way, complete...

While I'm doubtful issues with competing runtimes could be solved completely transparently, which is always my ideal, they can certainly be surfaced where relevant (see #13, again). It might be...

Right now, no, that doesn't work. I'm unfamiliar with how virtualenv works, so I have no idea what it would take to make that possible. Right now, b-b only works...

Dude, could you be a little less awesome? You're making me look bad! :P But seriously, thanks for kicking ass, man. I will look at this in depth this week...

Okay, proper review time! My apologies for failing to meet my own deadline. Overall: This is a _fantastic_ start! So much good stuff here! This response is long, but mostly...

On 2015.06.24 22:52, Mariano Montone wrote: > On 24/06/15 19:40, pinterface wrote: > > > # Functions Dealing with FILE\* (fopen, PyRun_AnyFile, etc.) > > > > ... > >...

Hrm... in theory, one could qualify the forms in ffi-interface.lisp which mention :long-long with a #-cffi-sys::no-long-long. You'd lose access to that particular functionality (so no PyLong_FromLongLong, etc.), but if you...

#-no-long-long should already account for CFFI supporting :long-long on 64bit Allegro, no? I'm not sure I understand what you're asking in relation to modern mode. Are you saying you want...

Neat! If I'm understanding this correctly, it essentially stuffs Python's stdout and stderr into strings, much like the CL:WITH-OUTPUT-TO-STRING macro, yes? There are certainly cases where that's good enough (and...

Interesting! I kind of expected it'd be a lot more effort to get Python 3 even a little usable, so having a preliminary version is exciting. I'll try to take...