On Sat, May 19, 2018 at 3:27 AM, bartc <b...@freeuk.com> wrote: > On 18/05/2018 15:47, Chris Angelico wrote: >> >> On Sat, May 19, 2018 at 12:37 AM, bartc <b...@freeuk.com> wrote: >>> >>> Have a look at some of the implementations here (to test some Mandelbrot >>> benchmark): >>> >>> >>> https://benchmarksgame-team.pages.debian.net/benchmarksgame/performance/mandelbrot.html >>> >>> The three Python examples all use 'import sys' and 'import >>> multiprocessing', >>> none of which I can find any trace of as any sort of files let alone .py. >>> One of them also uses 'import array', which I can't find either. >> >> >> I guess you didn't look very hard. >> >>>>> import multiprocessing >>>>> multiprocessing.__file__ >> >> '/usr/local/lib/python3.8/multiprocessing/__init__.py' > > > But you have to load it first to find out. (And if you follow nested > imports, you will eventually get to those that don't have a .py file.)
... so? > However, if I load sys, multiprocessing and array, then print sys.modules, I > get a very long list of modules, at which point anyone thinking of emulating > the behaviour of those modules would promptly give up. Once again, you're confusing *porting* with *emulating*. If you don't understand the difference between those two concepts, I recommend spending some time with Wikipedia. ChrisA -- https://mail.python.org/mailman/listinfo/python-list
