Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.python > #12906
| From | Peter Otten <__peter__@web.de> |
|---|---|
| Subject | Re: How to structure packages |
| Date | 2011-09-07 19:30 +0200 |
| Organization | None |
| References | <2a4f542c-a8c1-46c7-9899-a3fad0940cf6@x11g2000yqc.googlegroups.com> |
| Newsgroups | comp.lang.python |
| Message-ID | <mailman.842.1315416661.27778.python-list@python.org> (permalink) |
bclark76 wrote:
> I'm learning python, and was playing with structuring packages.
If you are coming from Jave you have to unlearn a thing or two.
> Basically I want to have a package called mypackage that defines a
> number of classes and functions.
> I'm trying to follow the rule that every file defines only one class.
> I could define MyClass in __init__.py, but then what if I wanted to
> define more classes in the mypackage package? My one class per file
> rule goes out the window.
>
> Is this rule wrongheaded,
Yes.
> or is there another way to do this?
I recommend that you always start out with a module. Once that becomes
unwieldy you can convert it into a package. Let's assume that
mystuff.py
contains a MyClass that you want to move into a separate file. You get the
following files:
mystuff
__init__.py
descriptivename.py # MyClass here
Note that all filenames are lowercase. If you add the line
from .descriptivename import MyClass
to __init__.py you can continue to import and use MyClass with the statement
from mystuff import MyClass
m = MyClass()
or
import mystuff
m = mystuff.MyClass()
The disadvantage is of course that mystuff.descriptivename will always be
imported, even if you don't need the part of the mystuff package defined
there.
You may also have a look into unittest as an example of a module that was
recently converted into a package. Classes and functions are grouped into
submodules by their functionality rather than employing Java's mechanical
one-class-per-file pattern.
Back to comp.lang.python | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
How to structure packages bclark76 <bclark76@gmail.com> - 2011-09-07 08:56 -0700
Re: How to structure packages John Gordon <gordon@panix.com> - 2011-09-07 16:11 +0000
Re: How to structure packages Rafael Durán Castañeda <rafadurancastaneda@gmail.com> - 2011-09-07 19:18 +0200
Re: How to structure packages Peter Otten <__peter__@web.de> - 2011-09-07 19:30 +0200
Re: How to structure packages Steven D'Aprano <steve+comp.lang.python@pearwood.info> - 2011-09-08 10:29 +1000
Re: How to structure packages Chris Angelico <rosuav@gmail.com> - 2011-09-08 12:39 +1000
Re: How to structure packages Dan Sommers <dan@tombstonezero.net> - 2011-09-08 09:51 +0000
Re: How to structure packages Jonathan Hartley <tartley@tartley.com> - 2011-09-08 03:22 -0700
Re: How to structure packages Nobody <nobody@nowhere.com> - 2011-09-09 01:45 +0100
Re: How to structure packages Chris Angelico <rosuav@gmail.com> - 2011-09-09 11:37 +1000
Re: How to structure packages Nobody <nobody@nowhere.com> - 2011-09-10 11:11 +0100
Re: How to structure packages Chris Angelico <rosuav@gmail.com> - 2011-09-10 20:29 +1000
Re: How to structure packages "Littlefield, Tyler" <tyler@tysdomain.com> - 2011-09-10 08:04 -0600
Re: How to structure packages Alec Taylor <alec.taylor6@gmail.com> - 2011-09-10 02:38 +1000
Re: How to structure packages rantingrick <rantingrick@gmail.com> - 2011-09-07 10:56 -0700
Re: How to structure packages "Littlefield, Tyler" <tyler@tysdomain.com> - 2011-09-07 12:11 -0600
Re: How to structure packages Westley Martínez <anikom15@gmail.com> - 2011-09-07 14:35 -0700
csiph-web