On Sat, Dec 28, 2019 at 8:41 PM Samuel Lelièvre <samuel.lelie...@gmail.com> wrote: > > Le sam. 28 déc. 2019 à 02:12, Samuel Lelièvre: > > > > Computer, OS, build choices: > > > > - iMac, Mid 2015 > > - macOS 10.14.6 Mojave > > - build for Python 2 > > - build Sage's `gcc` and `openssl` packages > > - build Sage's Python with its `_ssl` and `_tkinter` modules > > > > Running `make testlong` gave 2 failing doctests > > in the file `src/sage/misc/sageinspect.py`. > > > > Running the tests for that file again gave 6 failing doctests. > > The key parts seem to be these: > > > ModuleNotFoundError: No module named > > '_Users_lelievre__sage_temp_Ghost_80496_tmp_2caqjln__pyx_0' > > where it seems that all "/" and "." in the path > > /Users/lelievre/.sage/temp/Ghost/etc > > became underscores. Not sure how to dig into this...
This is intentional: Note that it is says "No module named ..." as in, it is expecting that to be part of the module *name* (which for Python modules is typically derived from the filename). The modules produced by the cython() function include a mangled version of their absolute path in the module name itself to ensure that they have unique module names. Rather, it looks like it's having some other kind of problem building Cython modules. Can you confirm whether or not those examples work manually? I've had them fail before in Windows due to fork-related issues, but I don't know why it would fail on OSX. -- You received this message because you are subscribed to the Google Groups "sage-release" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-release+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/sage-release/CAOTD34aL1C7EfufF0GpJjneTKVo-30eSs_HsfDaPo8n2ztz03g%40mail.gmail.com.
