On Mon, Sep 28, 2015 at 5:14 PM, Mark Lawrence wrote:
>
> For anyone interested although this http://bugs.python.org/issue3871 mingw
> issue is closed, it points to four other issues. In total there are around
> 25 mingw issues open. Maybe some of the work done on them can be tied up
> with the
On 9/28/2015 7:05 PM, Martin Panter wrote:
On 28 September 2015 at 22:31, Terry Reedy wrote:
. . . it may have merged in the wrong place, such as putting a things into the
3.5.1 section of 3.6 NEWS, which should not be there.
Since you mentioned this and I also noticed this, can I ask why the
On 29/09/2015 00:52, Nathaniel Smith wrote:
On Mon, Sep 28, 2015 at 2:55 PM, Paul Moore wrote:
On 28 September 2015 at 22:18, Nathaniel Smith wrote:
On Sep 28, 2015 1:39 PM, "Paul Moore" wrote:
On 28 September 2015 at 21:18, MRAB wrote:
Same here. I compile the regex module for Python 2.
On Mon, Sep 28, 2015 at 2:55 PM, Paul Moore wrote:
> On 28 September 2015 at 22:18, Nathaniel Smith wrote:
>> On Sep 28, 2015 1:39 PM, "Paul Moore" wrote:
>>>
>>> On 28 September 2015 at 21:18, MRAB wrote:
>>> > Same here. I compile the regex module for Python 2.5-2.7 and 3.1-3.5,
>>> > both 32
At the top of the file in the default branch, I see:
What's New in Python 3.6.0 alpha 1?
Which has a few things in it.
Eric.
On 9/28/2015 7:30 PM, Guido van Rossum wrote:
> It used to be tradition to keep old news sections. Looks like the last
> time we cleared it out was for 3.4.0.
>
> But it
It used to be tradition to keep old news sections. Looks like the last time
we cleared it out was for 3.4.0.
But it's suspicious there's no section for 3.6 at all. Unless... 3.6 has
nothing new yet, it's all just bugfixes ported from 3.5?
On Mon, Sep 28, 2015 at 4:05 PM, Martin Panter wrote:
>
On 28 September 2015 at 22:31, Terry Reedy wrote:
> . . . it may have merged in the wrong place, such as putting a things into the
> 3.5.1 section of 3.6 NEWS, which should not be there.
Since you mentioned this and I also noticed this, can I ask why the
3.5.1 section is there, if it isn’t meant
On 9/28/2015 1:12 PM, Alexander Belopolsky wrote:
On Mon, Sep 28, 2015 at 4:13 AM, Terry Reedy mailto:tjre...@udel.edu>> wrote:
Normal one specified in devguide: commit 3.4, merge 3.5, merge 3.6,
That's exactly what I did at fist, but apparently while I was doing
this, another commit was
On Sep 28, 2015, at 02:38 PM, Guido van Rossum wrote:
>Your comments make total sense -- we're just short on people who can write
>that kind of docs. :-(
Oh well, maybe someday we will! ;)
-Barry
pgpGVDxk58hN8.pgp
Description: OpenPGP digital signature
_
On 28 September 2015 at 22:18, Nathaniel Smith wrote:
> On Sep 28, 2015 1:39 PM, "Paul Moore" wrote:
>>
>> On 28 September 2015 at 21:18, MRAB wrote:
>> > Same here. I compile the regex module for Python 2.5-2.7 and 3.1-3.5,
>> > both 32-bit and 64-bit, using MinGW-w64, and I haven't had a probl
Your comments make total sense -- we're just short on people who can write
that kind of docs. :-(
On Mon, Sep 28, 2015 at 2:15 PM, Barry Warsaw wrote:
> On Sep 28, 2015, at 08:22 AM, Guido van Rossum wrote:
>
> >I saw that you had a need for an asyncio tutorial. I wonder if the "500
> >lines" ch
On Sep 28, 2015 1:39 PM, "Paul Moore" wrote:
>
> On 28 September 2015 at 21:18, MRAB wrote:
> > Same here. I compile the regex module for Python 2.5-2.7 and 3.1-3.5,
> > both 32-bit and 64-bit, using MinGW-w64, and I haven't had a problem yet
> > that wasn't due to a bug in the source code.
>
> I
On Sep 28, 2015, at 08:22 AM, Guido van Rossum wrote:
>I saw that you had a need for an asyncio tutorial. I wonder if the "500
>lines" chapter on asyncio would help? I didn't write it; I only write the
>500 lines of code, A. Jesse Jiryu Davis wrote the text, and it's wonderful:
>http://aosabook.or
On 2015-09-28 21:38, Paul Moore wrote:
On 28 September 2015 at 21:18, MRAB wrote:
> Same here. I compile the regex module for Python 2.5-2.7 and 3.1-3.5,
> both 32-bit and 64-bit, using MinGW-w64, and I haven't had a problem yet
> that wasn't due to a bug in the source code.
Interesting. With P
On 28 September 2015 at 21:18, MRAB wrote:
> Same here. I compile the regex module for Python 2.5-2.7 and 3.1-3.5,
> both 32-bit and 64-bit, using MinGW-w64, and I haven't had a problem yet
> that wasn't due to a bug in the source code.
Interesting. With Python 3.5, what CRT does the module use?
On 2015-09-28 19:00, Erik Bray wrote:
On Fri, Sep 25, 2015 at 6:27 PM, Chris Barker - NOAA Federal
wrote:
You can use "Windows SDK for Windows 7 and .NET Framework 4".
http://www.microsoft.com/en-us/download/details.aspx?id=8279
Thanks. Last time I tried that route, it was for 64 bit py2.7.
On Fri, Sep 25, 2015 at 6:27 PM, Chris Barker - NOAA Federal
wrote:
>
> You can use "Windows SDK for Windows 7 and .NET Framework 4".
>
> http://www.microsoft.com/en-us/download/details.aspx?id=8279
>
>
> Thanks. Last time I tried that route, it was for 64 bit py2.7. And it
> required some kludgin
See http://bugs.python.org/issue18967 if you want to join the discussion on
how to solve Misc/NEWS potentially in the short term (long term we have a
plan once someone has time to hack on the issue tracker).
On Mon, 28 Sep 2015 at 10:12 Alexander Belopolsky <
alexander.belopol...@gmail.com> wrote:
On Mon, Sep 28, 2015 at 4:13 AM, Terry Reedy wrote:
> Normal one specified in devguide: commit 3.4, merge 3.5, merge 3.6,
That's exactly what I did at fist, but apparently while I was doing this,
another commit was pushed to all three branches. To recover, I did a
series of hg update 3.x; hg
meant:
https://mail.python.org/pipermail/group-organizers/2015-September/000441.html
___
Python-Dev mailing list
Python-Dev@python.org
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
https://mail.python.org/mailman/options/python-dev/arc
I would like to propose a mixed core-dev none-core-dev sprint to occur in
Chicago within the next couple months. ChiPy (http://chipy.org) can help
sponsor. I am going to share my thoughts on this with the group-organizers <
group-organiz...@python.org> list first in order to get some feedback. Post
Cool! Glad to see that the idea of local core-dev sprints hasn't totally
been forgotten.
I saw that you had a need for an asyncio tutorial. I wonder if the "500
lines" chapter on asyncio would help? I didn't write it; I only write the
500 lines of code, A. Jesse Jiryu Davis wrote the text, and it'
Yesterday (27-Sep-2015), four Washington DC area Python developers got
together for a local Python hacking sprint. Andrew, Eric, Jason, and I were
joined remotely by the esteemed R. David Murray. We did stuff and had fun!
We hope to do stuff and have fun again! If you want to join us for stuff a
On 9/28/2015 2:56 AM, Martin Panter wrote:
Also @Terry, not sure on your workflow,
Normal one specified in devguide: commit 3.4, merge 3.5, merge 3.6,
except I do it with TortoiseHG Workbench GUI.
> but you might have been able
to avoid pushing your 3.4 commits. You might have been able to
On 28/09/2015, Terry Reedy wrote:
> You neglected to forward merge a 3.4-3.4 merge and a 3.5-3.5 merge. I
> failed to notice the first and added a commit, and then backed it out,
> when I could not merge forward due to merge conflicts with your commits.
> Perhaps you just need to null-merge the
25 matches
Mail list logo
