[Bf-committers] Python 2.3 and Windows
Willian Padovani Germano
Wed, 28 Apr 2004 00:30:27 -0300
Hi, thanks Douglas and Kent
(forgot to mention that I used Martin's (theeth) win build for the tests --
> > Python 2.3 (#1, Sep 13 2003, 00:49:11)
> > [GCC 3.3 20030304 (Apple Computer, Inc. build 1495)] on darwin
> > Type "help", "copyright", "credits" or "license" for more information.
> > >>> import sys; print sys.builtin_module_names
> > ('__builtin__', '__main__', '_codecs', '_sre', '_symtable', 'errno',
> > 'exceptions', 'gc', 'imp', 'marshal', 'posix', 'signal', 'sys',
> > 'thread', 'xxsubtype', 'zipimport')
Few modules, like on Linux -- natural, since Python can be considered a standard
component in modern *nix platforms. So, for these, packages of modules would be
considerably bigger, including many system specific shared libraries. We can
1) Assume that users of the cooler platforms should have full Python 2.3
installed already or do that themselves (just download, configure
with --enable-shared and compile, it installs to /usr/local/ and doesn't mess
with older versions available);
2) Tweak Python's compilation in each or some of these systems to get a library
with more builtin modules to link against Blender. This will make Blender
bigger, of course.
3) Create extra packages of modules anyway for all or at least some platforms,
available for those who prefer to download one of them instead of full Python.
Personally, I prefer (1), but of these systems I only use Linux.