ACTIVITY SUMMARY (2014-11-28 - 2014-12-05)
Python tracker at http://bugs.python.org/
To view or respond to any of the issues listed below, click on the issue.
Do NOT respond to this message.
Issues counts and deltas:
open4666 ( -2)
closed 30095 (+39)
total 34761 (+37)
Open issues
For those who haven't followed along, here's the final text of PEP 479,
with a brief Acceptance section added. The basic plan hasn't changed, but
there's a lot more clarifying text and discussion of a few
counter-proposals. Please send suggestions for editorial improvements to
p...@python.org. The
This is a bit long as I espoused as if this was a blog post to try and give
background info on my thinking, etc. The TL;DR folks should start at the
Ideal Scenario section and read to the end.
P.S.: This is in Markdown and I have put it up at
On Dec 5, 2014, at 3:04 PM, Brett Cannon bcan...@gmail.com wrote:
words
This looks like a pretty good write up, seems to pretty fairly evaluate the
various sides and the various concerns.
---
Donald Stufft
PGP: 7C6B 7C5D 5E2B 6356 A926 F04F 6E3C BCE9 3372 DCFA
It now promotes using tooling as much as possible to automate the process
of making code by Python 2/3 source-compatible:
https://docs.python.org/3.5/howto/pyporting.html
Blog post about it at
http://nothingbutsnark.svbtle.com/commentary-on-getting-your-code-to-run-on-python-23
.
On Fri, Dec 5, 2014, at 16:04, Brett Cannon wrote:
It now promotes using tooling as much as possible to automate the process
of making code by Python 2/3 source-compatible:
https://docs.python.org/3.5/howto/pyporting.html
Are you going to update the 2.7 copy of the howto, too?
Very nice, Brett.
On Fri, Dec 5, 2014 at 1:04 PM, Brett Cannon bcan...@gmail.com wrote:
And we can't forget the people who help keep all of this running as well.
There are those that manage the SSH keys, the issue tracker, the review
tool, hg.python.org, and the email system that let's use
On Fri Dec 05 2014 at 4:07:46 PM Benjamin Peterson benja...@python.org
wrote:
On Fri, Dec 5, 2014, at 16:04, Brett Cannon wrote:
It now promotes using tooling as much as possible to automate the process
of making code by Python 2/3 source-compatible:
On Dec 5, 2014, at 6:10 PM, Brett Cannon bcan...@gmail.com wrote:
On Fri Dec 05 2014 at 4:07:46 PM Benjamin Peterson benja...@python.org
mailto:benja...@python.org wrote:
On Fri, Dec 5, 2014, at 16:04, Brett Cannon wrote:
It now promotes using tooling as much as possible to
On Dec 5, 2014 4:18 PM, Eric Snow ericsnowcurren...@gmail.com wrote:
Very nice, Brett.
On Fri, Dec 5, 2014 at 1:04 PM, Brett Cannon bcan...@gmail.com wrote:
And we can't forget the people who help keep all of this running as
well.
There are those that manage the SSH keys, the issue
On 6 December 2014 at 06:24, Donald Stufft don...@stufft.io wrote:
On Dec 5, 2014, at 3:04 PM, Brett Cannon bcan...@gmail.com wrote:
words
This looks like a pretty good write up, seems to pretty fairly evaluate the
various sides and the various concerns.
Agreed - thanks for taking this on
On Fri, Dec 5, 2014, at 18:16, Donald Stufft wrote:
On Dec 5, 2014, at 6:10 PM, Brett Cannon bcan...@gmail.com wrote:
On Fri Dec 05 2014 at 4:07:46 PM Benjamin Peterson benja...@python.org
mailto:benja...@python.org wrote:
On Fri, Dec 5, 2014, at 16:04, Brett Cannon
Hi All
I just want to put my two cents into this.
This would definitely be a great step to take. I have been discussing PEP
462 with Nick, and the automation was definitely something that would be
something that would be great to have - I mean, I was submitting a simple
documentation patch for
On Fri, 05 Dec 2014 15:17:35 -0700, Eric Snow ericsnowcurren...@gmail.com
wrote:
On Fri, Dec 5, 2014 at 1:04 PM, Brett Cannon bcan...@gmail.com wrote:
We don't exactly have a ton of people
constantly going I'm so bored because everything for Python's development
infrastructure gets sorted
On Dec 5, 2014, at 8:26 PM, R. David Murray rdmur...@bitdance.com wrote:
On Fri, 05 Dec 2014 15:17:35 -0700, Eric Snow ericsnowcurren...@gmail.com
wrote:
On Fri, Dec 5, 2014 at 1:04 PM, Brett Cannon bcan...@gmail.com wrote:
We don't exactly have a ton of people
constantly going I'm so
On 6 December 2014 at 11:39, Donald Stufft don...@stufft.io wrote:
Maybe our infrastructure folks will have a thought or two about this?
I'm willing to put some work into this if we can figure out what
direction to head in. It could well be tied in to moving
bugs.python.org in with the rest
On 6 December 2014 at 10:44, Benjamin Peterson benja...@python.org wrote:
On Fri, Dec 5, 2014, at 18:16, Donald Stufft wrote:
Do we need to update it? Can it just redirect to the 3 version?
Technically, yes, of course. However, that would unexpected take you out
of the Python 2 docs context.
On 6 December 2014 at 04:42, Guido van Rossum gu...@python.org wrote:
For those who haven't followed along, here's the final text of PEP 479, with
a brief Acceptance section added. The basic plan hasn't changed, but there's
a lot more clarifying text and discussion of a few counter-proposals.
On 6 December 2014 at 14:40, Nick Coghlan ncogh...@gmail.com wrote:
On 6 December 2014 at 10:44, Benjamin Peterson benja...@python.org wrote:
On Fri, Dec 5, 2014, at 18:16, Donald Stufft wrote:
Do we need to update it? Can it just redirect to the 3 version?
Technically, yes, of course.
On 12/5/2014 3:04 PM, Brett Cannon wrote:
1. Contributor clones a repository from hg.python.org http://hg.python.org
2. Contributor makes desired changes
3. Contributor generates a patch
4. Contributor creates account on bugs.python.org
http://bugs.python.org and signs the
[contributor
20 matches
Mail list logo
