Replace absolute imports with relative imports

I’d like to use 2.0 in a project of mine, but I rely on some packages that don’t yet support it, so my intent is to temporarily bundle prompt_toolkit as a subpackage until these issues clear themselves up. When trying to do this, I discovered many absolute imports that could/should be rewritten as package-relative, e.g. in application.py.

Would you be willing to accept a PR that replaces the absolute imports of prompt_toolkit.x with relative imports? I’d stick to the library code and wouldn’t touch examples/tests/etc.

[natezb]

While I’d argue that using relative imports is the “correct” thing to do, I agree with you that it seems other large, well-established projects are getting along fine with absolute imports.

I also agree that adding docs/scripts concerning vendoring would be valuable, as I can’t imagine I’m the only person who will run into this issue with the 1.0/2.0 split.

When I get the chance I can play around with that one-liner and let you know what tweaks need to be made, if any.

[alejandrogallo]

I’m glad I found this, since I intend to do the same with my project, I too intend to do it this way by replacing all from ... with my package namespace. I hope in the future this is not broken too much @jonathanslenders , if you could have in mind people like us when you further develop that’d be great! Thanks for your great lib!