Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.python > #20158
| Date | 2012-02-10 03:11 -0800 |
|---|---|
| From | mloskot <mateusz@loskot.net> |
| References | <CABUeae_vv=THd0VLsAteEKu7z8U2KA4p+vK1a=nAeMSKzM-L7g@mail.gmail.com> <jh161s$kqp$1@dough.gmane.org> |
| Subject | Re: Read-only attribute in module |
| Newsgroups | comp.lang.python |
| Message-ID | <mailman.5653.1328872316.27778.python-list@python.org> (permalink) |
Terry Reedy wrote > > On 2/9/2012 6:43 AM, Mateusz Loskot wrote: >> import xyz print(xyz.flag) # OK >> xyz.flag = 0 # error due to no write access > > Why prevent that? If you called it 'FLAG', that would indicate that it > is a constant that should not be changed. While Python make some effort > to prevent bugs, it is generally a 'consenting adults' language. > Terry, 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() But, I thought it would be more convenient to have a read-only property in scope of the module. Sometimes, especially when wrapping C code, it is not possible to map C API semantics to Python concepts as 1:1. ----- -- Mateusz Loskot http://mateusz.loskot.net -- View this message in context: http://python.6.n6.nabble.com/Read-only-attribute-in-module-tp4378950p4382967.html Sent from the Python - python-list mailing list archive at Nabble.com.
Back to comp.lang.python | Previous | Next | Find similar | Unroll thread
Re: Read-only attribute in module mloskot <mateusz@loskot.net> - 2012-02-10 03:11 -0800
csiph-web