Changes by Zachary Ware :
--
components: -Windows
resolution: -> not a bug
stage: -> resolved
status: open -> closed
title: Bug -> Spam
type: enhancement ->
versions: -Python 2.6
___
Python tracker
<http://bugs.pyt
Zachary Ware added the comment:
So the mystery of that buildbot is solved, but I think that test needs some
work.
--
keywords: +buildbot
nosy: +alex, christian.heimes, dstufft, giampaolo.rodola, janssen, pitrou
stage: -> needs patch
___
Pyt
Zachary Ware added the comment:
I wonder if it's worth a ..versionchanged note in the namedtuple docs pointing
out that __doc__ assignment on fields only works in 3.5+ due to property
docstrings becoming writable.
--
nosy: +zach.ware
stage: ->
Changes by Zachary Ware :
--
title: Update the documentation to 3.5 -> Update the devguide to 3.5
___
Python tracker
<http://bugs.python.org/issue25704>
___
_
Zachary Ware added the comment:
Fixed in f7283190e896.
I had actually already fixed this in my sandbox repo for speed.python.org; I
just went ahead and pushed it (and a couple other very minor changes) to the
main benchmark repo.
Thanks for the report and patch!
--
nosy: +zach.ware
Zachary Ware added the comment:
+1
Unless anybody else objects in the next couple days, I'll commit this.
--
nosy: +zach.ware
stage: -> commit review
versions: -Python 2.7
___
Python tracker
<http://bugs.python.org
Zachary Ware added the comment:
This broke test_xpickle with python 2.4 and 2.5 due to 'b' prefixes and an
import that's not actually used in the 2.7 patch; now fixed. The
ware-gentoo-x86 buildslave now has pythons 2.4, 2.5, and 2.6 installed for
test_xpickle to use.
Zachary Ware added the comment:
Here's a patch to try to modernize the whole section a bit, and to remove one
of the two other instances of 'Python35' in the docs (the other instance is in
the docs for pyvenv, which needs its own overhaul in a separate issue).
--
keywor
Zachary Ware added the comment:
Done. Thanks, Florin!
--
resolution: -> fixed
stage: commit review -> resolved
status: open -> closed
___
Python tracker
<http://bugs.python.or
Zachary Ware added the comment:
Thanks for the report!
--
nosy: +zach.ware
___
Python tracker
<http://bugs.python.org/issue25767>
___
___
Python-bugs-list mailin
New submission from Zachary Ware:
Here's a patch to the benchmarks repo that allows running a benchmark on a
single interpreter and returning raw data, and provides a script to upload the
raw data to a codespeed instance. It's a bit of a quick hack, but is effective.
This is a pr
Zachary Ware added the comment:
Left one minor comment on Rietveld.
However, I'm not yet convinced that this is a bug in Python. I can't find an
authoritative source to say whether \0 is valid in a REG_SZ value, but the fact
that you can set one and get it back makes me think
Zachary Ware added the comment:
> Is it possible that Python 2 is using a non-unicode Windows API to get the
> values
It does, but according to Anshul's nullcheck2.py output that doesn't matter.
--
___
Python tracker
<htt
Zachary Ware added the comment:
So then this is actually matplotlib's bug: Python is returning the blob as it
should, but matplotlib is assuming too much about what it contains. However, I
suspect that this particular issue isn't entirely matplotlib's fault; it looks
to me l
Zachary Ware added the comment:
There's also backward compatibility to consider here; someone somewhere is
depending on getting back \0 in his REG_SZes. If we were to make a change, it
could only go in 3.6. With that restriction, I don't see a particularly nice
way to get the sam
Zachary Ware added the comment:
Ok, that example is an argument I'll accept.
I'll give the patch another couple of days for others to review, and commit if
nobody beats me to it. It's too late for 3.5.1, but it can probably make 3.4.4.
--
stage: patch review -> comm
Zachary Ware added the comment:
Hmm, oops. This would be a result of 3aec776fc796, which was applied only to
the default before 3.5 was branched.
--
stage: -> needs patch
type: -> behavior
versions: +Python 3.5
___
Python tracker
Changes by Zachary Ware :
--
title: test_fork1 cannot be run directly: ./pyhon Lib/test/test_fork1.py ->
test_fork1 cannot be run directly: ./python Lib/test/test_fork1.py
___
Python tracker
<http://bugs.python.org/issu
Changes by Zachary Ware :
--
resolution: -> not a bug
stage: -> resolved
status: open -> closed
___
Python tracker
<http://bugs.python.org/issue25039>
___
___
Zachary Ware added the comment:
STINNER Victor added the comment:
> Can you please check if the branch 3.5 is impacted?
It is.
--
___
Python tracker
<http://bugs.python.org/issu
Zachary Ware added the comment:
I'd rather leave things as they were, just add ', main as unittest_main' to the
existing 'from unittest import TestCase' and change the call at the end from
'unittest.main()' to 'unittest_main()'.
Felippe, have yo
Zachary Ware added the comment:
I made the change to test_pyclbr that I mentioned and committed it. Thanks,
Fellipe!
--
___
Python tracker
<http://bugs.python.org/issue25
Changes by Zachary Ware :
--
versions: +Python 3.4
___
Python tracker
<http://bugs.python.org/issue25800>
___
___
Python-bugs-list mailing list
Unsubscribe:
Zachary Ware added the comment:
Thanks for the report!
--
type: -> behavior
___
Python tracker
<http://bugs.python.org/issue25800>
___
___
Python-bugs-list mai
Changes by Zachary Ware :
--
keywords: +buildbot
nosy: +zach.ware
stage: -> needs patch
versions: -Python 3.2, Python 3.3, Python 3.4
___
Python tracker
<http://bugs.python.org/issu
Changes by Zachary Ware :
--
stage: -> resolved
___
Python tracker
<http://bugs.python.org/issue25815>
___
___
Python-bugs-list mailing list
Unsubscrib
Zachary Ware added the comment:
Also, if you only need to support Python 2.6+, you can use 'from __future__
import print_function' and get all the benefits of 'print' as a function in
Python 2 (except the 'flush' argument, which was added in Python 3.3)
Changes by Zachary Ware :
--
components: +Windows
nosy: +paul.moore, steve.dower, tim.golden, zach.ware
___
Python tracker
<http://bugs.python.org/issue25
Zachary Ware added the comment:
Eryk is correct, there should be no -32 suffix in 2.7. It's simple enough to
fix, just remove the last line Eryk quoted (and purge generated files from PC/).
This is a pretty major bug; Benjamin and Steve, how do you want to deal with it?
--
compo
Changes by Zachary Ware :
--
stage: -> resolved
type: crash -> behavior
___
Python tracker
<http://bugs.python.org/issue25826>
___
___
Python-bugs-list
New submission from Zachary Ware:
Attached is a patch that adds support for ICC to configure, making it easier to
build with ICC on Unix and adjusting arguments to better fit ICC.
- Adds '--with-icc' argument to configure, which sets 'CC=icc' and 'CXX=icpc
Zachary Ware added the comment:
Responded on python-list.
--
resolution: -> not a bug
stage: -> resolved
status: open -> closed
___
Python tracker
<http://bugs.python.or
Zachary Ware added the comment:
Right, I should have been more specific here. Sorry about that.
--
___
Python tracker
<http://bugs.python.org/issue25842>
___
___
Zachary Ware added the comment:
I'm inclined to close this as 'not a bug'. There's not much we can do about
that (if you want 64 bit extensions, you need a 64 bit compiler), and 2015
Community Edition does include the 64 bit compiler (if you select it).
I'm not sure
Changes by Zachary Ware :
--
versions: +Python 3.4, Python 3.5, Python 3.6 -Python 3.1, Python 3.2, Python
3.3
___
Python tracker
<http://bugs.python.org/issue12
Zachary Ware added the comment:
In which direction do you find us to be mad?
--
___
Python tracker
<http://bugs.python.org/issue25847>
___
___
Python-bugs-list m
Zachary Ware added the comment:
I think Ezio's suggestion of a sentinel value would be better, allowing None to
be using as a legitimate 'message' [1]. That is, somewhere at global scope,
define '_subtest_msg_sentinel = object()', change the msg default at
Lib/unitte
Zachary Ware added the comment:
At this point our MSBuild project files are hand-crafted, and are best edited
by hand. You can use the GUI to get a general idea of what the changes should
be, but it just creates far too much spam to really be usable.
This should be about a 2 line change, but
New submission from Zachary Ware:
The title can barely be called accurate; the description of the problem isn't
easy to condense to title length. Here's the issue:
$ cat subtest_test.py
import os
import unittest
class TestClass(unittest.TestCase):
def test_subTest(self):
Zachary Ware added the comment:
Martin Panter added the comment:
> Okay, so you have a test with subtests. You have presented three cases:
>
> 1. Single subtest which passes. No problem I assume.
Or several subtests which pass. No problems.
> 2. Two subtests: 1st fails, 2nd pas
Zachary Ware added the comment:
After testing, I think I like '-fp-model strict' better in CFLAGS_NODIST. On
Ubuntu, `CC=gcc ./python -m test.test_distutils` passes when the flag is in
CFLAGS_NODIST, but fails when it's in BASECFLAGS. On OSX, it fails both ways,
due to de
Zachary Ware added the comment:
This one is officially weird.
I can reliably reproduce the segfault in test_ascii_formatd on OSX with ICC 15
or 16, using the included libffi in Modules/_ctypes/libffi_osx. There are also
segfaults in test_ctypes, test_multiprocessing, and test_threading (all
Changes by Zachary Ware :
--
components: +Windows
nosy: +paul.moore, steve.dower, tim.golden, zach.ware
___
Python tracker
<http://bugs.python.org/issue25
Zachary Ware added the comment:
Larry: considering that 3.4 is now officially out of bugfix mode, how long do
you want to keep the 3.4 buildbots around? From a selfish buildmaster
configurator perspective, axing the 3.4 bots simplifies a few things
Zachary Ware added the comment:
I like Serhiy's suggestion to use the old walk implementation on Windows if the
argument is bytes, with a DeprecationWarning (like all other bytes operations
in os on Windows). There was no warning that bytes paths would stop working
with os.walk, so we s
Changes by Zachary Ware :
--
nosy: +zach.ware
___
Python tracker
<http://bugs.python.org/issue4709>
___
___
Python-bugs-list mailing list
Unsubscribe:
Zachary Ware added the comment:
That's alright, it'll be here whenever you come back to it, unless
somebody else takes it up :)
By the way, my wording was poor in my previous message. My 'hundreds
of lines of spam' remark was not meant to disparage your patch, but
ra
Zachary Ware added the comment:
The buildbots appear to be happy with this, so I'm closing the issue. The
intel-ubuntu-icc Non-Debug builders each had their first green build after this
changeset. The OSX ICC builder still has some issues, but they seem to be OSX
specific (see issue
Zachary Ware added the comment:
The project file was moved to PC/bdist_wininst/bdist_wininst.vcxproj. See
55e5be11264e. It's still included in the build solution, but not in the
project used for building from the command line.
--
nosy: +zach.ware
resolution: -> not a b
Zachary Ware added the comment:
Left a couple of review comments on Rietveld.
--
nosy: +zach.ware
stage: -> patch review
___
Python tracker
<http://bugs.python.org/issu
Zachary Ware added the comment:
Would pretty much eliminate the benefit; there are currently a few special
cases for 3.4 (particularly for the ICC builders, and the XP bot), which could
go away.
For the record, the secret undocumented method for running a build on all
custom builders is to
Zachary Ware added the comment:
I think only keeping some builders would be more complex than any other option.
Here's a patch against pep101 to document the custom builder trick.
--
keywords: +patch
Added file: http://bugs.python.org/file41389/pep101_custom_buildbots
Zachary Ware added the comment:
I have no idea how you got a curl.exe there, but it didn't come from our
installer. Where did you get your 3.5.1 installer from?
--
resolution: -> not a bug
stage: -> resolved
status: open -> closed
Zachary Ware added the comment:
Unfortunately, #25827 has no effect on Windows, which is where this issue
occurs. There are still several segfaults on Windows, including test_re.
--
___
Python tracker
<http://bugs.python.org/issue24
Zachary Ware added the comment:
ctypes in the test suite is fine, just be sure it's guarded properly (with
either `ctypes = test.support.import_module("ctypes")` or `if sys.platform ==
'win32'): ...`.
--
___
Python tracker
Zachary Ware added the comment:
Just some missing parentheses, so I fixed it:
http://buildbot.python.org/all/builders/AMD64%20Windows7%20SP1%203.x/builds/7116
--
components: +Build
resolution: -> fixed
stage: -> resolved
status: open -> closed
type: -> compile er
Zachary Ware added the comment:
Missed the boat on 3.4.
I tried out the new test on 2.7, and it does not fail with no change to
_winreg.c. Eryk, do you want to provide a patch for 2.7? I'm not interested
enough to figure out what's going on there, but if you provide a patch I
Zachary Ware added the comment:
Here's a patch that folds PGO into PCbuild\build.bat (removing
PCbuild\build_pgo.bat) and defaults to using "python -m test --pgo" for
training. This should apply to all branches, but will need some slight
adjustment for 2.7 (namely, s/-m test/-
Zachary Ware added the comment:
I'd also suggest using double quotes ("); single quotes don't work on Windows.
C:\>echo 'test>=test'
C:\>dir /b test*
test'
C:\>type "test'"
'test
--
nosy: +zach.ware
_
Zachary Ware added the comment:
Glad you got it figured out. It's a situation that can be tricky to debug, as
your eyes tend to gloss over the paths given in the traceback. It's much
easier to figure out after you've been bitten the first time, though!
--
nosy: +
Zachary Ware added the comment:
Just like it says, you need Service Pack 1 for Python 3.5. If for some reason
that's not possible, you'll have to revert back to Python 3.4.
--
nosy: +zach.ware
resolution: -> not a bug
stage: -> resolved
status: open -> closed
Zachary Ware added the comment:
Terry, it doesn't look like you used Upendra's patch. What you committed just
removes the "of", but doesn't change "addition" to "additional", which is also
required to make that sent
Zachary Ware added the comment:
I'm on the fence about this one. MSVC 12.0 is not officially supported for any
Python release. Also, using PlatformToolset makes things difficult for ICC
builds (which set PlatformToolset to e.g. "Intel C++ Compiler 16.0").
On the other hand,
Zachary Ware added the comment:
The fewer patches we carry against Tcl/Tk the better. This can be
revisited if necessary when other ICC issues with our Tcl/Tk build are
fixed.
--
___
Python tracker
<http://bugs.python.org/issue26
Zachary Ware added the comment:
Thanks for the review, Steve.
--
assignee: brett.cannon -> zach.ware
___
Python tracker
<http://bugs.python.org/issu
Changes by Zachary Ware :
--
nosy: +curioswati
___
Python tracker
<http://bugs.python.org/issue25913>
___
___
Python-bugs-list mailing list
Unsubscribe:
Zachary Ware added the comment:
Go for it :)
--
___
Python tracker
<http://bugs.python.org/issue25778>
___
___
Python-bugs-list mailing list
Unsubscribe:
Zachary Ware added the comment:
This isn't obviously a distutils bug, but sounds strikingly similar to #4508.
Closing as a duplicate of #4508.
--
assignee: eric.araujo ->
nosy: +zach.ware
resolution: -> duplicate
stage: needs patch -> resolved
status: open ->
Zachary Ware added the comment:
It's not easy to find anything with a google search for 'ffi_convenience'
that's not this issue. I did find doko's patch to GCC to not install
libffi_convenience, which included a comment from the author of libffi saying
he didn
Zachary Ware added the comment:
I've been doing some research on this, the below is pretty much a brain-dump.
Related issues: issue232609, issue420565, issue10520.
This looks to me like the ideal solution is to assign a priority to each entry
and sort by that priority before using it;
Zachary Ware added the comment:
I'm a bit concerned that the flags are being added unconditionally to CFLAGS
and LDFLAGS (when configured --with-lto), which means extensions are forced
into it as well. I think it would be better to use CFLAGS_NODIST and to add
LDFLAGS_NODIST. Unfortun
Zachary Ware added the comment:
PGO is available as `make profile-opt`, LTO has a patch in issue25702. Are
there any other interesting options worth investigating?
--
nosy: +zach.ware
status: open -> pending
___
Python tracker
&l
Zachary Ware added the comment:
I've looked into this a bit, and tests won't pass with MSVC /fp:strict, so it
would need to be ICC specific. UNIX ICC builds do unconditionally use
-fp-model strict now, though, so I think Windows ICC builds shou
Zachary Ware added the comment:
Unless I'm just missing something, I don't see how introducing CFLAGS_NODIST
and LDFLAGS_NODIST to 2.7 would introduce instability. It should be a fairly
non-invasive change, restricted to configure and the Makefile; both vars should
usually be empt
Zachary Ware added the comment:
Committed (with a couple minor tweaks), thanks for the patch!
--
resolution: -> fixed
stage: patch review -> resolved
status: open -> closed
___
Python tracker
<http://bugs.python.or
Zachary Ware added the comment:
Ah, it's been a while since I tested that, so my reporting was inaccurate. The
problem is actually that the compile fails:
..\Modules\mathmodule.c(1924): error C2099: initializer is not a constant
[C:\cpython\PCbuild\pythoncore.vcxproj]
..\Modules\mathmod
Zachary Ware added the comment:
I don't believe this is a bug.
1) try/except does not introduce a new scope
2) 'except E as N' is just name assignment
3) except clauses are documented to always delete the exception alias at the
end of the except block[0]. The example in th
Zachary Ware added the comment:
Here's a patch that specifies /fp:strict if it looks like ICC is being used for
the build. It also adds a convenient property for checking whether it's an ICC
build ($(ICCBuild)). This doesn't change anything for MSVC builds but allows
ICC
Zachary Ware added the comment:
What version of Python are you using, where did you get it from, and what
version of Windows are you using?
--
components: +Windows
nosy: +paul.moore, steve.dower, tim.golden, zach.ware
___
Python tracker
<h
Zachary Ware added the comment:
In that case, does this patch do what you want it to do?
--
stage: -> patch review
Added file: http://bugs.python.org/file41710/issue24923.diff
___
Python tracker
<http://bugs.python.org/issu
Zachary Ware added the comment:
Steve, I'm assuming you meant "x86_amd64" rather than "x86_arm" on that last
filename?
Note that this issue is restricted to Debug builds (as suggested by the issue
being with mspdb140.dll), the Non-Debu
Changes by Zachary Ware :
--
components: +Windows
nosy: +paul.moore, steve.dower, tim.golden, zach.ware
___
Python tracker
<http://bugs.python.org/issue26
New submission from Zachary Ware:
As reported in msg258685 (issue25934), Python cannot be built with /fp:strict
while using MSVC. As Mark showed in msg258686 and msg258689, there are three
calculations that could be replaced with suitable constants to allow /fp:strict
to be used.
(Nosy list
Zachary Ware added the comment:
With the buildbots not angry over this, I'm closing the issue. I opened #26262
to follow the possibility of changing the initializers to allow /fp:strict with
MSVC.
--
assignee: -> zach.ware
resolution: -> fixed
stage: -> resolve
New submission from Zachary Ware:
http://openssl.org/news/secadv/20160128.txt
--
components: Build, Macintosh, Windows
messages: 259422
nosy: ned.deily, paul.moore, ronaldoussoren, steve.dower, tim.golden, zach.ware
priority: normal
severity: normal
stage: needs patch
status: open
title
Zachary Ware added the comment:
Actually, this one can be closed now, see issue26268.
--
nosy: +zach.ware
resolution: -> fixed
stage: needs patch -> resolved
status: open -> closed
___
Python tracker
<http://bugs.python.or
Zachary Ware added the comment:
Perhaps the ideal approach here would be to pass TMP_DIR and OUT_DIR into the
Tcl/Tk builds, so we can tell them where to put stuff. However, that would
require major surgery to Tix's makefile to get it to build. I'd be +1 on doing
so (since we'
Zachary Ware added the comment:
Fair point, I'll leave out the upload script.
Thanks for the review!
--
___
Python tracker
<http://bugs.python.org/is
Changes by Zachary Ware :
--
resolution: -> fixed
stage: patch review -> resolved
status: open -> closed
___
Python tracker
<http://bugs.python.or
Zachary Ware added the comment:
This is a documented peculiarity of the %p format code, see the '%p' entry in
the table at [1], note 3 in particular.
>>> from datetime import datetime
>>> datetime.strptime('1:00 PM', '%H:%M %p').hour
1
>>&
Zachary Ware added the comment:
I added the note to the devguide instead of pep101, and will be removing the
3.4 builders shortly.
--
resolution: -> out of date
stage: -> resolved
status: open -> closed
___
Python tracker
<http://bug
Zachary Ware added the comment:
OpenSSL seems to have FUBARed their release process, such that the include/
directory no longer includes anything. As such I had to update prepare_ssl.py
to handle creating include directories for 32 and 64 bit. This is somewhat
wasteful since the only thing
Zachary Ware added the comment:
I suspect this may be what causes several of the 2.7 builders to fail. The
ones that fail look like they complete successfully, but then sit with no
output until buildbot kills them.
For example:
http://buildbot.python.org/all/builders/AMD64%20Debian%20PGO
Zachary Ware added the comment:
Attaching regenerated patch to coax Rietveld into accepting it for easier
review.
--
nosy: +zach.ware
Added file: http://bugs.python.org/file42058/issue26462_regen.diff
___
Python tracker
<http://bugs.python.
Changes by Zachary Ware :
--
nosy: +zach.ware
___
Python tracker
<http://bugs.python.org/issue26470>
___
___
Python-bugs-list mailing list
Unsubscribe:
Zachary Ware added the comment:
I can confirm that child-exit.patch fixes the immediate issue, so I'm +1 on
just committing it since it will make several buildbots useful again.
Improving general handling of the situation can be done in a new issue.
For the record, I agree that this see
Zachary Ware added the comment:
Paul, I think you were in a Python 2 session:
$ python
Python 2.7.10 (v2.7.10:15c95b7d81dc, May 23 2015, 09:33:12)
[GCC 4.2.1 (Apple Inc. build 5666) (dot 3)] on darwin
Type "help", "copyright", "credits" or "license" f
Zachary Ware added the comment:
Steve: This broke 64-bit Windows, I haven't tried digging into what's going on
yet.
See:
http://buildbot.python.org/all/builders/AMD64%20Windows7%20SP1%203.x/builds/7331/steps/compile/logs/stdio
--
resolution: fixed ->
stage: resolv
Zachary Ware added the comment:
I can reproduce on Windows 10 with Pythons 2.7.11, 3.4.4, and 3.5.1 with the
attached script. Examples:
E:\>ver
Microsoft Windows [Version 10.0.10586]
E:\>py ccbug.py
2.7.11 (v2.7.11:6d1b6a68f775, Dec 5 2015, 20:32:19) [MSC v.1500 32 bit (Intel)]
Tra
Changes by Zachary Ware :
--
resolution: -> not a bug
stage: -> resolved
___
Python tracker
<http://bugs.python.org/issue26573>
___
___
Python-bugs-list
2401 - 2500 of 2740 matches
Mail list logo