On 06-08-11 01:38, Emile van Sebille wrote:
On 8/5/2011 4:22 PM Tim Johnson said...
* Christopher King [110805 12:03]:
To make a package, you make a folder named what you want to name the
package, for example: virus_toolkit. Then you make a file in it called
__init__.py. This is what you impor
* Emile van Sebille [110805 15:51]:
> On 8/5/2011 4:22 PM Tim Johnson said...
> >* Christopher King [110805 12:03]:
> >>To make a package, you make a folder named what you want to name the
> >>package, for example: virus_toolkit. Then you make a file in it called
> >>__init__.py. This is what you
On 8/5/2011 4:22 PM Tim Johnson said...
* Christopher King [110805 12:03]:
To make a package, you make a folder named what you want to name the
package, for example: virus_toolkit. Then you make a file in it called
__init__.py. This is what you import if you import the virus_toolkit. You
usuall
* Christopher King [110805 12:03]:
> To make a package, you make a folder named what you want to name the
> package, for example: virus_toolkit. Then you make a file in it called
> __init__.py. This is what you import if you import the virus_toolkit. You
> usually put documentation and general fun
To make a package, you make a folder named what you want to name the
package, for example: virus_toolkit. Then you make a file in it called
__init__.py. This is what you import if you import the virus_toolkit. You
usually put documentation and general functions in this I believe (I'm not
100% sure
I'm been coding in python now for close to 10 years. one of the
modules that I have composed for re-use has gotten pretty big:
It is implemented as
import tlib as std
I am thinking about 'downsizing' this module and breaking it up into
smaller components, thus a package. And I would like to do
