Timeline for Python Import Submodule Prefix
Current License: CC BY-SA 3.0
4 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Feb 4, 2017 at 23:31 | vote | accept | Community Bot | ||
| Feb 4, 2017 at 22:37 | comment | added | user6767685 | It's mostly to be explicit. Regarding relative imports, I've heard arguments against them. Is there another way I can structure my code to avoid this? | |
| Feb 4, 2017 at 22:34 | comment | added | will | it might be unnecessary, but perhaps it's either there so that the code's style is consistent, or perhaps it's so that a future change to the imported class doesn't break the code that's using it? | |
| Feb 4, 2017 at 22:29 | history | answered | Moses Koledoye | CC BY-SA 3.0 |