Re: [Tutor] Import vs #include

2009-09-18 Thread Kent Johnson
On Fri, Sep 18, 2009 at 4:15 PM, Warren Marshall wrote: > > Excellent, OK, this is becoming clearer ... > > So if I wanted a common library of code that several Python apps would be > using, best practices would say I should put that into a directory that the > projects can see and import it as a

Re: [Tutor] Import vs #include

2009-09-18 Thread Warren Marshall
Excellent, OK, this is becoming clearer ... So if I wanted a common library of code that several Python apps would be using, best practices would say I should put that into a directory that the projects can see and import it as a package.module. Cool... - Warren (epic...@gmail.com) On

Re: [Tutor] Import vs #include

2009-09-18 Thread Kent Johnson
On Fri, Sep 18, 2009 at 2:14 PM, Warren Marshall wrote: > > I'm trying to get my head around the organization of a larger Python > project. > > 1. Am I right in thinking that in Python, you don't have the concept of > something like a precompiled header and that every file that wants to use, > say

[Tutor] Import vs #include

2009-09-18 Thread Warren Marshall
I'm trying to get my head around the organization of a larger Python project. 1. Am I right in thinking that in Python, you don't have the concept of something like a precompiled header and that every file that wants to use, say "vector.py" needs to import that module? 2. How are Python