-
Notifications
You must be signed in to change notification settings - Fork 1.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unicode error in new atomic move #4168
Comments
Thank you for filing! Is there any chance that traceback got cut off at the end? It doesn't seem to end in the line that's the origin of the second exception. |
Same issue here: The error im getting is always the same except for the name of the file that causes the error:
Here is my congif.yaml: I don't have enough knowledge of python to be able to figure this out on my own, any help is truly appreciated. thanks in advance to anyone who can help. |
Thanks for the complete traceback; this definitely looks like a bug! @catap, this bug was introduced in your PR #4060. The concatenation here assumes incorrectly that Can you please take a look? |
`os.path.basename` returns the same type that was used. So, I have no guarantee that I needed here: `b'.''` or `'.'`. Let use something universal ;) Closes beetbox#4168
Fixes #4168. Also closes #4192, which it supersedes. The original problem is that this implementation used bytestrings incorrectly to invoke `mktemp`. However, `mktemp` is deprecated, so this PR just avoids it altogether. Fortunately, the non-deprecated APIs in `tempfile` support all-bytes arguments.
Hi, Sorry to comment on this old thread but I am getthing same error while trying to run
Below stacktrace is after i tried windows mklink thinking it might bypass it, but still giving same error. "The system cannot move the file to a different disk drive"
|
@krpradeep unfortunately but the fix isn’t released at any version yet. Hopefully the next release will be soon, see: #4501 |
@catap Thanks for reply. I able to work it out by manually merging change into local |
Problem
I’ve stumbled upon a bug when importing any file, seemingly related to the use of the
os.replace
function and theimport: move
option. using the copy option instead fixes the bug. According to adrian, it would be related to Introduce atomic move and write of fileSetup
The relevant bit of my configuration (output of
beet config
) is:The text was updated successfully, but these errors were encountered: