Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.python > #32689 > unrolled thread
| Started by | Michael Schwarz <michi.schwarz@gmail.com> |
|---|---|
| First post | 2012-11-03 09:54 +0100 |
| Last post | 2012-11-03 09:54 +0100 |
| Articles | 1 — 1 participant |
Back to article view | Back to comp.lang.python
This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by
below is the oldest one visible, not the original post.
Re: How to improve the usability of nested packages Michael Schwarz <michi.schwarz@gmail.com> - 2012-11-03 09:54 +0100
| From | Michael Schwarz <michi.schwarz@gmail.com> |
|---|---|
| Date | 2012-11-03 09:54 +0100 |
| Subject | Re: How to improve the usability of nested packages |
| Message-ID | <mailman.3236.1351932911.27098.python-list@python.org> |
[Multipart message — attachments visible in raw view] — view raw
Hi Terry On 2012-W44-5, at 18:56, Terry Reedy wrote: >> or would you maybe structure the library entirely different? > > Based on my limited experience with subpackages* plus reports on this list about problems, such as yours, I have concluded that subpackages are an attractive nuisance that are generally more trouble than they are worth. I suggest you consider sticking with your original flat (no subpackage) design. (But maybe someone knows better than me how to make subpackages work ;-). One thing that I would lose is the way I can choose very short names for the packages and modules that are imported into the local namespace (like sip or rtp) and also add new stuff without fearing a namespace conflict in one of the applications using the library. I really hope there is a better way :-(. Michael
Back to top | Article view | comp.lang.python
csiph-web