This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author gary ruben
Recipients Deniz Bozyigit, eryksun, gary ruben, giampaolo.rodola, paul.moore, r.david.murray, steve.dower, tim.golden, zach.ware
Date 2019-02-17.11:20:42
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1550402442.44.0.106612676748.issue33935@roundup.psfhosted.org>
In-reply-to
Content
I wanted to add a datapoint to this. I also experience this problem in Windows but not with Google Drive File Stream. In my case it is also being triggered by Jupyter, which was where Deniz first noticed it, but I was saving the notebook to my Z: drive, which is a mapping of a network drive that is backed up with Windows' Sync Center; nothing to do with Google's file stream, but a standard Windows feature that triggers the same bug. For the moment, I find that Deniz's workaround lets me continue to use Jupyter in conjunction with that drive path.
History
Date User Action Args
2019-02-17 11:20:42gary rubensetrecipients: + gary ruben, paul.moore, giampaolo.rodola, tim.golden, r.david.murray, zach.ware, eryksun, steve.dower, Deniz Bozyigit
2019-02-17 11:20:42gary rubensetmessageid: <1550402442.44.0.106612676748.issue33935@roundup.psfhosted.org>
2019-02-17 11:20:42gary rubenlinkissue33935 messages
2019-02-17 11:20:42gary rubencreate