mxDateTime on Mac: Fatal Python Error

2005-03-07 Thread contact
I'm trying to get mxDateTime working on a Mac so that I can use pyscopg
and cx_Oracle. The Egenix base package builds and installs quite
happily, but then when I try to import it I get

 import mx.DateTime
Fatal Python error: Interpreter not initialized (version mismatch?)
Abort

... any ideas?

Environment:

OS X 10.3.8
sys.version: '2.3 (#1, Sep 13 2003, 00:49:11) \n[GCC 3.3 20030304
(Apple Computer, Inc. build 1495)]'
egenix-mx-base-2.0.6

-- 
http://mail.python.org/mailman/listinfo/python-list


Re: mxDateTime on Mac: Fatal Python Error

2005-03-07 Thread M.-A. Lemburg
[EMAIL PROTECTED] wrote:
I'm trying to get mxDateTime working on a Mac so that I can use pyscopg
and cx_Oracle. The Egenix base package builds and installs quite
happily, but then when I try to import it I get

import mx.DateTime
Fatal Python error: Interpreter not initialized (version mismatch?)
Abort
... any ideas?
Messages like these are usually the result of a version mismatch
between the Python interpreter and the .so file of the extensions.
Make sure you build the package using the same Python interpreter
you will later use it with.
Environment:
OS X 10.3.8
sys.version: '2.3 (#1, Sep 13 2003, 00:49:11) \n[GCC 3.3 20030304
(Apple Computer, Inc. build 1495)]'
egenix-mx-base-2.0.6
Hmm, this might also be some weird Mac OS issue. While we currently
don't support Macs directly, we do welcome suggestions to make them
work on your favorite platform.
Thanks,
--
Marc-Andre Lemburg
eGenix.com
Professional Python Services directly from the Source  (#1, Mar 07 2005)
 Python/Zope Consulting and Support ...http://www.egenix.com/
 mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/
 mxODBC, mxDateTime, mxTextTools ...http://python.egenix.com/

::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,FreeBSD for free ! 
--
http://mail.python.org/mailman/listinfo/python-list


Re: mxDateTime on Mac: Fatal Python Error

2005-03-07 Thread Dave Reed

On Monday 07 March 2005 17:51, M.-A. Lemburg wrote:
 [EMAIL PROTECTED] wrote:
  I'm trying to get mxDateTime working on a Mac so that I can use 
pyscopg
  and cx_Oracle. The Egenix base package builds and installs quite
  happily, but then when I try to import it I get
  
  
 import mx.DateTime
  
  Fatal Python error: Interpreter not initialized (version mismatch?)
  Abort
  
  ... any ideas?
 
 Messages like these are usually the result of a version mismatch
 between the Python interpreter and the .so file of the extensions.
 
 Make sure you build the package using the same Python interpreter
 you will later use it with.
 
  Environment:
  
  OS X 10.3.8
  sys.version: '2.3 (#1, Sep 13 2003, 00:49:11) \n[GCC 3.3 20030304
  (Apple Computer, Inc. build 1495)]'
  egenix-mx-base-2.0.6
 
 Hmm, this might also be some weird Mac OS issue. While we currently
 don't support Macs directly, we do welcome suggestions to make them
 work on your favorite platform.
 
 Thanks,
 -- 
 Marc-Andre Lemburg
 eGenix.com



Works fine for me on a 2004 PowerBook with 10.3.8.

I'm using Python from DarwinPorts for pygtk and am using mx.DateTime 
with it. I don't remember if DarwinPorts had mx.DateTime or if I 
downloaded the source and installed it myself. I suspect it's the 
version mismatch problem mentioned above.

502 mac:~ $ /opt/local/bin/python
Python 2.3.4 (#1, Nov  9 2004, 21:05:33) 
[GCC 3.3 20030304 (Apple Computer, Inc. build 1666)] on darwin
Type help, copyright, credits or license for more information.
 import mx.DateTime
 


Dave

-- 
http://mail.python.org/mailman/listinfo/python-list


Re: mxDateTime on Mac: Fatal Python Error

2005-03-07 Thread Michael Maibaum
On Mon, Mar 07, 2005 at 11:51:20PM +0100, M.-A. Lemburg wrote:
[EMAIL PROTECTED] wrote:
I'm trying to get mxDateTime working on a Mac so that I can use pyscopg
and cx_Oracle. The Egenix base package builds and installs quite
happily, but then when I try to import it I get

import mx.DateTime
Fatal Python error: Interpreter not initialized (version mismatch?)
Abort
... any ideas?
Messages like these are usually the result of a version mismatch
between the Python interpreter and the .so file of the extensions.
Make sure you build the package using the same Python interpreter
you will later use it with.
It is most likely a result of this:
http://mail.python.org/pipermail/python-dev/2004-December/050324.html
http://www.mail-archive.com/pythonmac-sig@python.org/msg00964.html
Environment:
OS X 10.3.8
sys.version: '2.3 (#1, Sep 13 2003, 00:49:11) \n[GCC 3.3 20030304
(Apple Computer, Inc. build 1495)]'
egenix-mx-base-2.0.6
Hmm, this might also be some weird Mac OS issue. While we currently
don't support Macs directly, we do welcome suggestions to make them
work on your favorite platform.
If it is related to the issue I mention above, then it is a distutils specific bug fixed in current versions of Python, but not in the version installed by default by OS X. 

HTH 

Michael
--
http://mail.python.org/mailman/listinfo/python-list