Python by default builds the library `libpythonMAJOR.MINOR.a` and
statically links it into the interpreter. Also it has an `--enable-shared`,
(https://docs.python.org/3/using/configure.html#cmdoption-enable-shared)
flag, which will build a shared library `libpythonMAJOR.MINOR.so.1.0`, and
So after a long while I'm finally getting around to upgrading to 3.10 on
Windows from 3.9, and my first pip upgrade is causing issues with the
installation.
Problem seems to be that I run pip from a command prompt in the Scripts folder,
and it seems pip is trying to completely remove the
On Tue, Jul 19, 2022 at 03:58:41PM +0200, Antoon Pardon wrote:
I am writing a python package which has the following structure
PACKAGE
* module1.py
* module2.py
* data.cfg
However the data.cfg should be build at installation time.
Can someone give advise on which packaging tool and
I am writing a python package which has the following structure
PACKAGE
* module1.py
* module2.py
* data.cfg
However the data.cfg should be build at installation time.
Can someone give advise on which packaging tool and how
to use it, to accomplisch this.
e.g. de data config.cfg