Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.python > #20343 > unrolled thread
| Started by | mloskot <mateusz@loskot.net> |
|---|---|
| First post | 2012-02-13 03:57 -0800 |
| Last post | 2012-02-13 03:57 -0800 |
| 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: Read-only attribute in module mloskot <mateusz@loskot.net> - 2012-02-13 03:57 -0800
| From | mloskot <mateusz@loskot.net> |
|---|---|
| Date | 2012-02-13 03:57 -0800 |
| Subject | Re: Read-only attribute in module |
| Message-ID | <mailman.5758.1329134265.27778.python-list@python.org> |
Terry Reedy wrote > > On 2/10/2012 6:11 AM, mloskot wrote: >> The intent of xyz.flag is that it is a value set by the module >> internally. >> xyz is a module wrapping a C library. >> The C library defines concept of a global flag set by the C functions at >> some events, >> so user can check value of this flag. >> I can provide access to it with function: xyz.get_flag() > > If the value of the flag can change during a run, I would do that. > Otherwise, you have to make sure the local copy keeps in sync. Users > might also think that it is a true constant that they could read once. > > I understand that you might be concerned that one person in a > multi-programmer project might decide to rebind xyz.flag and mess up > everyone else. I think the real solution might be an option to freeze an > entire module. > Terry, Thanks for your really helpful notes. Best regards, ----- -- Mateusz Loskot http://mateusz.loskot.net -- View this message in context: http://python.6.n6.nabble.com/Read-only-attribute-in-module-tp4378950p4464760.html Sent from the Python - python-list mailing list archive at Nabble.com.
Back to top | Article view | comp.lang.python
csiph-web