Backup_Repos/beets
1
0
Fork 0
mirror of https://github.com/beetbox/beets.git synced 2025-12-28 11:32:30 +01:00
Code Issues Projects Releases Wiki Activity

play: Document #1785

Browse source
This commit is contained in:
nath@laptop 2016-01-01 12:17:12 +01:00
parent b0c94f4f47
commit e9cfae9369
2 changed files with 24 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

10
docs/changelog.rst
View file

@ -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)
--------------------------

14
docs/plugins/play.rst
View file

@ -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