I actually realized right after I sent this that I am writing C++, so
maybe it's a moot point. (Still trying to figure out how to use C for
this, but it's an optional extension module only exposed for testing,
so maybe it really doesn't matter.)
Context is https://github.com/python/cpython/pull/28
On Tue, Jul 25, 2017, at 21:59, Devin Jeanpierre wrote:
> https://www.python.org/dev/peps/pep-0007/ says two things:
>
> > Python versions greater than or equal to 3.6 use C89 with several select
> > C99 features:
> > [...]
> > C++-style line comments
This section overrides further edicts in t
https://www.python.org/dev/peps/pep-0007/ says two things:
> Python versions greater than or equal to 3.6 use C89 with several select C99
> features:
> [...]
> C++-style line comments
and also:
> Never use C++ style // one-line comments.
Which is it?
-- Devin
_
On Tue, 25 Jul 2017 at 07:30 Ben Hoyt wrote:
> With the linking back and forth, I'm curious why there wasn't a switch to
> use GitHub's issue tracker when we switched to GitHub. I'm sure there was
> previous discussion about this and good reasons not to, but couldn't find
> those quickly (PEP 512
With the linking back and forth, I'm curious why there wasn't a switch to
use GitHub's issue tracker when we switched to GitHub. I'm sure there was
previous discussion about this and good reasons not to, but couldn't find
those quickly (PEP 512, Google search, etc) -- can someone point me in the
ri
On 25/07/2017 06:51, Nick Coghlan wrote:
On 25 July 2017 at 02:23, Ben Hoyt wrote:
This is more of a python-ideas discussion, and Steven's answer is good.
I'll just add one thing. Maybe it's obvious to others, but I've liked
for...else since I found a kind of mnemonic to help me remember whe
On Sat, Jul 22, 2017 at 12:28 AM, Brett Cannon wrote:
> P.S.: Berker Peksag is working on providing commit emails with diffs in them
> which is the other most requested feature since the transition.
I forgot to give a status update on this. I deployed it on Heroku last
week. You can see an exampl
2017-07-25 10:37 GMT+02:00 Larry Hastings :
> On behalf of the Python development community and the Python 3.4 and Python
> 3.5 release teams, I'm relieved to announce the availability of Python
> 3.4.7rc1 and Python 3.5.4rc1.
I checked for known security vulnerabilities: except of the issue
#2960
On behalf of the Python development community and the Python 3.4 and
Python 3.5 release teams, I'm relieved to announce the availability of
Python 3.4.7rc1 and Python 3.5.4rc1.
Python 3.4 is now in "security fixes only" mode. This is the final
stage of support for Python 3.4. Python 3.4 no
