Download Microsoft C/C++ compiler for use with Python 2.6/2.7 ASAP

[Stephen Hansen]

On 7/7/10 9:46 PM, "Martin v. Löwis" wrote:
>> I saw you already mentioned work toward this a few months (years ?)
>> ago. Is there some kind of roadmap, or could you use some help ? I
>> would really like to solve this issue as much as we possibly can,
> 
> Well, Python 3 has already dropped stdio for its own io library, and
> I do want to get rid of the remaining FILE* usage for 3.2. Any other
> change needs to be discussed on python-dev first; contributions are welcome.

Really? I wasn't entirely aware of this effect of the "io" module.
Somehow, without at all paying attention (because certain third party
modules blocking me for awhile, I never looked close enough), I just
sort of thought the "io" module was mostly thin wrappers around stdio
primitives, into a more Pythonic API.

This actually makes me long for Python 3 more. And adjust agendas to
push my day-job work to 2.7 as soon as possible, and start a preemptive
reconfiguration to support a future Py3k migration.

-- 

   Stephen Hansen
   ... Also: Ixokai
   ... Mail: me+list/python (AT) ixokai (DOT) io
   ... Blog: http://meh.ixokai.io/

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 487 bytes
Desc: OpenPGP digital signature
URL: <http://mail.python.org/pipermail/python-list/attachments/20100707/2f0920eb/attachment-0001.sig>