Rationale for importing os.path as _path in cfclient?

Firmware/software/electronics/mechanics
Post Reply
mablem8
Beginner
Posts: 3
Joined: Fri Apr 17, 2015 1:57 am

Rationale for importing os.path as _path in cfclient?

Post by mablem8 » Tue Apr 28, 2015 1:50 pm

From what I've read, importing a module as some name is useful to deconflict different modules with matching names. In the cfclient file (located in /bin of the GitHub release), os.path is imported as _path (line 7). Is there a reason that this method is used as opposed to "from os import path"? docs.python.org/2.0/ref/import.html discourages "import module.submod as s" (5th paragraph).



Post Reply