Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Import-errors on lines that don't exist at the bottom of the file instead of the top?
See original GitHub issue
Pictured is the last line of the file, L617. Note that it’s calling out an import error from the top of the file on L618 which does not exist.
I could swear this started when I was briefly experimenting with an isort atom plug-in which I’ve since uninstalled.
Any ideas?
Issue Analytics
- State:
- Created 7 years ago
- Comments:12 (8 by maintainers)
Top Results From Across the Web
6 Common CSV Import Errors and How to Fix Them - Flatfile
One of the most common CSV import errors is that the file is simply too large. That can be caused by too many...
Read more >Review and troubleshoot import errors - Knowledge Base
Below, learn how to resolve errors detected during an import, download an error file, view error details, and correct issues in your import...
Read more >Troubleshooting manual import errors - Lexia Help Center
Manual import issues and errors. I don't see an Import button! Missing columns or incorrect column names. File is not in .csv or...
Read more >beyond top level package error in relative import
The running directory is usually located in sys.path. So, all files there are importable. This is behavior since Python 2 when packages did...
Read more >Solutions to common product CSV import problems
Another possible cause is an extra quote that has been added to the file. Open the file in a text editor and find...
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 Free
Top 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
OK, the problem is here
The symbol is
fabric.api.lcdwhile the token value is justlcdI’m guessing the error in pyflakes changed and now gives the full python path instead of just the symbol.
I was wondering why this all looked so familiar… 2eb8a3f91299b9cc04e06fe4c53eb52f9217a6dc