Re: [Pythonmac-SIG] Appscript and Snow Leopard and setuptools...
On 17 Sep, 2009, at 23:50, Bill Janssen wrote: Ronald Oussoren ronaldousso...@mac.com wrote: Bill, Appscript probably gets installed as a zipped egg, the .python-eggs directory gets created when a real filesystem path is needed for an item in such an egg. Yes, that's part of the problem. The other part is that .pth handling seems to have changed from 2.5 to 2.6. If you install appscript as an unzipped egg the problem should go away. How does one do that? Either python setup.py bdist_egg and then use the right flags to easy_install; or add 'zip_safe = False' to the arguments of setup() in setup.py install install using python setup.py install. Ronald smime.p7s Description: S/MIME cryptographic signature ___ Pythonmac-SIG maillist - Pythonmac-SIG@python.org http://mail.python.org/mailman/listinfo/pythonmac-sig
Re: [Pythonmac-SIG] Appscript and Snow Leopard and setuptools...
On 17 Sep, 2009, at 23:50, Bill Janssen wrote: Ronald Oussoren ronaldousso...@mac.com wrote: Bill, Appscript probably gets installed as a zipped egg, the .python-eggs directory gets created when a real filesystem path is needed for an item in such an egg. Yes, that's part of the problem. The other part is that .pth handling seems to have changed from 2.5 to 2.6. That's news to me. I've been using zipped eggs with 2.6 without any problems. Ronald smime.p7s Description: S/MIME cryptographic signature ___ Pythonmac-SIG maillist - Pythonmac-SIG@python.org http://mail.python.org/mailman/listinfo/pythonmac-sig
Re: [Pythonmac-SIG] Appscript and Snow Leopard and setuptools...
Ronald Oussoren ronaldousso...@mac.com wrote: On 17 Sep, 2009, at 23:50, Bill Janssen wrote: Ronald Oussoren ronaldousso...@mac.com wrote: Bill, Appscript probably gets installed as a zipped egg, the .python-eggs directory gets created when a real filesystem path is needed for an item in such an egg. Yes, that's part of the problem. The other part is that .pth handling seems to have changed from 2.5 to 2.6. If you install appscript as an unzipped egg the problem should go away. How does one do that? Either python setup.py bdist_egg and then use the right flags to easy_install; or add 'zip_safe = False' to the arguments of setup() in setup.py install install using python setup.py install. Thanks, Ronald. Hmmm. Neither seems ideal. The first idea involves actually *using* setuptools (easy_install), and the second involves editing the setup.py file. I suppose I could use python setup.py bdist_egg, then use unzip to unpack it in the right place, too. Bill ___ Pythonmac-SIG maillist - Pythonmac-SIG@python.org http://mail.python.org/mailman/listinfo/pythonmac-sig
Re: [Pythonmac-SIG] Appscript and Snow Leopard and setuptools...
Ronald Oussoren ronaldousso...@mac.com wrote: Yes, that's part of the problem. The other part is that .pth handling seems to have changed from 2.5 to 2.6. That's news to me. I've been using zipped eggs with 2.6 without any problems. Don't know that it had anything to do with eggs. What I was seeing was different sys.path construction between 2.5 and 2.6, both on SL. In 2.5, it went through and added the directories specified by .pth files in /Library/Python/2.5/site-packages; in 2.6, it didn't. Perhaps I'm just misunderstanding the way the processing of .pth files works. Bill ___ Pythonmac-SIG maillist - Pythonmac-SIG@python.org http://mail.python.org/mailman/listinfo/pythonmac-sig
Re: [Pythonmac-SIG] py2app cannot move to target thread error
Scott Frankel wrote: Thanks for the info and sample code! I've now got libqsqlpsql.bundle copying to the app bundle's frameworks dir. Reading http://doc.trolltech.com/4.4/deployment-mac.html#linking-the-application-to-qt-as-frameworks, I'm knee deep in otool and install_name_tool. I had no idea I had to wrestle with this for a Python app. I'll post back to the list once I've got things working. Ideally, when you've got it figured out, it could be turned into a py2app recipe and contributed to trunk -- hint, hint! -Chris -- Christopher Barker, Ph.D. Oceanographer Emergency Response Division NOAA/NOS/ORR(206) 526-6959 voice 7600 Sand Point Way NE (206) 526-6329 fax Seattle, WA 98115 (206) 526-6317 main reception chris.bar...@noaa.gov ___ Pythonmac-SIG maillist - Pythonmac-SIG@python.org http://mail.python.org/mailman/listinfo/pythonmac-sig
[Pythonmac-SIG] machine architecture 32/64 with Python 2.6 on Snow Leopard?
I'm running /usr/bin/python on SL, and
import platform; print platform.machine()
give me
i386
But Activity Monitor shows Python as Intel (64-bit).
Is this a bug in platform.machine(), or am I misunderstanding what i386
means? platform.architecture() returns ('64bit', '').
Bill
___
Pythonmac-SIG maillist - Pythonmac-SIG@python.org
http://mail.python.org/mailman/listinfo/pythonmac-sig
Re: [Pythonmac-SIG] machine architecture 32/64 with Python 2.6 on Snow Leopard?
If you run the CLI 'uname -m' on any Intel Mac, it always has returned
i386. So all it really means is 'Intel'.
On Sep 18, 2009, at 5:53 PM, Bill Janssen wrote:
I'm running /usr/bin/python on SL, and
import platform; print platform.machine()
give me
i386
But Activity Monitor shows Python as Intel (64-bit).
Is this a bug in platform.machine(), or am I misunderstanding what
i386
means? platform.architecture() returns ('64bit', '').
Bill
___
Pythonmac-SIG maillist - Pythonmac-SIG@python.org
http://mail.python.org/mailman/listinfo/pythonmac-sig
-
William Kyngesburye kyngchaos*at*kyngchaos*dot*com
http://www.kyngchaos.com/
Mon Dieu! but they are all alike. Cheating, murdering, lying,
fighting, and all for things that the beasts of the jungle would not
deign to possess - money to purchase the effeminate pleasures of
weaklings. And yet withal bound down by silly customs that make them
slaves to their unhappy lot while firm in the belief that they be the
lords of creation enjoying the only real pleasures of existence
- the wisdom of Tarzan
___
Pythonmac-SIG maillist - Pythonmac-SIG@python.org
http://mail.python.org/mailman/listinfo/pythonmac-sig
Re: [Pythonmac-SIG] machine architecture 32/64 with Python 2.6 on Snow Leopard?
William Kyngesburye wokl...@kyngchaos.com wrote:
If you run the CLI 'uname -m' on any Intel Mac, it always has returned
i386. So all it really means is 'Intel'.
On Sep 18, 2009, at 5:53 PM, Bill Janssen wrote:
I'm running /usr/bin/python on SL, and
import platform; print platform.machine()
give me
i386
But Activity Monitor shows Python as Intel (64-bit).
Is this a bug in platform.machine(), or am I misunderstanding what
i386
means? platform.architecture() returns ('64bit', '').
Hmmm. So what's the pythonic way of getting i386 vs. x86_64?
{'32bit': 'i386', '64bit': 'x86_64'}[platform.architecture()[0]]
seems so complicated that there should be a routine for it in sys or
platform.
Bill
___
Pythonmac-SIG maillist - Pythonmac-SIG@python.org
http://mail.python.org/mailman/listinfo/pythonmac-sig
Re: [Pythonmac-SIG] machine architecture 32/64 with Python 2.6 on Snow Leopard?
On Sep 18, 2009, at 5:05 PM, Bill Janssen wrote:
William Kyngesburye wokl...@kyngchaos.com wrote:
If you run the CLI 'uname -m' on any Intel Mac, it always has
returned
i386. So all it really means is 'Intel'.
On Sep 18, 2009, at 5:53 PM, Bill Janssen wrote:
I'm running /usr/bin/python on SL, and
import platform; print platform.machine()
give me
i386
But Activity Monitor shows Python as Intel (64-bit).
Is this a bug in platform.machine(), or am I misunderstanding what
i386
means? platform.architecture() returns ('64bit', '').
Hmmm. So what's the pythonic way of getting i386 vs. x86_64?
{'32bit': 'i386', '64bit': 'x86_64'}[platform.architecture()[0]]
seems so complicated that there should be a routine for it in sys or
platform.
I don't know the official way, but what I do is:
% python -c 'import sys;print sys.maxint'
9223372036854775807
% env VERSIONER_PYTHON_PREFER_32_BIT=1 python -c 'import sys;print
sys.maxint'
2147483647
So I would look at sys.maxint to determine if python is running 32 or
64-bit.
Ed
___
Pythonmac-SIG maillist - Pythonmac-SIG@python.org
http://mail.python.org/mailman/listinfo/pythonmac-sig
Re: [Pythonmac-SIG] machine architecture 32/64 with Python 2.6 on Snow Leopard?
I think I'm just going to put '32bit' or '64bit' in my installer name strings.
Bill
e...@apple.com wrote:
On Sep 18, 2009, at 5:05 PM, Bill Janssen wrote:
William Kyngesburye wokl...@kyngchaos.com wrote:
If you run the CLI 'uname -m' on any Intel Mac, it always has
returned
i386. So all it really means is 'Intel'.
On Sep 18, 2009, at 5:53 PM, Bill Janssen wrote:
I'm running /usr/bin/python on SL, and
import platform; print platform.machine()
give me
i386
But Activity Monitor shows Python as Intel (64-bit).
Is this a bug in platform.machine(), or am I misunderstanding what
i386
means? platform.architecture() returns ('64bit', '').
Hmmm. So what's the pythonic way of getting i386 vs. x86_64?
{'32bit': 'i386', '64bit': 'x86_64'}[platform.architecture()[0]]
seems so complicated that there should be a routine for it in sys or
platform.
I don't know the official way, but what I do is:
% python -c 'import sys;print sys.maxint'
9223372036854775807
% env VERSIONER_PYTHON_PREFER_32_BIT=1 python -c 'import sys;print
sys.maxint'
2147483647
So I would look at sys.maxint to determine if python is running 32 or
64-bit.
Ed
___
Pythonmac-SIG maillist - Pythonmac-SIG@python.org
http://mail.python.org/mailman/listinfo/pythonmac-sig
