Message158362
| Author | brett.cannon |
|---|---|
| Recipients | Arfrever, brett.cannon, eric.araujo, eric.snow, meador.inge, pitrou |
| Date | 2012-04-15.19:57:26 |
| SpamBayes Score | -1.0 |
| Marked as misclassified | Yes |
| Message-id | <1334519847.55.0.00153269986068.issue13959@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
Just because I was thinking about it, I wonder if necessarily all the frozen stuff really needs to stay in import.c. I mean a frozen module is really just an entry in an array of structs that has a name of an char*[]. I don't see why one couldn't simply have a get_frozen_bytes() method to convert that char*[] into a bytes object and use that to construct a module in pure Python code. |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2012-04-15 19:57:27 | brett.cannon | set | recipients: + brett.cannon, pitrou, eric.araujo, Arfrever, meador.inge, eric.snow |
| 2012-04-15 19:57:27 | brett.cannon | set | messageid: <1334519847.55.0.00153269986068.issue13959@psf.upfronthosting.co.za> |
| 2012-04-15 19:57:26 | brett.cannon | link | issue13959 messages |
| 2012-04-15 19:57:26 | brett.cannon | create | |