kxroberto <kxrobe...@users.sourceforge.net> added the comment:
its with any .pyx (Cython) module , when after pyximport.install() and
injection of --inplace option a .pyx module is imported.
the relevant lines in pyxbuild.py are
dist.run_commands()
return dist.get_command_obj("build_ext").get_outputs()[0]
which use the buggy "get_outputs" and shall return the full path of
built module to pyximport.py :
so_path = pyxbuild.pyx_to_dll(pyxfilename, extension_mod,
build_in_temp=build_in_temp,
pyxbuild_dir=pyxbuild_dir,
setup_args=sargs )
assert os.path.exists(so_path), "Cannot find: %s" % so_path
=> crash with "Cannot find..." before pyximport.load_module goes to
import it.
-
A stripped down test case should perhaps 'build_ext' any arbitrary
extension module with --inplace ( a option of base command 'build' ) and
something like ...
dist.get_command_obj("build_ext").inplace=1
dist.run_commands()
so_path = dist.get_command_obj("build_ext").get_outputs()[0]
assert os.path.isfile(so_path) and os.path.dirname(so_path) in ('','.')
... will produce a invalid so_path: not pointing to actual locally
in-place built xy.pyd/.so, but to a non-existing or old file in the
build folders
----------
_______________________________________
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/issue5977>
_______________________________________
_______________________________________________
Python-bugs-list mailing list
Unsubscribe:
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
