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 | bhy |
|---|---|
| Recipients | alexandre.vassalotti, amaury.forgeotdarc, benjamin.peterson, bhy |
| Date | 2008年07月24日.06:46:01 |
| SpamBayes Score | 0.0010235329 |
| Marked as misclassified | No |
| Message-id | <1216881965.34.0.361210909464.issue3208@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
I found the explanation of why buitl-ins are immutable: For the curious: there are two reasons why changing built-in classes is disallowed. First, it would be too easy to break an invariant of a built-in type that is relied upon elsewhere, either by the standard library, or by the run-time code. Second, when Python is embedded in another application that creates multiple Python interpreters, the built-in class objects (being statically allocated data structures) are shared between all interpreters; thus, code running in one interpreter might wreak havoc on another interpreter, which is a no-no. (From http://www.python.org/download/releases/2.2.3/descrintro/) Is the statement still valid for current version of Python? |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2008年07月24日 06:46:05 | bhy | set | spambayes_score: 0.00102353 -> 0.0010235329 recipients: + bhy, amaury.forgeotdarc, alexandre.vassalotti, benjamin.peterson |
| 2008年07月24日 06:46:05 | bhy | set | spambayes_score: 0.00102353 -> 0.00102353 messageid: <1216881965.34.0.361210909464.issue3208@psf.upfronthosting.co.za> |
| 2008年07月24日 06:46:04 | bhy | link | issue3208 messages |
| 2008年07月24日 06:46:02 | bhy | create | |