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 skrah
Recipients ezio.melotti, pitrou, serhiy.storchaka, skrah, vstinner
Date 2015-08-10.10:14:07
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1439201648.17.0.961818757449.issue24831@psf.upfronthosting.co.za>
In-reply-to
Content
Yes, the current scheme is probably good for easy buildbot cleanup.


> Maybe we can blacklist some filesystems to choose the temporary directory.

If that's easily possible, it would be a good solution at least
for ecryptfs.


I've removed ecryptfs from my setup, since speedwise it's not
production-ready for encrypting an entire home directory.


The Ubuntu setup is a bit of a trap, since the encryption is
completely transparent to the user (i.e. mounting ecryptfs
occurs automatically on login).

So if you install Ubuntu as the first system on new hardware
and choose the ecryptfs option, after a while you forget about
ecryptfs entirely and blame any slowness on the hardware or
the software.
History
Date User Action Args
2015-08-10 10:14:08skrahsetrecipients: + skrah, pitrou, vstinner, ezio.melotti, serhiy.storchaka
2015-08-10 10:14:08skrahsetmessageid: <1439201648.17.0.961818757449.issue24831@psf.upfronthosting.co.za>
2015-08-10 10:14:08skrahlinkissue24831 messages
2015-08-10 10:14:07skrahcreate