Ned Deily added the comment:
Steve: just a minute ago, zware out the win8.1 bot's repo and restarted a 3.7
build.
--
___
Python tracker
<https://bugs.python.org/is
Ned Deily added the comment:
er, "cleaned out"
--
___
Python tracker
<https://bugs.python.org/issue33614>
___
___
Python-bugs-list mailing list
Uns
Ned Deily added the comment:
Thanks, David. Yes, I think disabling "largefile" tests on that buildbot makes
the most sense. We're working on it.
--
nosy: +ned.deily
___
Python tracker
<https://bugs.pyt
Ned Deily added the comment:
> * Merge my patch in 3.7rc1, or
Sorry but we are not going to revisit this decision for 3.7.0. It's too late!
--
___
Python tracker
<https://bugs.python.org
Ned Deily added the comment:
New changeset 8ebf5ceb0f5408d1ebc26c19702ac0762ef5ea04 by Ned Deily in branch
'master':
bpo-33109: argparse subparsers are once again not required by default (GH-6919)
https://github.com/python/cpython/commit/8ebf5ceb0f5408d1ebc26c19702ac0
Ned Deily added the comment:
New changeset 8ebf5ceb0f5408d1ebc26c19702ac0762ef5ea04 by Ned Deily in branch
'master':
bpo-33109: argparse subparsers are once again not required by default (GH-6919)
https://github.com/python/cpython/commit/8ebf5ceb0f5408d1ebc26c19702ac0
Ned Deily added the comment:
New changeset dd7a255911f364cf521676082a89d4cac307737e by Ned Deily (Miss
Islington (bot)) in branch '3.7':
bpo-33109: argparse subparsers are once again not required by default (GH-6919)
(GH-7089)
https://github.com/python/cpyt
Ned Deily added the comment:
New changeset dd7a255911f364cf521676082a89d4cac307737e by Ned Deily (Miss
Islington (bot)) in branch '3.7':
bpo-33109: argparse subparsers are once again not required by default (GH-6919)
(GH-7089)
https://github.com/python/cpyt
Ned Deily added the comment:
> Is there then no pathway for actually fixing the bug? aka how can I get
> `required=True` to be the default.
There may very well be but, unfortunately, dealing with this newly-identified
3.x compatibility issue takes precedence for 3.7.0. In genera
Ned Deily added the comment:
That Windows8.1 buildbot sure keeps busy with all those builders assigned to it
:) Those refleaks builds take a *long* time!
http://buildbot.python.org/all/#/workers/11
But I see at least one builder has made it through successfully and no longer
fails in this
Ned Deily added the comment:
The same intermittent failure was seen on the ARMv7 Ubuntu 3.7 builder:
http://buildbot.python.org/all/#/builders/117/builds/314/steps/4/logs/stdio
0:00:36 load avg: 5.14 [ 48/415/1] test_numeric_tower crashed (Exit code -11)
-- running: test_unicodedata (36 sec
Ned Deily added the comment:
Update: we flubbed the first attempt at altering the Windows7 buildbot config
and, at the moment, I'm waiting for the fix for that to get manually copied to
the buildbot.
--
___
Python tracker
<https://bugs.py
Ned Deily added the comment:
This problem is still unresolved and causing buildbot failures. It really
should be fixed before we tag 3.7.0rc1. Serhiy, could you take a look at it,
please? Thanks!
http://buildbot.python.org/all/#/builders/87/builds/1014/steps/4/logs/stdio
--
nosy
Ned Deily added the comment:
Christian, I'm not sure how this issue now differs from Issue33618 (and whether
it can be closed as a duplicate) but, with the delay in OpenSSL 1.1.1 and as
discussed over there, full 1.1.1 support will have to wait for 3.7.1 et al so
I'm removing the
Ned Deily added the comment:
Since this is just an intermittent test failure and we have lived with it this
long, I think it can wait for 3.7.1 at this point. Downgrading to "critical".
--
priority: deferred blocker -> critical
___
P
Ned Deily added the comment:
At the PyCon US sprints, we looked into this and updated the Developer's Guide
with suggestions for how to configure a build on macOS with either Homebrew or
MacPorts for either 3.7+ or earlier. It is not an ideal solution so I want to
keep this open for no
Ned Deily added the comment:
Christian, ping again: can this be closed? In any case, it would not seem to
be a "deferred blocker"; downgrading to "critical". Please close or update,
thanks!
--
priority: deferred blocker -> critical
___
Ned Deily added the comment:
As far as I can tell, this issue is still open only because of the original
desire to expand the original documentation. YoSTEALTH produced PR 5447 based
on Victor's original doc update PR. In the meantime, the current 3.7 docs have
been updated som
Ned Deily added the comment:
Considering we have already shipped this fix in 3.6.5, I guess we can live
without a NEWS entry at this point -> closing this issue.
--
priority: deferred blocker ->
stage: patch review -> resolved
status: open
Ned Deily added the comment:
> PYTHONPATH=/usr/local/lib/python2.7/site-packages
That looks pretty suspicious right there. It's pulling in 2.7 modules. Normally
you should never need to set PYTHONPATH in a shell initialization script, like
.profile, rarely e
Ned Deily added the comment:
The Windows7 buildbot now runs the test suite with the "largefile" resource
disabled and no longer timed out on test_mmap. So that immediate problem is
now resolved. Before closing the issue, it would be good to discuss whether we
should do the same f
Ned Deily added the comment:
Sorry, I *did* close the issue prematurely; thanks for noticing!
--
___
Python tracker
<https://bugs.python.org/issue33614>
___
___
Ned Deily added the comment:
Victor:
>It would be nice to fix this bug before Python 3.7.0 final: either skip the
>test, or fix it.
These tests (and failures) are only on master / 3.x, not 3.7, right? If so,
they have no bearing on 3.7.0.
--
nosy: +ned.deily
priority: de
Change by Ned Deily :
--
priority: deferred blocker ->
___
Python tracker
<https://bugs.python.org/issue32493>
___
___
Python-bugs-list mailing list
Unsubscrib
Ned Deily added the comment:
For the record, Serhiy commented on this issue today in a thread on the
python-committers list:
"I have doubts about two issues. I feel the responsibility for them because I
had the opportunity to solve them before, but I lost it.
1. Changes in the AST
Ned Deily added the comment:
Based on more recent discussions and indirect feedback from downstream users
(primarily the recent IPython experience), I am reluctantly re-opening this
issue for 3.7.0. I take responsibility for encouraging us earlier in the beta
phase to continue with the
Ned Deily added the comment:
LGTM for 3.7
--
priority: release blocker -> high
___
Python tracker
<https://bugs.python.org/issue33654>
___
___
Python-bugs-lis
Ned Deily added the comment:
Yury, are you still planning to address this?
--
___
Python tracker
<https://bugs.python.org/issue32458>
___
___
Python-bugs-list m
Ned Deily added the comment:
Vinay, PR_6704, the 3.7 backport is still unmerged with review comments and
there are unresolved comments here. Can we at least get the 3.7 branch in sync
with the other branches while you sort this out one way or another?
--
nosy: +ned.deily
Change by Ned Deily :
--
versions: +Python 3.6, Python 3.7, Python 3.8 -Python 3.4
___
Python tracker
<https://bugs.python.org/issue33400>
___
___
Python-bug
Ned Deily added the comment:
> Last time I looked into this I couldn't reproduce the failures on my Windows
> 10 VM, so it seems like an AppVeyor-specific problem. I'll take another look
> on Monday.
But in msg317468 Victor asserts that it sometimes
New submission from Ned Deily :
Seen on some of the various FreeBSD buildbots:
==
ERROR: test_posix_fallocate (test.test_posix.PosixTester)
--
Traceback (most
Change by Ned Deily :
--
keywords: +patch
pull_requests: +6768
___
Python tracker
<https://bugs.python.org/issue33655>
___
___
Python-bugs-list mailing list
Unsub
Ned Deily added the comment:
New changeset 09c4a7dee2eb39b515e5f499f184257cdbe9cb42 by Ned Deily in branch
'master':
bpo-33655: Also ignore test_posix_fallocate failures on BSD platforms (GH-7134)
https://github.com/python/cpython/commit/09c4a7dee2eb39b515e5f499f18425
Ned Deily added the comment:
Fix merged for 3.7.0 and 3.6.6.
--
resolution: -> fixed
stage: patch review -> resolved
status: open -> closed
___
Python tracker
<https://bugs.python.or
Ned Deily added the comment:
P.S.:
> Koobs, could you please open a new issue about the failing test? Unless
> someone knows of a foolproof way to determine on all platforms that a file is
> resident on ZFS, the fix is to skip the test on FreeBSD as well if ZFS is
> likely to b
Ned Deily added the comment:
The macOS Tiger buildbot where all of these "too many files open" OS failures
occurred has been retired.
--
resolution: -> out of date
stage: -> resolved
status: open -> closed
___
Pyt
Ned Deily added the comment:
Since the macOS Tiger buildbot has been retired, let's close this unless a
similar failure pops up on another, more modern platform.
--
nosy: +ned.deily
resolution: -> out of date
stage: -> resolved
status: ope
Ned Deily added the comment:
OK, since I believe everyone who has spoken up so far has chosen B or a
variation on it, I think we can eliminate option A. And there also seems to be
a consensus so far among the core developers who have spoken up for the
approach in PR 7121. Before we commit
Ned Deily added the comment:
Nick, thanks for the notification. I assume this means you are planning to
provide one or more updates. If so, any idea when?
--
___
Python tracker
<https://bugs.python.org/issue33
Ned Deily added the comment:
Whether or not Tiger is supported, we no longer have any Tiger buildbots. We
agreed to retire them earlier this year.
--
___
Python tracker
<https://bugs.python.org/issue32
Ned Deily added the comment:
Steve - PR 7165 appears to have caused a buildbot failure:
http://buildbot.python.org/all/#/builders/12/builds/910
--
___
Python tracker
<https://bugs.python.org/issue33
Ned Deily added the comment:
@mdk, Would you have time to take a look at this? Thanks!
--
nosy: +mdk
versions: +Python 3.8
___
Python tracker
<https://bugs.python.org/issue32
Ned Deily added the comment:
bug fix, go for it.
--
___
Python tracker
<https://bugs.python.org/issue33672>
___
___
Python-bugs-list mailing list
Unsubscribe:
Ned Deily added the comment:
If it's a problem with a Windows build, you should add the Windows component so
the Windows team is nosied. But, in this case, I think Steve has already fixed
this.
--
components: +Windows
nosy: +ned.deily, paul.moore, steve.dower, tim.golden, zach
Change by Ned Deily :
--
versions: +Python 3.8
___
Python tracker
<https://bugs.python.org/issue30317>
___
___
Python-bugs-list mailing list
Unsubscribe:
Ned Deily added the comment:
New changeset 420092e255389008b399efa61db300fe44356ee8 by Ned Deily (Miss
Islington (bot)) in branch '3.7':
bpo-32410: Avoid blocking on file IO in sendfile fallback code (GH-7172) (#7182)
https://github.com/python/cpyt
Ned Deily added the comment:
New changeset 0dd8fd03584b61cd769be88f5a2fb59b0d8f6d18 by Ned Deily (Miss
Islington (bot)) in branch '3.7':
bpo-33674: asyncio: Fix SSLProtocol race (GH-7175) (#7187)
https://github.com/python/cpython/commit/0dd8fd03584b61cd769be88f5a2fb5
Ned Deily added the comment:
New changeset 78e14f8eb4b4a96d0766f2857c00de21d3303b17 by Ned Deily (Miss
Islington (bot)) in branch '3.7':
bpo-32878: Adds documentation for st_ino on Windows (GH-5764) (#7189)
https://github.com/python/cpython/commit/78e14f8eb4b4a96d0766f2857c00de
Ned Deily added the comment:
FWIW, Issue29589 seems to be an older example of this failure.
--
nosy: +ned.deily
versions: +Python 3.7
___
Python tracker
<https://bugs.python.org/issue33
Ned Deily added the comment:
Can we close this now?
--
___
Python tracker
<https://bugs.python.org/issue33672>
___
___
Python-bugs-list mailing list
Unsub
Ned Deily added the comment:
Thank you all for your input and thank you, Inada-san and Serhiy, for the PRs.
Is there anything more that needs to go in for 3.7.0b5 tomorrow so that this
can be tested before the release candidate? If not, can we now close this
again? If new issues arise
Ned Deily added the comment:
FTR:
> On macOS, readline is provided by libedit.
It *may* be provided by libedit. GNU readline is also commonly used on macOS,
although it is not provided by Apple. The easiest way to tell which is in use
is to examine the __doc__ attribute of the readl
Ned Deily added the comment:
Xiang Zhang, was that on macOS? If so, can someone try on one or more Linux
systems with a Chinese locale? I see the same behavior on Linux but I'm not
sure that I'm testing it properly.
--
___
Pyth
Ned Deily added the comment:
So it's not a macOS-specific issue: editing the title et al accordingly
--
nosy: -ronaldoussoren
title: Chinese characters issue with input() function under Mac OSX -> Chinese
characters issue with input()
Change by Ned Deily :
--
nosy: -ned.deily
___
Python tracker
<https://bugs.python.org/issue33692>
___
___
Python-bugs-list mailing list
Unsubscribe:
Ned Deily added the comment:
> Fix in the 3.5 branch which is not allowed as the branch is in "security
> only" mode.
I think you could appeal to the 3.5 Release Manager that this should go in.
Since the 3.5 docs are only rebuilt manually these days (I think), in the
Ned Deily added the comment:
We have just updated the release schedule for Python 3.7 to include 3.7.0b5,
now available. The 3.7.0 release candidate is now planned for 2018-06-11 with
3.7.0 final to follow on 2018-06-27. We expect 3.7.0 to be adopted quickly but
3.6.x will be still
Change by Ned Deily :
--
nosy: +steve.dower, zach.ware
___
Python tracker
<https://bugs.python.org/issue33711>
___
___
Python-bugs-list mailing list
Unsubscribe:
Change by Ned Deily :
--
nosy: -ned.deily
priority: release blocker ->
versions: -Python 3.7
___
Python tracker
<https://bugs.python.org/issue33470>
___
_
Ned Deily added the comment:
> What's the procedure here? If I backport the fix to the 3.7 branch, will it
> go straight into the 3.7.0 release or will it be deferred to 3.7.1??
"All fixes that have been merged into the 3.7 branch as of cutoff tomorrow
will be in 3.7.0b5
Change by Ned Deily :
--
nosy: +christian.heimes
___
Python tracker
<https://bugs.python.org/issue33729>
___
___
Python-bugs-list mailing list
Unsubscribe:
Ned Deily added the comment:
(As a side note, the macOS Pythons provided by python.org installers should not
behave differently on macOS 10.13 High Sierra since none of them are built with
a 10.13 SDK.)
--
nosy: +davin, pitrou
___
Python tracker
Change by Ned Deily :
--
nosy: +serhiy.storchaka
___
Python tracker
<https://bugs.python.org/issue33738>
___
___
Python-bugs-list mailing list
Unsubscribe:
Ned Deily added the comment:
This is not a security issue so a change would not be applicable to the 3.4 or
3.5 branches, currently in security-fix-only mode.
--
versions: +Python 3.8 -Python 3.4, Python 3.5
___
Python tracker
<ht
Ned Deily added the comment:
Puneet, sorry but this bug tracker is for reporting issues found with the
Python language and its implementation, not for help with programming problems.
Please see the Help page on python.org for suggestions on getting help:
https://www.python.org/about/help
Change by Ned Deily :
--
nosy: +gregory.p.smith
___
Python tracker
<https://bugs.python.org/issue33650>
___
___
Python-bugs-list mailing list
Unsubscribe:
Change by Ned Deily :
--
keywords: +easy
nosy: +orsenthil
versions: +Python 3.7, Python 3.8
___
Python tracker
<https://bugs.python.org/issue33663>
___
___
Pytho
Ned Deily added the comment:
Have you run "xcode-select --install" to ensure system header files are
installed? If so, what compiler are you using from what source? What version
of macOS are you using?
https://devguide.python.org/setup/#macos
--
nosy:
Ned Deily added the comment:
Clicking on the Messages tab:
https://ci.appveyor.com/project/python/cpython/build/3.8build16878/messages
"Build exceeded allowed resource quotas. Fix your build to consume less
resources or contact AppVeyor support to request quotas increase."
-
Ned Deily added the comment:
Looks like this was another case of test_mmap on Windows taking a long time.
If the change has now been made to disable tests with "largefile" resources,
test_mmap should no longer be a hangup.
--
___
Pyth
Ned Deily added the comment:
We discussed this earlier: https://bugs.python.org/issue33355#msg317587
--
___
Python tracker
<https://bugs.python.org/issue33
Ned Deily added the comment:
New changeset 47a6c79f0986ce9a84d0efc3c565b28255042911 by Ned Deily (Zachary
Ware) in branch 'master':
bpo-33764: Appveyor fixes (GH-7364)
https://github.com/python/cpython/commit/47a6c79f0986ce9a84d0efc3c565b2
Ned Deily added the comment:
New changeset 37343a2db8763a114e63ac63a249603b1df2554d by Ned Deily (Miss
Islington (bot)) in branch '3.7':
bpo-33764: Appveyor fixes (GH-7364) (GH-7369)
https://github.com/python/cpython/commit/37343a2db8763a114e63ac63a24960
Ned Deily added the comment:
Sorry, I can't reproduce it and I do not recall every seeing a failure like
that.
Just to be sure, you do mean ".configure" and not "./configuration"?
Perhaps you are picking up an old, third-party version of libutil from
/usr/lo
Ned Deily added the comment:
Steve, what do you think about a similar change to the VSTS Windows CI builds
to disable the "longfile" resource for the tests? test_mmap seems to take a
long time.
--
nosy: +steve.dower
___
Python track
Ned Deily added the comment:
New changeset e36837cb71032ccfa713e75623b314f091dc22bb by Ned Deily (Serhiy
Storchaka) in branch 'master':
bpo-33760: Fix file leaks in test_io. (GH-7361)
https://github.com/python/cpython/commit/e36837cb71032ccfa713e75623b314f091dc22bb
-
Ned Deily added the comment:
New changeset 7cfd8c6a1b53a7dbdea14b6f414f2629dcd130a2 by Ned Deily (Serhiy
Storchaka) in branch 'master':
bpo-33759: Fix test.test_xmlrpc.ServerProxyTestCase. (GH-7362)
https://github.com/python/cpython/commit/7cfd8c6a1b53a7dbdea14b6f414f26
Ned Deily added the comment:
That change should not have affected the macOS build. Now that you have a
working python, can you please run:
./python.exe -m test.pythoninfo
and report the results here?
--
___
Python tracker
<ht
Ned Deily added the comment:
New changeset 4d11fe7cad9e138423e16338c88908f24a55f1cf by Ned Deily (Miss
Islington (bot)) in branch '3.7':
bpo-33760: Fix file leaks in test_io. (GH-7361) (GH-7370)
https://github.com/python/cpython/commit/4d11fe7cad9e138423e16338c88908
Ned Deily added the comment:
New changeset 7453caedbb42dd16e069dd08009f0317f7a9abc9 by Ned Deily (Miss
Islington (bot)) in branch '3.7':
bpo-33759: Fix test.test_xmlrpc.ServerProxyTestCase. (GH-7362) (GH-7371)
https://github.com/python/cpython/commit/7453caedbb42dd16e069dd08009f03
Ned Deily added the comment:
New changeset d18b13d36a22f93050a9d7cdfce594002f69236f by Ned Deily (Miss
Islington (bot)) in branch '3.6':
bpo-33760: Fix file leaks in test_io. (GH-7361) (GH-7372)
https://github.com/python/cpython/commit/d18b13d36a22f93050a9d7cdfce594
Ned Deily added the comment:
New changeset 2e601c54d9d5f03f1fe1f7b4a1f2cb8e843fdeae by Ned Deily (Serhiy
Storchaka) in branch '3.6':
[3.6] bpo-33759: Fix test.test_xmlrpc.ServerProxyTestCase. (GH-7362) (GH-7375)
https://github.com/python/cpyt
Ned Deily added the comment:
New changeset b02ceb57d23c26acab3a9f4c5b7d84d0ea0a by Ned Deily (Serhiy
Storchaka) in branch '2.7':
[2.7] bpo-33760: Fix file leaks in test_io. (GH-7361). (GH-7373)
https://github.com/python/cpython/commit/b02ceb57d23c26acab3a9f4c5b
Ned Deily added the comment:
New changeset 93ba6da27eed980600a874dfeffb2856fe1d4126 by Ned Deily (Serhiy
Storchaka) in branch '2.7':
[2.7] bpo-33759: Fix test.test_xmlrpc.ServerProxyTestCase. (GH-7362) (GH-7374)
https://github.com/python/cpyt
Ned Deily added the comment:
The only really suspicious thing I see is that your shell PATH is *gigantic*.
pulling things in from all over the place including Homebrew. If you want to
pursue further, suggest you try a clean build from the tarball without the
modification and use a simple
Ned Deily added the comment:
As I said, I do not recall ever seeing a failure like this before and I
regularly build and test Python on macOS in many different versions and
environments. It would be very time-consuming to try to debug your environment
remotely, time that would be better
Change by Ned Deily :
--
pull_requests: +7006
___
Python tracker
<https://bugs.python.org/issue33764>
___
___
Python-bugs-list mailing list
Unsubscribe:
Change by Ned Deily :
--
pull_requests: +7007
___
Python tracker
<https://bugs.python.org/issue33764>
___
___
Python-bugs-list mailing list
Unsubscribe:
Ned Deily added the comment:
New changeset 1cbdbf35db16f2b06c0974b711c4d8b840c8a264 by Ned Deily in branch
'2.7':
bpo-33764: Appveyor fixes (GH-7364) (GH-7380)
https://github.com/python/cpython/commit/1cbdbf35db16f2b06c0974b711c4d8
Ned Deily added the comment:
New changeset b8f2fb52007f6d0d9eacfb459a9e813678f55f7e by Ned Deily in branch
'3.6':
bpo-33764: Appveyor fixes (GH-7364) (GH-7379)
https://github.com/python/cpython/commit/b8f2fb52007f6d0d9eacfb459a9e81
Ned Deily added the comment:
New changeset e292b75e3ecdc6bbe81cda09de836dc9e27ab9e6 by Ned Deily (Victor
Stinner) in branch 'master':
bpo-33509: Fix test_warnings for python3 -Werror (GH-7365)
https://github.com/python/cpython/commit/e292b75e3ecdc6bbe81cda09de836d
Ned Deily added the comment:
> My understanding is that all changes including this one in 3.7 branch will
> end up in 3.7.0rc1, right?
Yes. Don't worry, the train won't leave without it.
--
___
Python tracker
<https://bugs.py
Ned Deily added the comment:
Thanks for the fix! Since it apparently does not apply to 3.6, we should just
close it like any other issue, right? So doing!
--
priority: release blocker ->
resolution: -> fixed
stage: patch review -> resolved
status: open
Ned Deily added the comment:
Setting to deferred blocker for evaluation
--
nosy: +inada.naoki, ncoghlan, ned.deily
priority: normal -> deferred blocker
versions: +Python 3.8
___
Python tracker
<https://bugs.python.org/issu
Ned Deily added the comment:
Steve, I'm OK with the proposed reduction as a workaround. We have other
platform- and build-specific limits based on stack sizes etc. It's hard to
have one-size-fits-all.
--
___
Python track
Ned Deily added the comment:
> I guess at this stage you're manually cherry-picking into your own 3.7 branch
> for release?
No, not until 3.7.0rc1 next week. No need to cherry pick. Thanks!
--
___
Python tracker
<https://b
Ned Deily added the comment:
{Note: this is not particularly relevant to the issue here.)
Ronald:
> In the long run the macOS installers should be build using the latest SDK
> [...] That's something that would require some effort though to ensure that
> the resulting binary
Ned Deily added the comment:
Thank you for looking into it! In the example you chose, I think the first
step would be to trim the two two-paragraph news items to be only one paragraph
each; in general, news items should only be a few sentences at most. With that
change, I think the choice
Ned Deily added the comment:
With the workaround merged for 3.7.0rc1, I'm downgrading from "release blocker"
to "high" since I believe Steve wants to keep this issue open for a possible
compiler resolution.
--
priority
3701 - 3800 of 6927 matches
Mail list logo