8000 Remote interpreter incompatible with future.builtins (for making code 2/3 compatible) · Issue #800 · pyscripter/pyscripter · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Remote interpreter incompatible with future.builtins (for making code 2/3 compatible) #800

New issue
8000

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

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

Jump to bottom
Closed
GoogleCodeExporter opened this issue Aug 24, 2015 · 1 comment
Closed

Remote interpreter incompatible with future.builtins (for making code 2/3 compatible) #800

GoogleCodeExporter opened this issue Aug 24, 2015 · 1 comment
Labels
auto-migrated fixed

Comments

@GoogleCodeExporter
Copy link 
What steps will reproduce the problem?
1. Add the import: "from future.builtins import str" to any script
2. Run the script
3.

What is the expected output? What do you see instead?
Upon completion of execution, an error pops up which says "Error in getting the 
namespace of globals". Then, after each keystroke, an error again pops up which 
says "Error in getting the namespace of". The blank in the previous error 
message is intentional, that is the verbatim transcription of the error. 
Obviously no errors should be expected.

What version of the product are you using? On what operating system?
PyScripter 2.6.0.0 x64
Windows 7 Professional SP1

Please provide any additional information below.

Python 2.7.6
Installed from Anaconda 2.3.0 (x64)
future.__version__ 0.12.1

Removing the "..import str" and re-initializing the interpreter corrects the 
problem. Other imports from the future.builtins module do not appear to cause 
this problem. Disabling code completion in the interpreter removes the 
repeated, incomplete errors caused by keystrokes, but the first error remains.

Original issue reported on code.google.com by drwo...@gmail.com on 10 Jul 2015 at 2:38
@pyscripter
Copy link
Owner

Fixed in version control.

pyscripter added a commit that referenced this issue Sep 9, 2018
@pyscripter
Fixed #800
8a632bb
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
auto-migrated fixed
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@pyscripter @GoogleCodeExporter
0