Le jeu. 2 mai 2019 à 16:20, Edwin Zimmerman a écrit :
> > ``-c COMMAND````run_module = COMMAND``
> should read "run_command = COMMAND". Typo, not?
Oops, you're right: it's a typo. Now fixed:
``-c COMMAND````run_command = COMMAND``
Victor
--
Night gather
Just an update based on testing. If I zip the modules up into python36.zip
(whether in .py or .pyc form) the linux binary does not find them. If I
copy them into the embedded root, alongside the python executable, it finds
them as expected.
This just makes it seem more like an issue where Linux
On Thursday, May 02, 2019 Victor Stinner wrote:
>
According to this
> * ``run_command`` (``wchar_t*``): ``-c COMMAND`` argument
> * ``run_filename`` (``wchar_t*``): ``python3 SCRIPT`` argument
> * ``run_module`` (``wchar_t*``): ``python3 -m MODULE`` argument
this
> ``-c COMMAND``
Hi,
Thanks to Steve Dower's feedback, I enhanced and completed my PEP 587.
Main changes:
* It is now possible to read the configuration and then modify the
read configuration. For example, new directories can be added to
PyConfig.module_search_paths (see the example below and the example in
the P
With minimal patching of tools/msi/make_zip.py, I was able to create an
equivalent zip package on Linux. It doesn't work out of the box of
course. I had to do two commands
My biggest concern is that even if the layout is "correct" on linux, the
python runtime might not actually support being run
On 2019-05-01, 06:46 GMT, Serhiy Storchaka wrote:
> These lines were added for purpose. They are needed for
> running tests in separate file as a script.
>
> $ ./python Lib/unittest/test/testmock/testcallable.py -v
> test_attributes (__main__.TestCallable) ... ok
Isn't the standard way how to run
I've successfully automated the build of the embedded zip on Windows for
3.6 on my internal CI using tools/msi script.
Moving onto linux, can you please summarize the primary
challenges/differences for creating the embeddable zip for linux?
Gerald R. Wiltse
jerrywil...@gmail.com
On Wed, May 1,
