[Python-ideas] Python-ideas Digest, Vol 90, Issue 30

Terry Reedy tjreedy at udel.edu
Fri May 23 22:05:11 CEST 2014


On 5/23/2014 6:39 AM, Ned Batchelder wrote:
> On 5/23/14 5:53 AM, Antoine Pitrou wrote:
>> On Thu, 22 May 2014 22:53:28 -0400
>> Terry Reedy <tjreedy at udel.edu> wrote:
>>>> I'd like to understand why we think the Python compiler is different in
>>>> this regard than a C compiler.
>>> Python is a different language. But let us not get sidetracked on that.
>> The number one difference is that people don't compile code explicitly
>> when writing Python code (well, except packagers who call compileall(),
>> and a few advanced uses). So "choosing compilation options" is really
>> not part of the standard workflow for developing in Python.
>
> That seems an odd distinction to make, given that we already do have
> ways to control how the compilation step happens,

There are not used much, and I doubt that anyone is joyous at the status 
quo. Which is why your proposal looks more inviting (to me, and I think 
to some others) as part of a reworking of the clumbsy status quo than as 
a clumbsy add-on.

-- 
Terry Jan Reedy



More information about the Python-ideas mailing list