Use absolute imports
See original GitHub issueThroughout the repository, relative imports are used.
As a result, simple and useful checks for the repository are missed.
For example:
python3 -m doctest api/nvim.py
Can’t work because the internal imports are relative; however, if all the imports were refactored from
from .buffer import Buffer
# to
from pynvim.buffer import Buffer
simple checks like this would be possible.
Issue Analytics
- State:
- Created 3 years ago
- Reactions:2
- Comments:5 (5 by maintainers)
Top Results From Across the Web
Absolute vs Relative Imports in Python
An absolute import specifies the resource to be imported using its full path from the project's root folder. Syntax and Practical Examples. Let's...
Read more >Absolute and Relative Imports in Python - GeeksforGeeks
Absolute import involves a full path i.e., from the project's root folder to the desired module. An absolute import state that the resource...
Read more >Why and How to Use Absolute Imports in React
Using absolute imports to better organize your React project is a great way. Relative imports are hard to follow and break during ...
Read more >What is absolute import in python? - Stack Overflow
Relative {imports, paths, URLs} are exactly what they say they are: they're relative to their current location. That is, if the directory ...
Read more >Making Life Easier with Absolute Imports - React in Javascript ...
According to create-react-app Docs, We can use absolute imports in our react project by configuring a jsconfig.json / tsconfig.json (for ...
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
Other reviwers eye are needed.
I’m glad you agree. Are there any concerns that would stop
https://github.com/neovim/pynvim/pull/451
from being merged?