Message288012
| Author |
lemburg |
| Recipients |
christian.heimes, lemburg, methane, vstinner |
| Date |
2017年02月17日.15:30:39 |
| SpamBayes Score |
-1.0 |
| Marked as misclassified |
Yes |
| Message-id |
<5462d68e-f0a1-01cf-0aab-0f3cf252a1f9@egenix.com> |
| In-reply-to |
<CAMpsgwYcpsu-TO1s1_8H5wSYfR23BHVJn9Go1APsfrs5YNe4dw@mail.gmail.com> |
| Content |
On 17.02.2017 13:06, STINNER Victor wrote:
>> Alternatively, sysconfig data could be made available via a C lookup function; with the complete dictionary only being created on demand. get_config_var() already is such a lookup API which could be used as front-end.
>
> I don't think that it's worth it to reimplement partially sysconfig in
> C. This module is huge, complex, and platform dependant.
Sorry, I was just referring to the data part of sysconfig,
not sysconfig itself.
Having a lookup function much like we have for unicodedata
makes things much more manageable, since you don't need to
generate a dictionary in memory for all the values in the
config data. Creating that dictionary takes a while (in terms
of ms). |
|