Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.python > #21994 > unrolled thread
| Started by | Rod Person <rodperson@rodperson.com> |
|---|---|
| First post | 2012-03-21 13:10 -0400 |
| Last post | 2012-03-21 13:10 -0400 |
| 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: class checking its own module for an attribute Rod Person <rodperson@rodperson.com> - 2012-03-21 13:10 -0400
| From | Rod Person <rodperson@rodperson.com> |
|---|---|
| Date | 2012-03-21 13:10 -0400 |
| Subject | Re: class checking its own module for an attribute |
| Message-ID | <mailman.867.1332349843.3037.python-list@python.org> |
On Wed, 21 Mar 2012 17:59:56 +0100 Peter Otten <__peter__@web.de> wrote: > Rod Person wrote: > > > We have a module called constants.py, which contains [whatever] > > related to server names, databases, service account users and their > > passwords. > > Passwords? > Yes, not the best thing, but they are only service account that run nightly batch jobs. Everyone in our IT department knows these password and users. I only deploy the .pyo or .pyc files for this module, although I'm looking into a better way than that. -- Rod Person http://www.rodperson.com rodperson@rodperson.com 'Silence is a fence around wisdom'
Back to top | Article view | comp.lang.python
csiph-web