From e9cfae9369fd628a1ca0679785ce025ec6b87163 Mon Sep 17 00:00:00 2001 From: "nath@laptop" Date: Fri, 1 Jan 2016 12:17:12 +0100 Subject: [PATCH] play: Document #1785 --- docs/changelog.rst | 10 ++++++++++ docs/plugins/play.rst | 14 ++++++++++++++ 2 files changed, 24 insertions(+) diff --git a/docs/changelog.rst b/docs/changelog.rst index e9c2befe9..50699cadd 100644 --- a/docs/changelog.rst +++ b/docs/changelog.rst @@ -14,6 +14,16 @@ New: .. _AcousticBrainz: http://acousticbrainz.org/ +Fixes: + +* :doc:`/plugins/play`: Remove dead code. From this point on, beets isn't + supposed and won't try to delete the playlists generated by ``beet play`` + (Note that although it was supposed to, beet didn't actually remove the + generated ``.m3u`` files beforehand either.). If this is an issue for you, you + might want to take a look at the ``raw`` config option of the + :doc:`/plugins/play`. :bug:`1785`, :bug:`1600` + + 1.3.16 (December 28, 2015) -------------------------- diff --git a/docs/plugins/play.rst b/docs/plugins/play.rst index 9a7210b4e..5092ce846 100644 --- a/docs/plugins/play.rst +++ b/docs/plugins/play.rst @@ -82,3 +82,17 @@ example:: indicates that you need to insert extra arguments before specifying the playlist. + +Note on the Leakage of the Generated Playlists +_______________________________________________ + +Because the command that will open the generated ``.m3u`` files can be +arbitrarily configured by the user, beets won't try to delete those files. For +this reason, using this plugin will leave one or several playlist(s) in the +directory selected to create temporary files (Most likely ``/tmp/`` on Unix-like +systems. See `tempfile.tempdir`_.). Leaking those playlists until they are +externally wiped could be an issue for privacy or storage reasons. If this is +the case for you, you might want to use the ``raw`` config option described +above. + +.. _tempfile.tempdir: https://docs.python.org/2/library/tempfile.html#tempfile.tempdir