Alberto <agarciaill...@gmail.com> added the comment: Hi,
First of all thank you for your answer. If every module can't be statically compiled within a library, what is the point of having instructions to compile python statically in the build instructions? Can I modify the code to make it completely statically? Thank you On Fri, Jul 6, 2018 at 12:27 AM STINNER Victor <rep...@bugs.python.org> wrote: > > STINNER Victor <vstin...@redhat.com> added the comment: > > > Why is Python looking for external modules when it is a statically > linked library and encodings should be built-in? > > Hi, this is not a bug. Python needs its standard library. You might want > to put the whole stdlib into a single ZIP, but I don't recall how to do > that. > > The encodings and codecs modules are not built-in, but _codecs is built-in: > > >>> import encodings, codecs, _codecs > >>> encodings > <module 'encodings' from '/usr/lib64/python3.6/encodings/__init__.py'> > >>> codecs > <module 'codecs' from '/usr/lib64/python3.6/codecs.py'> > >>> _codecs > <module '_codecs' (built-in)> > > I suggest to close this issue as "not a bug". You should ask on a Python > mailing list or forum to get help how to build a standalone Python. > > ---------- > > _______________________________________ > Python tracker <rep...@bugs.python.org> > <https://bugs.python.org/issue34057> > _______________________________________ > -- Alberto García Illera GPG Public Key: https://goo.gl/twKUUv ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <https://bugs.python.org/issue34057> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
