Change by Ben Boeckel :
--
nosy: +mathstuf
___
Python tracker
<https://bugs.python.org/issue28584>
___
___
Python-bugs-list mailing list
Unsubscribe:
New submission from Ben Boeckel :
Generally, the `configure.ac` script tries to detect compilers based on the
path to the compiler. This is mostly fine, but trips up when using `mpicc` as
the compiler. Even if the underlying compiler is `gcc`, this gets detected as
`icc` in various
Ben Boeckel added the comment:
We build our own applications which run Python interpreters internally, so the
auto-discovery won't work. It also doesn't seem to work for venvs either since
the venv's `python.exe` is under `Scripts` which makes it not able to find
things either on its own
New submission from Ben Boeckel :
On Windows, we are extracting a tarball of a Python installation for CI (to
avoid needing to juggle umpteen Python installs on umpteen machines). This
requires `PYTHONHOME` to be set to use properly since there is no registry
entry for the "install
Ben Boeckel added the comment:
> Presumably you looked around for ideas before figuring out the issue
Usually when "could not find foo.lib" popping up without any mention of
"foo.lib" on the link line points directly to these "autolinking" "features&qu
Ben Boeckel added the comment:
I believe this to be a clang bug. I've filed an issue with upstream here:
https://bugs.llvm.org/show_bug.cgi?id=45170
--
nosy: +mathstuf
___
Python tracker
<https://bugs.python.org/issue37
Ben Boeckel added the comment:
> The paths are not user provided: they are hardcoded paths from the sysconfig
> module:
No, those paths are the *replacement* values, not the input. From the trace
docs:
> trace.py -c -f counts --ignore-dir '$prefix' spam.py eggs
This is the str
Ben Boeckel added the comment:
`\b` is a bit too loose. That example should *not* have it replaced because it
is not a full path component.
(Granted, any of these conflicting paths are "dumb" in general; I'm fine with
just leaving this as a low priority, but if it does ge
New submission from Ben Boeckel :
Previously reported as a sidenote in Issue21016.
The `--ignore-dir` option in trace.py replaces `$prefix` and `$exec_prefix`
*anywhere* in the path when it really should just replace it in the start of
the path and if it is followed by nothing or a path
Ben Boeckel added the comment:
Thanks!
Should I file a new issue for the other (less urgent) problem mentioned at the
bottom or is it not really worth fixing?
> It also erroneously replaces things like '$prefixpath'. It should probably do
> split the path on the path separators an
Ben Boeckel added the comment:
Ah, that does look like it is suitable (since it is a shell script). I assume
it is a batch script on Windows (though I feel cross-compilation is far rarer
there). Thanks.
--
stage: -> resolved
status: open ->
New submission from Ben Boeckel :
Currently, the SOABI suffix is only available by running the Python interpreter
to ask `sysconfig` about the setting. This complicates cross compilation
because the target platform's Python may not be runnable on the build platform.
Exposing
Change by Ben Boeckel :
--
nosy: +mathstuf
___
Python tracker
<https://bugs.python.org/issue38728>
___
___
Python-bugs-list mailing list
Unsubscribe:
New submission from Ben Boeckel:
In the --ignore-dir handling of trace.py, the following is done:
s = s.replace($prefix,
os.path.join(sys.base_prefix, lib,
python + sys.version[:3]))
s
14 matches
Mail list logo
