[Bug] "No module named __future__" for py2exe builds

[Tox86]

sorry my in is very limited.

[Hrxn]

Some infos please, like OS, Python, etc..

[Tox86]

Windows 10 64bits, python=none, my batch file for download:
@echo off

set downloads=C:\Users\user\Downloads

REM ---

echo.
echo.
echo.
echo This is a batch file that will use youtube-dl to download
echo a video from a live streaming site like YouTube and others.
echo.
echo.
set /p url="Paste the URL you want to download: "

if "%url%"=="" goto no_url

REM We need double '%' to escape them.
youtube-dl.exe %url% -i -w --restrict-filenames -o "%downloads%%%(upload_date)s-%%(id)s-%%(title)s.%%(ext)s"
echo.
echo Finished!
goto end

:no_url
echo You didn't give me a URL

:end
echo ------------------------------
pause
exit

[Tox86]

Sorry test with CBS video and equal:

[Hrxn]

No Python installation? Well, that error msg says.. Okay, could be caused by py2exe, I don't know.

Please just try youtube-dl.exe -v URL from your cmd, or from a batch file, you get the idea..

[vxbinaca]

Try copying and pasting the test it's easier on the devs. Use --verbose so the problem can be examined.

[Tox86]

Ver. 2016.2.5.1 work fine.

[yan12125]

Possibly a duplicate of #2919. Do you have Cyrillic characters in the path?

[yan12125]

As reported by @danfiscus at #9529, on 64-bit systems, put youtube-dl.exe in \Windows\Systems32 causes similar errors. Can anyone try #3065 (comment)?

[Hrxn]

This one?

You can put youtube-dl into, say, C:\ytdl, and then add C:\ytdl to your PATH to be able to run youtube-dl from any directory again.

Why shouldn't this work?

[yan12125]

#3065 is a proposed solution. The one not working is \Windows\System32.

[Hrxn]

Yes...
Any subdir inside of C:\ in the PATH works, as it should.

System32 is a special directory of the OS, I would not recommend to randomly put binaries in there, etc.
So what exactly is the issue?

[yan12125]

Some people did put youtube-dl.exe in System32 and got errors. I guess @Tox86 is one of them, and I need his/her feedback before closing this issue.

[Hrxn]

Oh, okay. Sure..

Pinging @Tox86 again
😉

[mpenkov]

It's been over 2 years and still no reply from @Tox86 , it may be suitable to close this ticket.