Hi Frederic and all - I installed the following patch to py-compile.
Hopefully it restores the previous behavior of setting the PYTHON envvar
to whatever and "disabling" the compilation (but exiting succesfully).
Hope it flies, let me know if problems. --thanks, karl.
Here is a revision of the patch, so that py-compile-en.sh test passes.
Here's another attempt at the patch, calling $PYTHON -V instead of using
the name of $0 to decide if it's really Python. Wdyt?
The result is that $PYTHON can be set to anything at all and py-compile
will succeed. Since the
On Sun, Nov 24, 2024 at 3:05 AM Karl Berry wrote:
> +case "$PYTHON" in
> + *python*) ;;
> + *)
> + echo "$me: Invalid python executable ${PYTHON}";
> + echo "$me: Python support disabled";
> + exit 0;;
> +esac
>
> Thanks. But I'm not sure about requiring the execu
+case "$PYTHON" in
+ *python*) ;;
+ *)
+ echo "$me: Invalid python executable ${PYTHON}";
+ echo "$me: Python support disabled";
+ exit 0;;
+esac
Thanks. But I'm not sure about requiring the executable name to include
"python". Apart from technically being against
Hi,
Here is a revision of the patch, so that py-compile-en.sh test passes.
I leave to you to decide if a test dedicated to "PYTHON=:" is truly necessary.
Fred.
-- 8< --
Subject: [PATCH v2] py-compile: Allow user to disable python
Common practice is to set PYTHON=: to disable python support, whi
There may be a bit more thoughts needed to get the py-compile-env.sh test
to work properly though.
Yes, we should add an explicit check for this PYTHON=: setting.
If you have time to munge around in the test(s), that would be great.
Else I'll get to it when I get to it. --thanks, karl.
On Tue, Nov 19, 2024 at 10:29 PM Karl Berry wrote:
> Hi Frederic,
>
> I believe this is a common practice
>
> Well, clearly no one had thought of it nor was it tried at any point
> during the lengthy automake pretest sequence, but anyway, agreed that
> there's no reason to gratuitously fail i
Hi Frederic,
I believe this is a common practice
Well, clearly no one had thought of it nor was it tried at any point
during the lengthy automake pretest sequence, but anyway, agreed that
there's no reason to gratuitously fail in this case.
As for disabling pythong, it doesn't seem to me th
Hello,
While integrating automake 1.17, I found that otf2 package build fails.
The failure is due to:
py-compile: could not determine : major version
This is a side-effect of a rework of the py-compile script, which
formerly defaulted to python3 if there was an error while getting the
pyt
