#beets

https://www.reddit.com/r/linux/comments/4hivcb/... <- beets love

lazka, i liked thed cleanups for the mutagen errors, but is that gonna fly with the various mutagen versions packaged in different distros?

excluding rhel/centos 6 of course

jrobeson, as I noted in the commit message I tested with both 1.27 and master

1.27 being the oldest supported by beets

ah ok.. i guess i didn't get that

so can you fix the flake8 bit then?

I think I did

i didn't get a notification, and i thought github did that now, but mabye it's not rolled out to everybody yet

yay

feedback to the mutagen changes welcome.. I haven't done a release with these changes

i don't know the codebase well enough to comment

i'm just glad that you're fixing a python3 test for me :)

jrobeson, I think I pushed a minute before you posted there

i just don't like being annoying if i can avoid it .. except to sampsyo

jrobeson, I mean feedback for the changes from a user POV

which user?

you ;)

consumer of mutagen or consumer of beets?

can you be a little more precise?

jrobeson, the next mutagen release breaks some beets tests, thus the pull request. If you think any of the mutagen changes are wrong/counterproductive -> please complain.

With 1.3.19 I'm having trouble with permissions plugin. Somehow what once was working is broken.

When I import stuff beets finds them. Matches them. Tries to import them and at the last step it starts throwing out errors like this: http://paste.ee/r/l4gDv

do you actually have the permission plugin enabled?

does it work without it?

Also, the imported files and folders become inaccessible due to incorrect permissions. Even though I have 755 and 644 set up in the config.

Now, I disabled and it works jrobeson

ok, file a bug then

But I had to relocate my whole 600+gb to find out which folders weren't actually imported during my previous import. Because it didn't register some of those to database as well.

i have my own problems with the permission handling in beets

i kinda don't think that the permissions plugin should be a plugin .. or at least not one you have to enable at all

Well, may be. You should at least specify user name to write the files with . Or maybe for those who're in need of specific permissions it should be useful.

I'm submitting a bug.

lazka, you mentioned that you tested it against those mutagen versions, but i think that should be in the PR message

that is, just put most of mediafile: Cleanup mutagen error handling message in the PR message

hm, ok

if i wanted you to do even more work, I'd make you split out the alac detetion thing into it's own PR, but sampsyo won't make you do that :)

so you don't have to worry about that

I thought of it more as a patch series

I'll split things up later, but busy right now

I wouldn' tworry about it since sampsyo won't make you do it it :)

i am happy to see that hack gone, i was gonna get around to it, but py3 stuff was more important

that alac hack i mean

I have one more issue. Whenever I run beet mv, I always have some files that tries to move themselves to the same folder they are in. This might be related to my renaming syntax (my config is on the upper link as well) but even if I run beet mv 10 times in a row, right now I see the same 200 files at each run.

file that one too

Is there a way to let beets import the higher quality version of an existing album in quiet mode? (If possible a it can replace existing tracks in order to avoid track loss on a higher quality version with missing tracks) :P

well that simplifies things :)

sampsyo, the channel message (which I can't remember how to change) still points to radbox

jrobeson: Huh -- the one when you join #beets? I also don't remember how to change that. :)

I think the person (rawsted?) who set up the channel set it up and I never thought about it again.

howdy sampsyo

Yo!

glad somebody was able to figure out that issue!

Yeah, that was truly crazy.

i tried getting help on #python. and got down to debugging the locking, but hten the person had to go

comparing the python source though was a good idea :)

Absolutely.

so what's the top 3 items on your todo list? sorted by priority ?

Do you mean about py3, beets in general, or just my whole life? :)

let's stick with beets

Well, in the category of near-term things, py3 and the modularization have bubbled up to the top lately because we have momentum

And the third is probably an AURA implementation, which is long overdue

so, how what did you wanna do for py3?

Getting a minimally working `beet version` or whatever on Python 3 would be awesome to do in the near term

And then we can grind away at the details one by one

hmm? you mean the command beet version?

that's old news

i got all the way to the importer screen

where it gave me choices .. and tried every option but Apply

Huh, I'm still getting `sys.stdout.write argument bust be str, not bytes`

well it's been a fewe weeks

yeah, you need to help me out with what to do with the stdio!

that junk PR i have

i mean junk commit

Ah, right -- I guess what I meant in terms of priorities was getting your current patch queue transitioned onto master

So we get the same level of py3 usability you're currently seeing in a 2/3 way

(even if that's not complete)

so how do we do that? :)

Good question! Do you have that link to the compare view again?

1 moment

I guess one place to start with `print_` would be to use `if PY2` to encode to bytes manually, and on py3 use the Unicode string directly.

that one is too easy .. that's why i didn't bother doing it

basically taking the three changes you have here and putting them behind a version check: https://github.com/beetbox/beets/commit/72520f8...

Easy but effective? Perhaps!

thanks

i just wanted to remove one skipped PR cuz of lazka !

i mean one skipped test commit

then i ran the tests , and it passed, so!

Woohoo!

i just didn't wanna make those kind of decisions, so you can do what you think is best.

Would you mind opening a PR with those changes to ui/__init__.py and I'll take it from there?

if you ignore windows, getattr(sys.stdout, "buffer", sys.stdout).write(b"bytes")