[issue28949] Stdlib modules disappear from file system

Jason R. Coombs added the comment: Throughout the week, I've not experienced this issue again. Perhaps the reinstall of Dropbox corrected some transient condition. Or perhaps my system was in some environment where it was particularly sensitive on Monday but has since returned to the status

[issue28949] Stdlib modules disappear from file system

Jason R. Coombs added the comment: I paused the Dropbox sync and ran the `rm -R .tox; tox` routine many times without incident, which strongly implicates Dropbox. I'm going to now re-enable Dropbox sync and see if I can trigger the behavior. Now even with Dropbox updated back to the latest

[issue28949] Stdlib modules disappear from file system

Ned Deily added the comment: Thanks. I'm still interested in the outcome but my immediate concern was whether this was a showstopper problem for 3.6.0. Good luck! -- nosy: +ned.deily ___ Python tracker

[issue28949] Stdlib modules disappear from file system

Changes by Jason R. Coombs : -- nosy: -ned.deily ___ Python tracker ___ ___

[issue28949] Stdlib modules disappear from file system

Jason R. Coombs added the comment: > virtualenvs and not venvs? Correct. > In any case, at this point it seems pretty clear that we're not dealing with > a problem with Python 3.6.0 nor with the python.org installer, no? Also correct. If you don't mind, I'd like to continue to document and

[issue28949] Stdlib modules disappear from file system

Changes by Jason R. Coombs : -- versions: -Python 3.6 ___ Python tracker ___ ___

[issue28949] Stdlib modules disappear from file system

Jason R. Coombs added the comment: This morning, I noticed my Mercurial install isn't working either - failing with this error message: $ hg pull abort: couldn't find mercurial libraries in [/usr/local/Cellar/mercurial/4.0.1/lib/python2.7/site-packages /usr/local/Cellar/mercurial/4.0.1/bin

[issue28949] Stdlib modules disappear from file system

Ned Deily added the comment: Have you verified that the problem no longer occurs if the virtualenvs are not in a Dropbox directory? (And these are virtualenvs, not venvs?) In any case, at this point it seems pretty clear that we're not dealing with a problem with Python 3.6.0 nor with the

[issue28949] Stdlib modules disappear from file system

Jason R. Coombs added the comment: I'm getting good at reinstalling Python, though. Now I'm invoking it with this single command-line: sudo installer -verboseR -pkg ~/Downloads/python-3.6.0rc1-macosx10.6.pkg -target / -- ___ Python tracker

[issue28949] Stdlib modules disappear from file system

Jason R. Coombs added the comment: Downgrading Dropbox did not help. This morning I woke up to `importlib.abc` missing. -- ___ Python tracker ___

[issue28949] Stdlib modules disappear from file system

Jason R. Coombs added the comment: I've reinstalled Dropbox, downgrading to 15.4.22. I'll see if that helps. -- ___ Python tracker ___

[issue28949] Stdlib modules disappear from file system

Jason R. Coombs added the comment: I don't think hard links are involved. I see symlinks in the .tox/python virutalenv, and virtualenv defaults to creating symlinks (https://github.com/pypa/virtualenv/blob/master/virtualenv.py#L565-L570) and falls back to copying files rather than hard

[issue28949] Stdlib modules disappear from file system

Ned Deily added the comment: That's sounding better, thanks. Out of curiosity, are there hard links involved? -- ___ Python tracker ___

[issue28949] Stdlib modules disappear from file system

Jason R. Coombs added the comment: I've just encountered what appears to be a different manifestation of the same issue. I unlinked the .tox directory and that rendered importlib broken. $ pwd /Users/jaraco/yg/queso $ rm -R .tox $ python Python 3.6.0rc1 (v3.6.0rc1:29a273eee9a5, Dec 6 2016,