Hi, Chris.
They are "builtin" module.
python executable contains the modules already.
But I don't know it's safe to remove them from setup.py.
There are so many platforms and special build of Python.
$ ./python
Python 3.7.0a0 (default:9f7d16266928, Jan 18 2017, 23:59:22)
[GCC 6.2.0 20161005] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import sys
>>> sys.builtin_module_names
('_ast', '_codecs', '_collections', '_functools', '_imp', '_io',
'_locale', '_operator', '_signal', '_sre', '_stat', '_string',
'_symtable', '_thread', '_tracemalloc', '_warnings', '_weakref',
'atexit', 'builtins', 'errno', 'faulthandler', 'gc', 'itertools',
'marshal', 'posix', 'pwd', 'sys', 'time', 'xxsubtype', 'zipimport')
On Fri, Jan 20, 2017 at 3:21 AM, Chris Angelico <ros...@gmail.com> wrote:
> I don't think I've ever seen this message before. This is just after
> 'hg pull -u' to get to the latest CPython (my previous build was about
> a month ago). 'make' succeeded, but concluded with this message:
>
> running build_ext
> The following modules found by detect_modules() in setup.py, have been
> built by the Makefile instead, as configured by the Setup files:
> atexit pwd time
>
> And then proceeded to run build_scripts as normal.
>
> It doesn't look like an error, and those three modules can happily be
> imported by "./python" and by the freshly-installed "python3.7". It's
> curious though. Any explanation?
>
> ChrisA
> --
> https://mail.python.org/mailman/listinfo/python-list
--
https://mail.python.org/mailman/listinfo/python-list
