On 3/15/2016 11:07 PM, Chris Angelico wrote:
On Wed, Mar 16, 2016 at 5:03 PM, Serhiy Storchaka wrote:
On 15.03.16 22:30, Guido van Rossum wrote:
I came across a file that had two different coding cookies -- one on
the first line and one on the second. CPython uses the first, but mypy
happens t
On Wed, Mar 16, 2016 at 2:07 AM, Chris Angelico wrote:
> Why would you ever have two coding cookies in a file? Surely this
> should be either an error, or ill-defined (ie parsers are allowed to
> pick whichever they like, including raising)?
>
> ChrisA
+1. If multiple coding cookies are found, an
On Wed, Mar 16, 2016 at 5:03 PM, Serhiy Storchaka wrote:
> On 15.03.16 22:30, Guido van Rossum wrote:
>>
>> I came across a file that had two different coding cookies -- one on
>> the first line and one on the second. CPython uses the first, but mypy
>> happens to use the second. I couldn't find a
On 15.03.16 22:30, Guido van Rossum wrote:
I came across a file that had two different coding cookies -- one on
the first line and one on the second. CPython uses the first, but mypy
happens to use the second. I couldn't find anything in the spec or
docs ruling out the second interpretation. Does
Hey all,
I've put up an incredibly sketchy, terrible ideas page up for Summer of
Code with core python:
https://wiki.python.org/moin/SummerOfCode/2016/python-core
I'm pretty much the worst person to do this since I'm always swamped
with admin stuff and particularly out of touch with what's n
Guido van Rossum writes:
> I agree that the spirit of the PEP is to stop at the first coding
> cookie found. Would it be okay if I updated the PEP to clarify this?
> I'll definitely also update the docs.
+1, it never occurred to me that the specification could mean otherwise.
On reflection I can
I agree that the spirit of the PEP is to stop at the first coding
cookie found. Would it be okay if I updated the PEP to clarify this?
I'll definitely also update the docs.
On Tue, Mar 15, 2016 at 2:04 PM, Brett Cannon wrote:
>
>
> On Tue, 15 Mar 2016 at 13:31 Guido van Rossum wrote:
>>
>> I cam
On 2016-03-15 20:53, MRAB wrote:
On 2016-03-15 20:30, Guido van Rossum wrote:
I came across a file that had two different coding cookies -- one on
the first line and one on the second. CPython uses the first, but mypy
happens to use the second. I couldn't find anything in the spec or
docs ruling
On Tue, Mar 15, 2016 at 01:30:08PM -0700, Guido van Rossum wrote:
> I came across a file that had two different coding cookies -- one on
> the first line and one on the second. CPython uses the first, but mypy
> happens to use the second. I couldn't find anything in the spec or
> docs ruling out th
On Tue, 15 Mar 2016 at 13:31 Guido van Rossum wrote:
> I came across a file that had two different coding cookies -- one on
> the first line and one on the second. CPython uses the first, but mypy
> happens to use the second. I couldn't find anything in the spec or
> docs ruling out the second in
On 2016-03-15 20:30, Guido van Rossum wrote:
I came across a file that had two different coding cookies -- one on
the first line and one on the second. CPython uses the first, but mypy
happens to use the second. I couldn't find anything in the spec or
docs ruling out the second interpretation. Do
I came across a file that had two different coding cookies -- one on
the first line and one on the second. CPython uses the first, but mypy
happens to use the second. I couldn't find anything in the spec or
docs ruling out the second interpretation. Does anyone have a
suggestion (apart from followi
On 15 March 2016 at 08:04, Nick Coghlan wrote:
> On 15 March 2016 at 15:15, Martin Panter wrote:
>> _freeze_importlib.o: _freeze_importlib.c Makefile
>>
>> _freeze_importlib: _freeze_importlib.o [. . .]
>> $(LINKCC) [. . .]
>>
>> importlib_external.h: _bootstrap_external.py _freeze_import
> On 15 Mar 2016, at 01:08, Jim Baker wrote:
>
> I have no vested interest in this, other than the continuing work we have
> done to make Jython compatible with OpenSSL's model, warts and all.
>
> But the fact that BoringSSL cleans up the OpenSSL API
> (https://boringssl.googlesource.com/bori
On 15 March 2016 at 15:15, Martin Panter wrote:
> The problem is not the reference to Makefile. The graminit files do
> not depend on Makefile. The bigger problem is that the checked-in
> files depend on compiled programs. This is a summary of the current
> rules for importlib:
>
> _freeze_importl
15 matches
Mail list logo