Re: import of zexp containing Page Template objects causes sudden zope death

Chris Withers <[email protected]>
Newsgroups gmane.comp.web.zope.devel
Message-ID <[email protected]>
Tim Hoffman wrote:
> on linux 
> 
> timh@chrome:~$ file /usr/bin/python2.5
> /usr/bin/python2.5: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), 
> dynamically linked (uses shared libs), for GNU/Linux 2.6.15, stripped
> timh@chrome:~$ 

Right, so the linux boxes are 32-bit as I suspected:

$ file /usr/local/bin/python2.6
/usr/local/bin/python2.6: ELF 32-bit LSB executable, Intel 80386, 
version 1 (SYSV), for GNU/Linux 2.2.5, dynamically linked (uses shared 
libs), not stripped

$ file /usr/local/bin/python2.6
/usr/local/bin/python2.6: ELF 32-bit LSB executable, Intel 80386, 
version 1 (SYSV), dynamically linked (uses shared libs), for GNU/Linux 
2.6.8, not stripped

> os/x will work the same.

Sadly not:

$ file /Library/Frameworks/Python.framework/Versions/2.6/bin/python2.6
/Library/Frameworks/Python.framework/Versions/2.6/bin/python2.6: Mach-O 
universal binary with 2 architectures
/Library/Frameworks/Python.framework/Versions/2.6/bin/python2.6 (for 
architecture ppc):	Mach-O executable ppc
/Library/Frameworks/Python.framework/Versions/2.6/bin/python2.6 (for 
architecture i386):	Mach-O executable i386

Nonetheless, why would a .zexp on a 32-bit architecture and import on 
64-bit cause sudden crash death when viewing /manage_main of a an 
imported folder containing Page Templates?!

Still in "wtf?!" mode...

Chris

-- 
Simplistix - Content Management, Batch Processing & Python Consulting
             - http://www.simplistix.co.uk
_______________________________________________
Zope-Dev maillist  -  [email protected]
https://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
 https://mail.zope.org/mailman/listinfo/zope-announce
 https://mail.zope.org/mailman/listinfo/zope )
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.