On 05/08/2019 06:22, raymond.hettin...@gmail.com wrote:
I have read through (most) of the thread, and visited the issue referenced.
> We should revisit what we want to do (if anything) about invalid escape
> sequences.
IMHO - revisit is okay, generally - but that was actually done a long
time ago.
On Tue, Aug 6, 2019 at 11:48 AM wrote:
>
> End-user experience isn't something that can just be argued away. Steve and
> I are reporting a recurring annoyance. The point of a beta release is to
> elicit these kinds of reports so they can be addressed before it is too late.
> ISTM you are cho
End-user experience isn't something that can just be argued away. Steve and I
are reporting a recurring annoyance. The point of a beta release is to elicit
these kinds of reports so they can be addressed before it is too late. ISTM
you are choosing not to believe the early feedback and don't
> I broadly agree that the warning is very annoying, particularly
> when it comes from third-party packages (I see it from some
> of pip's vendored dependencies all the time),
The same here as well.
The other annoyance is that it pops up during live demos, student teaching
sessions, and during
Thanks for looking at other languages do. It gives some hope that this won't
end-up being a usability fiasco.
___
Python-Dev mailing list -- python-dev@python.org
To unsubscribe send an email to python-dev-le...@python.org
https://mail.python.org/mailm
On 04Aug2019 2122, raymond.hettin...@gmail.com wrote:
We should revisit what we want to do (if anything) about invalid escape
sequences.
For Python 3.8, the DeprecationWarning was converted to a SyntaxWarning which
is visible by default. The intention is to make it a SyntaxError in Python 3.9
On Mon, 5 Aug 2019 at 15:44, Facundo Batista wrote:
>
> El lun., 5 de ago. de 2019 a la(s) 01:25,
> escribió:
> >
> > We should revisit what we want to do (if anything) about invalid escape
> > sequences.
> >
> > For Python 3.8, the DeprecationWarning was converted to a SyntaxWarning
> > which
El lun., 5 de ago. de 2019 a la(s) 01:25,
escribió:
>
> We should revisit what we want to do (if anything) about invalid escape
> sequences.
>
> For Python 3.8, the DeprecationWarning was converted to a SyntaxWarning which
> is visible by default. The intention is to make it a SyntaxError in Py
On 01/08/2019 15:14, Victor Stinner wrote:
> For example, xlc C compiler seems to be commonly used on AIX. I don't
> know how is its C99 support.
FYI - this is from the XL C "compiler" reference document for V-10, with
copyright set in 2008.
Just an excerpt - c99 is supported. Just have to say CC=
Thank you for confining it!
Currently, Python defines PY_FORMAT_SIZE_T as:
#ifndef PY_FORMAT_SIZE_T
# if SIZEOF_SIZE_T == SIZEOF_INT && !defined(__APPLE__)
# define PY_FORMAT_SIZE_T ""
# elif SIZEOF_SIZE_T == SIZEOF_LONG
# define PY_FORMAT_SIZE_T "l"
# elif defined(MS_WINDOWS)
# define PY_FORMAT_
On 02/08/2019 04:12, Inada Naoki wrote:
> On Thu, Aug 1, 2019 at 10:21 PM Victor Stinner wrote:
>> Hi INADA-san,
>>
>> Is it supported on macOS, FreeBSD, AIX, Android, etc.?
>>
>> My notes on platforms supported by Python:
>> https://pythondev.readthedocs.io/platforms.html
>>
>> For example, xlc C
05.08.19 07:22, raymond.hettin...@gmail.com пише:
We should revisit what we want to do (if anything) about invalid escape
sequences.
For Python 3.8, the DeprecationWarning was converted to a SyntaxWarning which
is visible by default. The intention is to make it a SyntaxError in Python 3.9.
On Mon, Aug 5, 2019 at 2:24 PM wrote:
> For Python 3.8, the DeprecationWarning was converted to a SyntaxWarning which
> is visible by default. The intention is to make it a SyntaxError in Python
> 3.9.
>
> This once seemed like a reasonable and innocuous idea to me; however, I've
> been using
13 matches
Mail list logo
