It seems the python interpreter built by Apple doesn't behave like the
ones built from upstream.
See this:
http://debbugs.gnu.org/cgi/bugreport.cgi?bug=10295#19
Any idea what's happened to python from apple?
Leo
___
Pythonmac-SIG maillist - Pythonma
In article <[email protected]>, Leo wrote:
> It seems the python interpreter built by Apple doesn't behave like the
> ones built from upstream.
>
> See this:
> http://debbugs.gnu.org/cgi/bugreport.cgi?bug=10295#19
>
> Any idea what's happened to python from apple?
Off the top of my head
On 2012-04-17 15:56 +0800, Ned Deily wrote:
> Off the top of my head, I suspect the most likely cause to be that the
> Apple system pythons are built with the BSD editline library rather than
> with GNU readline. You could try installing the third-party "readline"
> package which replaces the P
This is really an Emacs issue, not a Python issue. I don't even see
where they say they are both using the version of the Python interpreter.
Bill
Leo wrote:
> It seems the python interpreter built by Apple doesn't behave like the
> ones built from upstream.
>
> See this:
> http://debbugs.gnu
Hi list
I have an old script using the CoreGraphics API that's no longer working
properly since Snow Leopard.
I' running Lion with the default Python, which is 2.7.1.
I googled about this and it seems that's because Python is 64-bit now and some
old data types don't work anymore.
The first err
João Leão wrote:
> But now I'm getting another error (and I'll probably get some more) with
> another function that expects a CGFloat object instead of a plain integer.
> The code looks like this:
> ---
> self.pdf.drawPlainTextInRect(text_prov, textRect, 10)
> ---
>
> And the error (again cause
> João Leão wrote:
>
>> But now I'm getting another error (and I'll probably get some more) with
>> another function that expects a CGFloat object instead of a plain integer.
>> The code looks like this:
>> ---
>> self.pdf.drawPlainTextInRect(text_prov, textRect, 10)
>> ---
>>
>> And the error
On 2012-04-17 23:27 +0800, Bill Janssen wrote:
> This is really an Emacs issue, not a Python issue. I don't even see
> where they say they are both using the version of the Python interpreter.
Unthinkable.
I have built python 2.7.3 from upstream and see no such bug. Something
is done to python a
