On Feb 22, 2005, at 1:25, Roger Binns wrote:
[BTW I apologise for not updating the subject. My questions are
in the bigger picture context of Python on Mac, not the need for
PantherPythonFix]
You quoted something about link-time linker support for frameworks
and then talk about runtime linker sup
>/usr/bin/magic determines the file type heuristically by parsing
>/usr/share/file/magic and then reading a couple bytes out of the given
>file.
>
>This appears to be a direct Python translation of the file command,
>with an embedded copy of a magic table:
>http://www.demonseed.net/~jp/code/magi
You were (Bob was) more or less right -- which is no surprise. The
problem turned out to stem from the fact that when the
dialog-processing code adds a new word as a dictionary key, what it
adds is a string that wx.TextCtrl returns when a word is
double-clicked. On Windows, this included a trai
so if you build all of your extensions on a 10.2 environment
BTW I don't actually have a 10.2 environment. The Mac Mini comes
with 10.3.
In other words for a maximally redistributable application:
- Install PantherPythonFix immediately, on any Mac OS X 10.3 machine
that you will use distutils on
On Feb 22, 2005, at 12:18, Roger Binns wrote:
so if you build all of your extensions on a 10.2 environment
BTW I don't actually have a 10.2 environment. The Mac Mini comes
with 10.3.
Then you can't build 10.2 compatible software.. no big deal.
In other words for a maximally redistributable applica
Charles Hartman <[EMAIL PROTECTED]> writes:
> So why did my wx.TextCtrl show different double-click behavior on the
> two platforms? Though I'm using Python 2.3 on both, my wxPython on Mac
> is 2.5.3.1 and on Win it was 2.5.2.8 (dumb!) so I thought that might
> be the problem. But no: I upgraded o
Bob Ippolito wrote:
It is not yet public knowledge as to whether applications built with
the vendor Python 2.3.0 on Mac OS X 10.3 will work on Mac OS X 10.4.
Given that Python 2.3.x was in the WWDC sources and setup to build as
a framework in the same place, then signs point to yes. However, if
Ap
On Feb 22, 2005, at 17:23, Chris Barker wrote:
Bob Ippolito wrote:
It is not yet public knowledge as to whether applications built with
the vendor Python 2.3.0 on Mac OS X 10.3 will work on Mac OS X 10.4.
Given that Python 2.3.x was in the WWDC sources and setup to build as
a framework in the same
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
HI all,
this is probably a question that has been answered on the wiki, but i
can't seem to find it.
I decided to try and upgrade my version of Numeric (currently 23.1)
(building the latest Biopython was causing errors) but the
packagmanager give
Bob Ippolito wrote:
I also rarely screw with PATH. Using /usr/bin/env is saying "let PATH
decide".
right. I am always working across platforms, so I want to specify which
python to use, but not specify where to find it.
I use explicit paths like:
# MacPython 2.3.5
/usr/local/bin/python2.3
#
Kim Branson wrote:
HI all,
this is probably a question that has been answered on the wiki, but i
can't seem to find it.
I decided to try and upgrade my version of Numeric (currently 23.1)
(building the latest Biopython was causing errors) but the
packagmanager gives me a 404 errror opening
On Feb 22, 2005, at 18:06, Chris Barker wrote:
Bob Ippolito wrote:
I also rarely screw with PATH. Using /usr/bin/env is saying "let
PATH decide".
right. I am always working across platforms, so I want to specify
which python to use, but not specify where to find it.
I use explicit paths like:
My biggest 3rd party dependency is wxPython. Is there any way of
telling if it was built on a machine with the fix applied?
It wasn't.
Thank you for checking. I have passed on the request to Robin
to run PantherPythonFix on his 10.3 build machine.
There is no vendor Python on Windows, so py2exe
13 matches
Mail list logo
