Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.python > #27005 > unrolled thread
| Started by | Chris Angelico <rosuav@gmail.com> |
|---|---|
| First post | 2012-08-14 08:16 +1000 |
| Last post | 2012-08-14 08:16 +1000 |
| 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: Sharing code between different projects? Chris Angelico <rosuav@gmail.com> - 2012-08-14 08:16 +1000
| From | Chris Angelico <rosuav@gmail.com> |
|---|---|
| Date | 2012-08-14 08:16 +1000 |
| Subject | Re: Sharing code between different projects? |
| Message-ID | <mailman.3243.1344896191.4697.python-list@python.org> |
On Tue, Aug 14, 2012 at 2:53 AM, andrea crotti <andrea.crotti.0@gmail.com> wrote: > The problem is that there are functions/classes from many domains, so it > would not make much sense to create a real project, and the only name I > could give might be "utils or utilities".. There's actually much merit in a generic utilities module. Keep things nicely segregated (ideally such that you know what things depend on what other, but at very least keep track of where one ends and another begins - that's trivial if everything's "one function" or "one class", but less so when you have a family of related functions), and then you can consider promoting one block of code to stand-alone module. But in the meantime, you have a single module used in two places, even if it doesn't have a very clear definition as yet. ChrisA
Back to top | Article view | comp.lang.python
csiph-web