On 2021-5-19 08:15 , Karl Berry wrote:
Hi Joshua and all - regarding https://bugs.gnu.org/35322, I have
(finally) pushed your patches. I tweaked the doc update a little bit and
created a new test to try out the --with-python_prefix and
--with-python_exec_prefix options. (I left the underscores in
Hi Joshua and all - regarding https://bugs.gnu.org/35322, I have
(finally) pushed your patches. I tweaked the doc update a little bit and
created a new test to try out the --with-python_prefix and
--with-python_exec_prefix options. (I left the underscores in the name
since I saw there were other su
OK, here's a patch to add --with-python_prefix and
--with-python_exec_prefix options. It applies on top of my previous patch.
Thanks! I think the option names would be normal with all hyphens
(e.g., the std option is --exec-prefix, not --exec_prefix), but
I'll just tweak that when I inst
On 2021-3-3 10:54 , Karl Berry wrote:
I wonder if it might also make sense to offer a configure option to set
PYTHON_PREFIX?
I think that would be great (--pythondir, --pythonexecdir or some
such). Would you mind looking into that? I've never played around with
the options Automake add
On 2021-3-6 10:26 , Karl Berry wrote:
Hi Joshua - did you run the full make check on your Mac?
I saw you patched some of the tests, which is great, so I'm guessing
you did, but just asking ...
On Jim's Mac system, many more tests (35) fail, but haven't tracked that
down yet. --thanks, karl.
I
Hi Joshua - did you run the full make check on your Mac?
I saw you patched some of the tests, which is great, so I'm guessing
you did, but just asking ...
On Jim's Mac system, many more tests (35) fail, but haven't tracked that
down yet. --thanks, karl.
I wonder if it might also make sense to offer a configure option to set
PYTHON_PREFIX?
I think that would be great (--pythondir, --pythonexecdir or some
such). Would you mind looking into that? I've never played around with
the options Automake adds and have unfortunately limited time to
On 2021-3-2 10:14 , Karl Berry wrote:
Thanks much for the patch (including fixing the tests). I don't see any
immediate comments. Jim and I will ponder for a couple days. --best, karl.
Thanks Karl. I'd certainly appreciate input from other packagers as well.
I wonder if it might also make sens
Hi Joshua,
How about this? It bases the default values of PYTHON_PREFIX and
PYTHON_EXEC_PREFIX on sys.prefix and sys.exec_prefix respectively, ...
Thanks much for the patch (including fixing the tests). I don't see any
immediate comments. Jim and I will ponder for a couple days. --best,
How about this? It bases the default values of PYTHON_PREFIX and
PYTHON_EXEC_PREFIX on sys.prefix and sys.exec_prefix respectively, which
the documentation has long said might happen. Behaviour should not
change in the case that sys.prefix = $prefix. The variables can still be
overridden; e.g.
Thanks for the follow-up.
a question of whether the goal is installing modules in a consistent
location across different systems, or installing them somewhere
where the python on this system will be able to find them.
Yes. Ordinarily, install directories in Automake are supposed to be
On 2021-2-15 09:16 , Karl Berry wrote:
Unfortunately, simply removing the change to the `base' assignment as
you did in your change, for instance the first hunk,
-sitedir = sysconfig.get_path('purelib', vars={'base':'$am_py_prefix'})
+sitedir = sysconfig.get_path('purelib')
will affect
Hi - thanks for this report from almost two years ago (sorry).
https://debbugs.gnu.org/cgi/bugreport.cgi?bug=35322
On macOS, if CPython is configured with --enable-framework (default
for MacPorts [1]), Python packages should be installed in ...
Ok.
Here's a minimal example configure.
Hi Automake experts,
On macOS, if CPython is configured with --enable-framework (default
for MacPorts [1]), Python packages should be installed in
${prefix}/Library/Frameworks/Python.framework/Versions/3.7/lib/python3.7/site-packages.
However, AM_PATH_PYTHON gives
pythondir=${prefix}/lib/python3.7
14 matches
Mail list logo
