This issue tracker has been migrated to GitHub ,
and is currently read-only.
For more information,
see the GitHub FAQs in the Python's Developer Guide.
| Author | berker.peksag |
|---|---|
| Recipients | berker.peksag |
| Date | 2015年04月27日.17:40:18 |
| SpamBayes Score | -1.0 |
| Marked as misclassified | Yes |
| Message-id | <1430156419.01.0.516849484938.issue24065@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
Looks like READ_RESTRICTED, PY_WRITE_RESTRICTED and RESTRICTED flags were used for "restricted mode" [1] in Python 2. "restricted mode" has been deprecated in Python 2.3. Also, the current documentation is outdated. WRITE_RESTRICTED is now PY_WRITE_RESTRICTED: https://docs.python.org/3/extending/newtypes.html#generic-attribute-management There are a few usages of these flags in the CPython source: PY_WRITE_RESTRICTED * Objects/funcobject.c * Objects/methodobject.c RESTRICTED * Objects/funcobject.c * Objects/classobject.c Are they still useful or can we deprecate/remove them now? [1] https://github.com/python/cpython/blob/2.7/Python/structmember.c#L180 |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2015年04月27日 17:40:19 | berker.peksag | set | recipients: + berker.peksag |
| 2015年04月27日 17:40:19 | berker.peksag | set | messageid: <1430156419.01.0.516849484938.issue24065@psf.upfronthosting.co.za> |
| 2015年04月27日 17:40:18 | berker.peksag | link | issue24065 messages |
| 2015年04月27日 17:40:18 | berker.peksag | create | |