I get a error in the stardard module "os" (I use Python 3.5.1 64bit for Windows 10!)
What is wrong and have someone a patch
See the "os-bug.PNG"-file.

The "yield from" syntax was added in Python 3.3, so somehow you're using the 3.5 standard library with either an old 3.x or 2.x version. The older version shouldn't use 3.5's standard library, unless you have either PYTHONHOME or PYTHONPATH defined. Generally neither of these variables should be defined, especially not PYTHONHOME. In the command prompt run "set PYTHON" to list all environment variables that start with "PYTHON".

You also appear to be running with the 3.5 site-packages as the working directory. Even without the other problems, I recommend against this since the current directory has precedence in sys.path. You're moving site-packages to the head of the list, in front of the standard library. For example:

    C:\Program Files\Python35\Lib\site-packages>type subprocess.py
    print("This isn't the subprocess you're looking for.")

    C:\Program Files\Python35\Lib\site-packages>py -3 -c "import subprocess"
    This isn't the subprocess you're looking for.

Save your scripts in the top-level Scripts directory or a directory in your user profile. Generally leave everything under Lib alone, to be managed by pip and other installers.

I thank you much for thisse answer!
I Python is in "C:\Python35\" in the root of C-Drive (OS)
=-O
Den 11-01-2016 kl. 23:57 skrev Eryk Sun:
> Eryk Sun added the comment:
>
> The "yield from" syntax was added in Python 3.3, so somehow you're using the 3.5 standard library with either an old 3.x or 2.x version. The older version shouldn't use 3.5's standard library, unless you have either PYTHONHOME or PYTHONPATH defined. Generally neither of these variables should be defined, especially not PYTHONHOME. In the command prompt run "set PYTHON" to list all environment variables that start with "PYTHON".
>
> You also appear to be running with the 3.5 site-packages as the working directory. Even without the other problems, I recommend against this since the current directory has precedence in sys.path. You're moving site-packages to the head of the list, in front of the standard library. For example:
>
>      C:\Program Files\Python35\Lib\site-packages>type subprocess.py
>      print("This isn't the subprocess you're looking for.")
>
>      C:\Program Files\Python35\Lib\site-packages>py -3 -c "import subprocess"
>      This isn't the subprocess you're looking for.
>
> Save your scripts in the top-level Scripts directory or a directory in your user profile. Generally leave everything under Lib alone, to be managed by pip and other installers.
>
> ----------
> nosy: +eryksun
>
> _______________________________________
> Python tracker <report@bugs.python.org>
> <http://bugs.python.org/issue26086>
> _______________________________________
>

Hana, when responding, please delete the quoted previous message.  On the web page, your response directly follows that messages, so the quotation is redundant and annoying.

Please write and either copy into a message or upload a **minimum** program that shows the error -- one that we can quickly read and test.  Also copy the first line that appears in an interactive shell, the one that looks like "Python 3.5.1 (v3.5.1:37a07cee5969, Dec  6 2015, 01:54:25) [MSC v.1900 64 bit (AMD64)] on win32"

I don't see any conclusive evidence that this is a bug in the Python interpreter, so I'm going to close the issue.

Hana, if you are still having this problem, please join the main python mailing list https://mail.python.org/mailman/listinfo/python-list or newsgroup comp.lang.python, and we should be able to help you there. (But please don't post screen shots, copy and paste the text of the exception into your message.)