2017-06-29 17:09 GMT+02:00 Victor Stinner :
> Correct me if I'm wrong, but, for the first time, *all reference
> leaks* have been fixed on *all branches* (2.7, 3.5, 3.6 and master),
> on *Linux and Windows*! Before, we mostly focused on the master branch
> (called
On 6/29/2017 5:34 PM, Rob Boehne wrote:
Hello,
I¹m new to the list, and contributing to Python specifically, and I¹m
interested in getting master and 3.6 branches building and working
³better² on UNIX.
I¹ve been looking at a problem building 3.6 on HP-UX and see a PR was
merged into master,
Hello,
I¹m new to the list, and contributing to Python specifically, and I¹m
interested in getting master and 3.6 branches building and working
³better² on UNIX.
I¹ve been looking at a problem building 3.6 on HP-UX and see a PR was
merged into master, https://github.com/python/cpython/pull/1351
2017-06-29 19:13 GMT+02:00 Terry Reedy :
> How about compiler warnings (and errors)?
That would be nice to have, but I don't have the bandwidth to handle this goal.
> When I compile on Windows, there
> are a boatload of orange-yellow warnings. Some are about using a
On 29Jun2017 1157, Terry Reedy wrote:
On 6/29/2017 1:54 PM, Steve Dower wrote:
Some warnings are also complicated because of the nature of CPython.
For example, the socket module exposes deprecated CRT functions (on
Windows) directly because the API of the socket module promises to
provide
On 6/29/2017 1:54 PM, Steve Dower wrote:
On 29Jun2017 1013, Terry Reedy wrote:
Great work.
Agreed. Thanks, Victor!
How about compiler warnings (and errors)? When I compile on Windows,
there are a boatload of orange-yellow warnings. Some are about using
a deprecated featured; some about
On 29Jun2017 1013, Terry Reedy wrote:
Great work.
Agreed. Thanks, Victor!
How about compiler warnings (and errors)? When I compile on Windows,
there are a boatload of orange-yellow warnings. Some are about using a
deprecated featured; some about dodgy casts; some (I presume) about
other
On 6/29/2017 11:09 AM, Victor Stinner wrote:
Hi,
Our buildbots are now even more stable than in my previous buildbot report.
Many random failures have been fixed, even if there are still many
rare random failures (most of them are related to multiprocessing).
Search for issues created by
Hi,
Our buildbots are now even more stable than in my previous buildbot report.
Many random failures have been fixed, even if there are still many
rare random failures (most of them are related to multiprocessing).
Search for issues created by "haypo" (me!) with the Component "Tests"
to see all