On Thu, Dec 5, 2013 at 7:07 AM, Brian Curtin wrote:
>
> Not helpful.
>
> I'm in meetings/training/traveling all week, but I'll get another Windows
> build slave up within the next few days. I used to have a spare desktop box
> that ran a build slave as admin so it would exercise the os.symlink cod
On 5 Dec 2013 00:41, "Brett Cannon" wrote:
>
> On 2008-12-03, Python 3.0.0 was released by Barry. I was actually on IRC
the night when it happened, with Guido leaving his office across the hall
from mine. We gave each other a high-five and then we both went home. Not
exactly a party, but I know I
On Tue, Dec 3, 2013 at 8:14 PM, Ryan Gonzalez wrote:
> Just don't run it on Windows...
>
Not helpful.
I'm in meetings/training/traveling all week, but I'll get another Windows
build slave up within the next few days. I used to have a spare desktop box
that ran a build slave as admin so it would
On 2008-12-03, Python 3.0.0 was released by Barry. I was actually on IRC
the night when it happened, with Guido leaving his office across the hall
from mine. We gave each other a high-five and then we both went home. Not
exactly a party, but I know I at least breathed a sigh of relief that
Python 3
Hi Fil,
On Wed, 4 Dec 2013 23:17:11 +1100
Fil Mackay wrote:
>
> I've found that libffi does support this type, but sadly ctypes and cffi do
> not. Adding to ctypes does not seem to be trivial, since the description of
> an integer type is limited to a single character ("q" in the case of long
>
I have been doing some research on getting "int128_t" supported in Python,
and have hit a snag:
I've found that libffi does support this type, but sadly ctypes and cffi do
not. Adding to ctypes does not seem to be trivial, since the description of
an integer type is limited to a single character (
