In the wxPython 2.6.3.3 setup.py we find the following code:
for bo_name in ["build_options.py", "build_options.pyc"]:
if os.path.exists(bo_name):
os.remove(bo_name)
.
copy_file('config.py', 'wx/build', update=1, verbose=1)
copy_file('build_options.py', 'wx/build', update=1, verbose=1)
So, it's removing the build_options.py, and then it's trying to copy
this file to wx/build. On my system, this is resulting in an error:
Traceback (most recent call last):
File "setup.py", line 50, in <module>
copy_file('build_options.py', 'wx/build', update=1, verbose=1)
File "/data/tmp/wd/inst/python/lib/python2.5/distutils/file_util.py",
line 119, in copy_file
"can't copy '%s': doesn't exist or not a regular file" % src
distutils.errors.DistutilsFileError: can't copy 'build_options.py':
doesn't exist or not a regular file
Was this a typo, or am I missing something? Commenting out that
copy_file line fixes the problem. Comments?
Was this a typo, or am I missing something? Commenting out that
copy_file line fixes the problem. Comments?
The intent is that when running wxPython's setup.py the build_options.py file will be recreated with the options that are used for that build. So it is removing the existing file and when config.py is imported it builds another one. However build_options is needed when config.py is imported for building 3rd party extension modules that are using wxPython's config in order to be compatible. So in config.py it triggers the building of a new build_options.py only if there is an exception when trying to import it. So you probably have a build_options.py somewhere else on your PYTHONPATH that is being imported and so the trigger to build the new one doesn't happen.
···
--
Robin Dunn
Software Craftsman http://wxPython.org Java give you jitters? Relax with wxPython!
exception when trying to import it. So you probably have a
build_options.py somewhere else on your PYTHONPATH that is being
imported and so the trigger to build the new one doesn't happen.