Python 3 raises a NameError because of file builtin
See original GitHub issueHello, I am using pydot2==1.0.33
with Python 3.4. It seems that the pydot.Dot.write_png
does not work with Python 3 because of the file
builtin, removed in Python 3, causing a NameError
.
Issue Analytics
- State:
- Created 8 years ago
- Comments:10 (6 by maintainers)
Top Results From Across the Web
Built-in Exceptions — Python 3.11.1 documentation
Setting __cause__ also implicitly sets the __suppress_context__ attribute to True , so that using raise new_exc from None effectively replaces the old exception ......
Read more >Handling NameError Exception in Python - GeeksforGeeks
General causes for NameError being raised are : 1. Misspelled built-in functions: In the below example code, the print statement is misspelled ...
Read more >python NameError: name 'file' is not defined - Stack Overflow
It seems that your project is written in Python < 3. This is because the file() builtin function is removed in Python 3....
Read more >How NameError Works in Python with Examples - eduCBA
NameError is a kind of error in python that occurs when executing a function, variable, library or string without quotes that have been...
Read more >Error Types in Python - TutorialsTeacher
In Python 3.x, print is a built-in function and requires parentheses. The statement above violates this usage and hence syntax error is displayed....
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
nlhelper_master
here, or the fork’s repository, orpip install pydotplus
.Ok thanks I will test your repository. Out of curiosity, why not fixing this repository instead of creating another package? Indeed it seems no commits have been done since 2012, pull requests and issues do not seem to get much attention.