Chris Jerdonek added the comment:
I guess this isn't limited just to the raise from syntax. It also occurs if
from exc is removed from the example above.
--
title: unittest swallows part of stack trace using raise from with
AssertionError - unittest swallows part of stack trace when
Changes by Chris Rebert pyb...@rebertia.com:
--
nosy: +cvrebert
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue23597
___
___
Python-bugs-list
New submission from Chris Hogan:
Setup.py evaluates what's given in LDFLAGS and CPPFLAGS and CFLAGS. These
variables are the usual mechanism to communicate custom paths/libs/defs to a
build process. However, setup.py puts system paths in front of custom paths
which makes it impossible to use
chris laws added the comment:
I have updated the patch to address comments raised by haypo.
An exception is now raised if reuse_port is explicitly used and the platform
does not support SOREUSEPORT. The docs have also been updated to make it more
explicit that this feature is not supported
Chris Hogan added the comment:
Here's a change that might fix the trailing backslash problem for now without
breaking anything. libpath-fix.patch only affects arguments that we know are
paths. This happens before anything is quoted.
This avoids the problem when something like 'C:\path
Chris Hogan added the comment:
I think ensure_relative is incorrect. The comment in the function states:
Take the full path 'path', and make it a relative path. This is useful to
make 'path' the second argument to os.path.join().
However, according to the docs for os.path.join
Chris Hogan added the comment:
Since issue 8972 has been resolved by fixing the broken behavior, I think we
should just use list2cmdline.
We could leave _nt_quote_args alone and replace the call to it in _spawn_nt
with:
cmd = [list2cmdline([arg]) for arg in cmd]
I verified
Changes by Chris Hogan christopher.ho...@intel.com:
Added file: http://bugs.python.org/file40205/quote-args-ext.tar.gz
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue8987
Chris Hogan added the comment:
At Intel, we've run into problems with external modules giving paths to
_nt_quote_args that contain trailing backslashes, which escapes the final quote
and breaks the command. This fix takes care of special characters, trailing
backslashes, and embedded quotes
Chris Hogan added the comment:
From Clark Nelson:
In my opinion, exactly how and where the macro is defined that indicates our
conformance to the FP standard
doesn't really matter. The point is that it is our intention to conform, at
least to some degree and under
some circumstances
Chris Hogan added the comment:
Producing NaN by Py_HUGE_VAL / Py_HUGE_VAL as in the suggested patch is unsafe
as it can generate a FP exception during runtime. Also aggresive compiler FP
optimizations can eliminate this calculation on compile-time. For this reason,
we've used constant
New submission from Chris Rebert:
There is a cross-reference to namedtuple in SimpleNamespace's docs, but not
vice-versa, despite these types being fairly similar.
--
assignee: docs@python
components: Documentation
messages: 248389
nosy: cvrebert, docs@python
priority: normal
severity
Chris Brennan added the comment:
This bug appears (for me) when I use longer install paths, both in the GUI
installer and doing a silent install via msiexec. The paths I've used so far
are these:
E:\langs\Python\x32\27
E:\langs\Python\x32\34
E:\langs\Python\x64\27
E:\langs\Python\x64\34
E
New submission from Chris Jerdonek:
When newlines are present, the error message displayed by unittest's
self.assertEqual() to show where strings differ can be nonsensical. For
example, the caret symbol can show up in a strange location.
The first example below shows a case where things work
Chris Angelico added the comment:
Ah. It's one of *those* bugs. Got it.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue24707
___
___
Python-bugs
Chris Smowton added the comment:
Created #24706 to describe the unflushed connection problem.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue23906
Chris Smowton added the comment:
Why wouldn't that fix the problem? The issue is poplib not tolerating server
behaviour seen in the wild, and if you limit by message size not line length
you shouldn't see this problem?
(Side note, I'm surprised not to have been emailed when you replied, any
New submission from Chris Smowton:
As mentioned in #23906, when poplib bails from receiving a message with a 'line
too long' error it neither flushes nor re-establishes the TCP connection. This
means that subsequent commands fail because instead of the expected response we
receive part
Chris Angelico added the comment:
The host is running Debian Jessie (newer than the Debian Wheezy of the VM).
Linux sikorsky 3.16.0-4-amd64 #1 SMP Debian 3.16.7-ckt9-3~deb8u1 (2015-04-24)
x86_64 GNU/Linux
What info are you after re hardware virtualization?
VirtualBox 4.3.28 r100309 manages
Changes by Chris Rebert pyb...@rebertia.com:
--
nosy: +cvrebert
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue24668
___
___
Python-bugs-list
Chris Mattmann added the comment:
Hi there, we are experiencing this in tika-python too, see:
https://github.com/chrismattmann/tika-python/issues/44
--
nosy: +chrismattmann
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue23054
New submission from Chris Krycho:
There is no `ensurepip` module bundled with the embedded distribution of Python
3.5 for Windows:
Z:\python-3.5.0b3-embed .\python -m ensurepip --upgrade
Z:\python-3.5.0b3-embed\python.exe: No module named ensurepip
This may be the *intent*, but I
Chris Krycho added the comment:
Using --root or --target (as appropriate to the specific package) does appear
to be the preferred approach for that, and given the constraints of an embedded
installation, I agree that that's the most reasonable solution. I spent a fair
bit of time reading up
chris laws added the comment:
Attached is a patch that implements the suggested solution along with tests and
associated doc updates. Hope this helps.
--
keywords: +patch
Added file: http://bugs.python.org/file39930/23972_cjl.patch
___
Python
Chris Smowton added the comment:
+1 to the above; suggest this should be rolled back and replaced with a total
message size limit.
--
nosy: +Chris Smowton
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue16041
Chris Smowton added the comment:
I found the same problem retrieving mail from my ISP's (unknown) POP3 server. I
was sent an HTML email as one long 50KB line, which naturally broke everything.
Instead of limiting line length, I suggest you should limit total message body
size, since that's
chris laws added the comment:
I encountered this issue too. I needed it resolved ASAP for my work so I
created a loop patch that partially implements the suggestion solution by
overriding the create_datagram_endpoint method. Perhaps this might be of some
use to the eventual ticket resolver
Chris Angelico added the comment:
Interestingly, the 2.7 docs have this correct already.
https://docs.python.org/2.7/reference/expressions.html#id23
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue24610
New submission from Chris Angelico:
https://docs.python.org/3/reference/expressions.html#id18
The string \u0327\u0043 does not normalize to the same string as \u00C7, as
combining characters are supposed to _follow_ the base character. (Some
consoles may happen to display them the same way
Chris Angelico added the comment:
Another good option is read/write without the 'fd' suffix. Either works, I'd
prefer the shorter one but by a small margin.
--
nosy: +Rosuav
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue24536
New submission from Chris Angelico:
Grammar/Grammar points to PEP 306, which points instead to the dev guide. The
exact link is not provided, but it'd be useful to skip the PEP altogether and
just link to https://docs.python.org/devguide/grammar.html in the file.
--
messages: 245180
Chris Angelico added the comment:
Weird. Tests ran fine on my machine too. Interestingly, that number is
0xdbdbdbdbdbdbdbda - does that mean anything? (It's negative
0x2424242424242426, for what that's worth.)
--
___
Python tracker rep
Chris Angelico added the comment:
Thanks everyone for all the help getting this to land! This is going to be a
part of my active python3 binary from now on :)
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue22906
Chris Angelico added the comment:
The comment was general because I honestly had no idea what was needed still.
All I knew was that the patch seemed to work for me, all tests passing
(including the new one). Thanks for uploading the new patch; it compiles
happily, and I'm running tests now
Chris Angelico added the comment:
You sure can! Take it, deploy it, run the test suite, and then start writing
real code that uses it. When you find a problem, that's what needs help! :)
--
___
Python tracker rep...@bugs.python.org
http
Chris Angelico added the comment:
Stinner, not sure what you mean by first part / second part. Is there a way for
me to withdraw the first two versions of the patch and just keep #37646?
--
___
Python tracker rep...@bugs.python.org
http
Changes by Chris Rebert pyb...@rebertia.com:
--
nosy: +cvrebert
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue24064
___
___
Python-bugs-list
Chris Angelico added the comment:
Had a peek at the 2.7 branch in the web
(https://hg.python.org/cpython/file/4234b0dd2a54/Lib/test) and all the tests
appear to be testing the behaviour *with* the future directive, not bothering
to test the old behaviour. It makes sense - that way, when
Chris Angelico added the comment:
Got around to tracking down where this is actually being done. It's in
Objects/stringlib/codecs.h and it looks to be a hot area for optimization. I
don't want to fiddle with it without knowing a lot about the performance
implications (UTF-8 encode/decode
Chris Angelico added the comment:
Simple test case for the future directive. Needs expansion.
--
Added file: http://bugs.python.org/file39079/test_pep479.py
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue22906
Chris Abiad added the comment:
Running through each of the demos, it seems as though only 'penrose' and 'tree'
have console/shell output.
'penrose' output is a list of information about the current rendering and has a
format like:
Calculation:0.0009 s
Drawing: 0.0074 s
Together: 0.0083
Chris Abiad added the comment:
The original problem was described as:
the character is printed at the start of the current line rather than the
start of the next line.
I haven't gotten too far investigating the cause, but adding a single line to
the sample code makes this test code a bit
Changes by Chris Rebert pyb...@rebertia.com:
--
nosy: +cvrebert
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue23622
___
___
Python-bugs-list
Chris Angelico added the comment:
Nice document. Is that actually how Python's decoder checks things? Does the
decoder have different definitions of valid continuation byte based on the
lead byte? If that's the case... well, ten out of ten for complying with the
spec, to be sure
New submission from Chris Angelico:
b\xed\xb4\x80.decode(utf-8)
Traceback (most recent call last):
File stdin, line 1, in module
UnicodeDecodeError: 'utf-8' codec can't decode byte 0xed in position
0: invalid continuation byte
The actual problem here is that this byte sequence would decode
Changes by Chris Kaynor ckay...@zindagigames.com:
--
nosy: +DragonFireCK
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue23515
___
___
Python-bugs
Changes by Chris Rebert pyb...@rebertia.com:
--
nosy: +cvrebert
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue23342
___
___
Python-bugs-list
Changes by Chris Angelico ros...@gmail.com:
--
nosy: -Rosuav
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue2292
___
___
Python-bugs-list mailing
Chris Angelico added the comment:
*facepalm* Of course I am. I don't know how I missed that in there, but maybe I
was focusing too much on the abort that followed it to actually read the
exception text. Duh.
But with the latest version of the patch, I'm seeing something that I'm fairly
sure
Chris Angelico added the comment:
The third version of the patch is huge compared to the other two. Is it all
important?
I'm seeing a different build failure, and with the size of patch, I'm not sure
I'm well placed to figure out what's going on.
-- cut --
Traceback (most recent call last
Chris Rebert added the comment:
This behavior seems to be required by the General Decimal Arithmetic
Specification (http://speleotrove.com/decimal/daexcep.html ):
The following exceptional conditions can occur:
[...]
Invalid operation
This occurs and signals invalid
Chris Angelico added the comment:
Nick, any particular reason for pointing to
https://hg.python.org/cpython/annotate/bbf16fd024df/Lib/__future__.py rather
than https://hg.python.org/cpython/annotate/tip/Lib/__future__.py ? I'm looking
at both, anyhow
Chris Angelico added the comment:
PyErr_Restore doesn't seem to trigger exception chaining. But thanks for the
tip about explicitly setting the traceback; not sure how I missed that, but now
the StopIteration traceback is visible.
Minor point: The previous patch was setting the __context__
Changes by Chris Angelico ros...@gmail.com:
Added file: http://bugs.python.org/file37641/stopiter.py
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue22906
Chris Angelico added the comment:
I'm not sure what to look for in the code generation. In compile.c lines 3456
and following, there's a LOAD_CONST None coming through, in the else branch of
if (e-v.Yield.value), but nothing talking about lambda functions. There are
constants
Chris Angelico added the comment:
Okay! I think I have something here. DEFINITELY needs more eyeballs, but all
tests pass, including a new one that tests StopIteration leakage both with and
without the __future__ directive. Some docs changes have been made (I grepped
for 'stopiteration
Changes by Chris Angelico ros...@gmail.com:
--
type: - behavior
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue23192
___
___
Python-bugs-list
New submission from Chris Angelico:
As yield is an expression, it's legal in a lambda function, which then
means you have a generator function. But it's not quite the same as
the equivalent function made with def:
$ python3
Python 3.5.0a0 (default:1c51f1650c42+, Dec 29 2014, 02:29:06)
[GCC
Chris Angelico added the comment:
I can have a poke at the __future__ import tonight, but my main concern is
memory management - I'm not sufficiently familiar with the exception handling
calls to be sure that I'm neither leaking nor over-freeing anything. There's
also a secondary concern
New submission from Chris Angelico:
Creating an issue to keep track of a patch, but this probably wants to be
discussed on python-ideas.
The attached patch allows a Python function to be put into sys.__getglobal__,
which then works like __getattr__ but for global names. This allows
Changes by Chris Rebert pyb...@rebertia.com:
--
nosy: +cvrebert
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue19776
___
___
Python-bugs-list
New submission from Chris Jerdonek:
I have observed that when running unit tests using unittest's test discovery,
unittest can simultaneously (1) modify sys.path unnecessarily (by adding a path
that is already in sys.path with a different case), and (2) modify sys.path by
adding a path
New submission from Chris Jerdonek:
The documentation for os.path.normcase(path) is currently confusing or
self-contradictory.
Currently, it reads--
Normalize the case of a pathname. On Unix and Mac OS X, this returns the path
unchanged; on case-insensitive filesystems, it converts the path
New submission from Chris Jerdonek:
pathlib's relative_to(other) can give a confusing message when other is
os.curdir.
For example--
Python 3.4.2 (default, Nov 12 2014, 18:23:59)
[GCC 4.2.1 Compatible Apple LLVM 6.0 (clang-600.0.54)] on darwin
Type help, copyright, credits
Chris Jerdonek added the comment:
By the way, here is another (less) confusing error message:
Path(foo).relative_to(fo)
Traceback (most recent call last):
File stdin, line 1, in module
File
/opt/local/Library/Frameworks/Python.framework/Versions/3.4/lib/python3.4
Chris Jerdonek added the comment:
Was this also fixed for Mac OS X? Mac OS X is also case-insensitive by
default, and on Python 3.4.2 I'm getting:
Path(Foo).relative_to(foo)
Traceback (most recent call last):
File stdin, line 1, in module
File
/opt/local/Library/Frameworks
New submission from Chris Hand:
The current implementation of readline implements the redisplay function, but
not the forced version. This patch maintains the current behavior as the
default, but also allows a bool to be passed which, if True, calls
rl_forced_update_display instead
Chris Rebert added the comment:
WebM's docs use video/webm and never use an application/* type.
See http://www.webmproject.org/docs/container/
They also specify audio/webm for audio-only content, but both use the same
file extension, so associating .webm with video/webm seems quite reasonable
Chris Rebert added the comment:
Yes, the existing patch looks fine.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue16329
___
___
Python-bugs
Chris Rebert added the comment:
Here is a patch that adds the necessary warnings from issue 7950.
Please review it when you get a chance.
--
keywords: +patch
Added file: http://bugs.python.org/file37338/fix-21557.patch
___
Python tracker rep
Chris Rebert added the comment:
Ping. This small patch has been waiting nearly 3 months for a review.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue22356
Chris Angelico added the comment:
Stefan, I'm not sure - I don't know the details of the C API here. But I tried
commenting out everything but that one line, and while it does result in
RuntimeError, it doesn't do the exception chaining. Currently, I believe the
exception isn't being caught
Chris Angelico added the comment:
Yeah, I saw that. Since that function begins with an underscore, I thought it
best to replicate its behaviour rather than to call it. Either way ought to
work though.
--
___
Python tracker rep...@bugs.python.org
Changes by Chris Rebert pyb...@rebertia.com:
--
nosy: +cvrebert
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue22936
___
___
Python-bugs-list
Changes by Chris Rebert pyb...@rebertia.com:
--
nosy: +cvrebert
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue22951
___
___
Python-bugs-list
Chris Rebert added the comment:
Thanks Serhiy!
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue21514
___
___
Python-bugs-list mailing list
Chris Rebert added the comment:
Ping!
Seems like this should be closed since the new RFC explicitly legalizes the
feature in question and since the docs explicitly warn about the
interoperability of the feature.
--
___
Python tracker rep
Chris Angelico added the comment:
Known issues with the current patch, if anyone feels like playing with this who
better knows the code:
1) Needs a __future__ directive to control behaviour
2) test_generators needs to be heavily reworked
3) The test of what exception was thrown needs to also
Chris Angelico added the comment:
Marc, are those all cases where the raise StopIteration is actually inside a
generator? If so, it can be trivially replaced with return. Yes, it'll break
that way of spelling it, but it's a completely mechanical transformation, and
making the change won't
Chris Angelico added the comment:
Yep, the question is whether any of the raise StopIteration lines are
actually non-local flow control. If they're local, then it's easy: mechanical
replacement with return and it becomes compatible with all versions (unless
it has a value attached
Chris Angelico added the comment:
Sadly, I don't know of a way to check if that's the case, other than by
manually going through and eyeballing the code - if there's raise
StopIteration, see if there's also yield in the same function. The three
cited examples are (I checked those straight
New submission from Chris Angelico:
See PEP for full details. Attached is POC patch: behaviour is altered globally
(rather than respecting a __future__ directive), and minimal changes are made
elsewhere to make the test suite mostly pass (test_generators does not - it'll
need more
Chris Rebert added the comment:
Ping! It's been about 3 months since this was given the green light...
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue21514
Chris PeBenito added the comment:
I understand the resistance; I'm fine closing this as won't implement, though
this is not for academic use. In a nutshell, my package currently has a set of
classes to represent an SELinux policy, and the SELinux policy language
represents networks
Chris PeBenito added the comment:
That's unfortunate. The library provides factory functions so v4 and v6
addresses/networks are easily handled together, and yet it seems to have been
overlooked that you can do this:
ipaddress.ip_network('192.168.1.0/255.255.255.0
New submission from Chris PeBenito:
Here:
https://docs.python.org/3/library/ipaddress.html#ipaddress.IPv6Network
In the constructor documentation, item 1 says:
A string consisting of an IP address and an optional mask, separated by a slash
(/). The IP address is the network address
New submission from Chris PeBenito:
Python 3.3/3.4 sometimes does not recognize a legitimate IPv6Network netmask:
$ python3
Python 3.3.5 (default, May 28 2014, 13:56:57)
[GCC 4.7.3] on linux
Type help, copyright, credits or license for more information.
import ipaddress as ip
nodecon
Chris Adams added the comment:
I agree that making the code match the docs would be preferable – an unexpected
KeyError might be easier to track down that way but it'd still surprise most
developers.
re:pwd docs, the formatting in
https://hg.python.org/cpython/file/8e9df3414185/Doc/library
Chris E added the comment:
Whilst in most cases this would be correct, in this case it looks like the
original contributor took a subset of what the original author wrote and put it
into the python libraries.
Until relatively recently the ElementTree.py file included a stanza that
attempted
New submission from Chris Colbert:
This is how the macro is defined in object.h:
2.7
/* Helper for passing objects to printf and the like */
#define PyObject_REPR(obj) PyString_AS_STRING(PyObject_Repr(obj))
3.4
/* Helper for passing objects to printf and the like */
#define PyObject_REPR(obj
Changes by Chris Rebert pyb...@rebertia.com:
--
nosy: +cvrebert
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue22356
___
___
Python-bugs-list
Changes by Chris Rebert pyb...@rebertia.com:
--
nosy: +cvrebert
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue22393
___
___
Python-bugs-list
Chris Lasher added the comment:
int has int.from_bytes and int.to_bytes.
Currently, bytes has bytes.fromhex. Would the core developers please consider
naming the method bytes.tohex instead of bytes.hex, so there's at least a
modicum of consistency in the method names of Python's builtin types
Changes by Chris Lasher chris.las...@gmail.com:
--
nosy: +gotgenes
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue9951
___
___
Python-bugs-list
Chris Rose added the comment:
What's the word on this change?
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue20752
___
___
Python-bugs-list
Changes by Chris Rebert pyb...@rebertia.com:
--
nosy: +cvrebert
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue22189
___
___
Python-bugs-list
Changes by Chris Rebert pyb...@rebertia.com:
--
nosy: +cvrebert
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue22276
___
___
Python-bugs-list
Changes by Chris Rebert pyb...@rebertia.com:
--
nosy: +cvrebert
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue21611
___
___
Python-bugs-list
Chris Angelico added the comment:
Patch applies nicely to current default, and works for me on amd64 Linux. I'm
liking how this is looking.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue8
Changes by Chris Rebert pyb...@rebertia.com:
--
nosy: +cvrebert
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue20779
___
___
Python-bugs-list
701 - 800 of 2739 matches
Mail list logo
