Tim Tisdall added the comment:
oops. yeah, I got my terminology wrong. It accepts only a byte-string.
--
___
Python tracker
<http://bugs.python.org/issue24
Tim Tisdall added the comment:
Yes, then any existing implementations will continue to work.
One sticky issue with all of this... there's no existing tests as per #7687 .
--
___
Python tracker
<http://bugs.python.org/is
Changes by Tim Tisdall :
--
versions: +Python 3.6
___
Python tracker
<http://bugs.python.org/issue7687>
___
___
Python-bugs-list mailing list
Unsubscribe:
New submission from Tim Tisdall:
When Bluetooth LE support was added to Bluez they expanded sockaddr_l2 (the
struct for making L2CAP connections) to include a l2_bdaddr_type. Since the
existing code initializes the struct with 0's the type is set to regular
Bluetooth (BDADDR_BREDR)
Tim Tisdall added the comment:
Okay, since there's currently no existing tests for the Bluetooth components of
socket and the only example for BDADDR_ALL seems to be for something I'm not
sure you can do in socket, I'm just going to not bother including it.
I've attached
Tim Tisdall added the comment:
okay, I talked to one of the Bluez developers and he recommended leaving out
BDADDR_ALL since it doesn't seem to correspond to anything in the kernel.
--
___
Python tracker
<http://bugs.python.org/is
Tim Peters added the comment:
Stare at footnote 2 for the Reference Manual's "Binary arithmetic operations"
section:
"""
[2] If x is very close to an exact integer multiple of y, it’s possible for
x//y to be one larger than (x-x%y)//y due to rounding. In such cas
Tim Peters added the comment:
> What is the rounding mode used by true division,
For binary floats? It inherits whatever the platform C's x/y double division
uses. Should be nearest/even on "almost all" platforms now, unless the user
fiddles with their FP
New submission from Tim Smith:
In Xcode 7, Apple is replacing many of the .dylibs in SDKROOT with textual
stubs. [1] These files exist on disk with filenames like:
/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.11.sdk/usr/lib/libz.tbd
They are
Changes by Tim Graham :
--
nosy: +Tim.Graham
___
Python tracker
<http://bugs.python.org/issue25137>
___
___
Python-bugs-list mailing list
Unsubscribe:
Tim Peters added the comment:
BTW, I find this very hard to understand:
"it’s possible for x//y to be one larger than" ...
This footnote was written long before "//" was defined for floats. IIRC, the
original version must have said something like:
"it's pos
Changes by Tim Smith :
Added file: http://bugs.python.org/file40479/xcode-stubs-2.7.patch
___
Python tracker
<http://bugs.python.org/issue25136>
___
___
Python-bugs-list m
Tim Graham added the comment:
We can use an alternate approach in Django, if appropriate:
https://github.com/django/django/pull/5294
--
___
Python tracker
<http://bugs.python.org/issue25
Tim Graham added the comment:
It's fine with me.
--
___
Python tracker
<http://bugs.python.org/issue25137>
___
___
Python-bugs-list mailing list
Unsubscr
Tim Golden added the comment:
I'd just bail as early as poss. from the installer. If it's possible to
detect Windows versions, stick something like "The last version to
support WinXP is 3.4". If that's too tricky, perhaps something "Your
system may be unsu
Tim Golden added the comment:
I don't feel that strongly, but my preference would be
"python35[-whatever]" rather than the version with the spaces & the
dots. Both for ease of use and for some kind of continuity with the
c:\pythonxy we&#x
New submission from Tim Graham:
Regression in https://hg.python.org/cpython/rev/9e765e65e5cb (affects 2.7 and
3.2+), similar to issue22931 where inserting an invalid cookie value can cause
the rest of the cookie to be ignored. A test is attached, and here's a quick
demo:
Old:
>
Tim Peters added the comment:
The only way to be certain you're never going to face re-entrancy issues in the
future is to call malloc() directly - and hope nobody redefines that too with
some goofy macro ;-)
In the meantime, stick to PyMem_Malloc(). That's the intended way for cod
Tim Peters added the comment:
I expect Peter is correct: the C fromutc() doesn't match the logic of the
Python fromutc(), and there are no comments explaining why the C version
changed the logic.
The last 4 lines of his `time_issues.py` show the difference. The simplified
UKSumme
Tim Peters added the comment:
Patch looks good to me! Thanks :-)
--
___
Python tracker
<http://bugs.python.org/issue23600>
___
___
Python-bugs-list mailin
Tim Peters added the comment:
Afraid that's a question for python-dev - I lost track of the active branches
over year ago :-(
--
___
Python tracker
<http://bugs.python.org/is
Tim Peters added the comment:
Thank you for your persistence and patience, Peter! It shouldn't have been
this hard for you :-(
--
___
Python tracker
<http://bugs.python.org/is
New submission from Tim Chase:
Attempting to use a readline macro (use "C-x (" to start recording, "C-x )" to
stop recording, and "C-x e" to playback) with more than one newline in it will
cause a segfault. The behavior also presents in the [`rlwrap`
tool](https
Tim Peters added the comment:
You wholly consume the iterator after the first time you apply `list()` to it.
Therefore both `any()` and `all()` see an empty iterator, and return the
results appropriate for an empty sequence:
>>> multiples_of_6 = (not (i % 6) for i in range(1, 10))
Changes by Tim Peters :
--
nosy: +tim.peters
___
Python tracker
<http://bugs.python.org/issue24773>
___
___
Python-bugs-list mailing list
Unsubscribe:
Tim Peters added the comment:
What's your objection? Here's your original example:
>>> from bisect import *
>>> L = [1,2,3,3,3,4,5]
>>> x = 3
>>> i = bisect_left(L, x)
>>> i
2
>>> all(val < x for val in L[:i])
True
Tim Graham added the comment:
It might be a case of issue22983. I'll try to look into the details and offer a
patch next week.
For what it's worth, there are other regressions in Python 3.2 cookie parsing
that makes the latest patch release (3.2.6) unusable with Django (issue22758)
Tim Graham added the comment:
Sure, feel free to propose a patch.
--
___
Python tracker
<http://bugs.python.org/issue25228>
___
___
Python-bugs-list mailin
Tim Graham added the comment:
Could you please integrate my unit test into your patch?
You also need to sign the PSF Contributor Agreement:
https://www.python.org/psf/contrib/contrib-form/
--
___
Python tracker
<http://bugs.python.org/issue25
Tim Graham added the comment:
I had already proposed a test, see cookie-bracket-quotes-test.diff. What I
meant was that the fix and the test should be combined into a single patch.
--
___
Python tracker
<http://bugs.python.org/issue25
Tim Graham added the comment:
Yes, when I have some time.
By the way, did you intentionally remove all the "Python 3.X" versions on the
issue?
--
___
Python tracker
<http://bugs.python.o
Tim Peters added the comment:
This is just hard to believe. The symptom you describe is exactly what's
expected if you got the new test suite but did not compile the new C code, both
added by the fix for:
http://bugs.python.org/issue23600
Since we have numerous buildbots on whic
Changes by Tim Peters :
--
components: +Library (Lib) -Extension Modules, ctypes
resolution: -> not a bug
stage: -> resolved
status: open -> closed
___
Python tracker
<http://bugs.python.or
Tim Peters added the comment:
Do note that this is not an "edit distance" (like Levenshtein) algorithm. It
works as documented instead ;-) , searching (in effect recursively) for the
leftmost longest contiguous matching blocks. Both "leftmost" and "contiguous"
Tim Peters added the comment:
BTW, the "leftmost longest contiguous" bit is messy to explain, so the main
part of the docs don't explain it all (it's of no interest to 99.9% of users).
Instead it's formally defined in the .find_longest_match() docs:
"&q
Changes by Tim Golden :
--
nosy: -tim.golden
___
Python tracker
<http://bugs.python.org/issue25444>
___
___
Python-bugs-list mailing list
Unsubscribe:
Changes by Tim Smith :
--
nosy: +tdsmith
___
Python tracker
<http://bugs.python.org/issue25572>
___
___
Python-bugs-list mailing list
Unsubscribe:
Tim Peters added the comment:
If it were treating doubles as floats, you'd get a lot more failures than this.
Many of these look like clear cases of treating _denormal_ doubles as 0.0,
though. I have no experience with ICC, but a quick Google search suggests ICC
flushes denormals to 0
Tim Graham added the comment:
Given the inactivity here, I guess the patch won't be applied before Python 3.2
is end-of-life so I'm going to close the ticket.
--
resolution: -> wont fix
status: open -> closed
___
Pytho
Changes by Tim Smith :
--
nosy: +tdsmith
___
Python tracker
<http://bugs.python.org/issue24844>
___
___
Python-bugs-list mailing list
Unsubscribe:
Changes by Tim Graham :
--
nosy: +Tim.Graham
___
Python tracker
<http://bugs.python.org/issue25935>
___
___
Python-bugs-list mailing list
Unsubscribe:
Tim Peters added the comment:
Please read the responses to this older report:
http://bugs.python.org/issue25391
As they say, it's functioning as designed and documented, so this isn't "a
bug". For that reason I'm closing this as "not a bug".
As they also
Tim Peters added the comment:
I'd raise an exception when trying to insert into a bounded deque that's
already full. There's simply no way to guess what was _intended_; it's dead
easy for the user to implement what they _do_ intend (first make room by
deleting the s
Tim Peters added the comment:
My opinion doesn't change: I'd rather see an exception. I see no use case for
inserting "into the middle" of a full bounded queue. If I had one, it would
remain trivial to force the specific
Tim Peters added the comment:
+1 from me. Julian, you have the patience of a saint ;-)
--
___
Python tracker
<http://bugs.python.org/issue23601>
___
___
Pytho
Tim Peters added the comment:
If that's the actual code you're using, it has a bug: the "if k2[1] is None"
test is useless, since regardless of whether it's true or false, the next `if`
suite overwrites `retval`. You probably meant
elif k1[1] ...
^^
Tim Peters added the comment:
Right, these macros were in the original module (by Vladimir Marangozov).
They've never done anything - never been tested. Over the years I removed
other layers of macro indirection (while other people added more ;-) ), but
left these alone because they
Tim Peters added the comment:
Do note that `.match()` is constrained to match starting at the first byte.
`.search()` is not (it can start matching at any position), and your example
works fine if `.search()` is used instead.
This is all expected, and intended, and documented
Tim Peters added the comment:
Just noting that the `multiprocessing` module can be used instead. In the
example, add
import multiprocessing as mp
and change
with concurrent.futures.ProcessPoolExecutor() as executor:
to
with mp.Pool() as executor:
That's all it
Tim Golden added the comment:
I haven't tested everywhere but some versions of Windows don't in fact
accept forward slashes on the cmd.exe command line. Suggest changing to
backslashes as there's no reason to do otherwise.
--
no
Tim Peters added the comment:
All versions of cmd.exe want backslashes in paths for the commands implemented
_by_ cmd.exe - those interpret a forward slash as indicating an option. For
example, here on Win10 Pro:
C:\WINDOWS\system32>dir c:\Windows\System32\xwreg.dll
Volume in drive C is
Tim Golden added the comment:
The key point here is that if I run the example as given on my Win 8.1
box, it doesn't work. (The venv I'm using is called nw0).
d:\tim\.venvs>dir nw0\Scripts\activate.bat
Volume in drive D is New Volume
Volume Serial Number is 2639-22DA
Direct
Tim Peters added the comment:
Ya, this annoyance has been there forever. As I recall, the source of the
problem is the Tk text widget (which slows horribly when displaying long lines).
--
nosy: +tim.peters
___
Python tracker
<h
New submission from Tim Peters:
Some researchers found an error in the logic of merge_collapse, explained here,
and with corrected code shown in section 3.2:
http://envisage-project.eu/proving-android-java-and-python-sorting-algorithm-is-broken-and-how-to-fix-it/
This affects all current
Tim Peters added the comment:
@Benjamin, bless you for changing their "n-1 > 0" to "n > 1", and for adding
parentheses to make the intended grouping obvious instead of a puzzle, and for
swapping the addends on the RHS of the new
Tim Peters added the comment:
Since it's impossible to trigger the error on any current machine anyway (no
machine has enough memory), increasing the size of the stack would be absurd.
If you read the paper, they note that this is what the Java folks first did
(they changed this pa
Tim Peters added the comment:
Thanks, Terry! Absolutely agreed: a logical error is an error, and will bite
us eventually, regardless of whether it does so today. I'm very glad the
researchers went to all the trouble to analyze thi
Tim Golden added the comment:
The problem is that this isn't an area I'm particularly familiar with
(either in Python nor in Windows) so I need time to ramp up my awareness
of what Steve's proposing plus then assessing the change. I'll try...
but I rather hope Z
Tim Peters added the comment:
Nothing should ever crash the interpreter :-) So this is a thoroughly
legitimate bug report.
However, there's no way to guess whether _this_ crasher is easy to fix, or next
to impossible. Without a test program to provoke the error, there's little
Tim Golden added the comment:
This is a duplicate of issue22028.
Daiyue Weng: to move forward, can you apply the fix referred to in this post:
https://mail.python.org/pipermail/python-list/2015-January/696688.html
(ie the "removing corrupted keys" section from
http://www.swarley.
Tim Golden added the comment:
This has come up again in issue23604. Steve, please apply your patch. I think
it should go against 2.7, 3.4 & 3.5 especially since all those versions now
ship with ensurepip.
--
___
Python tracker
&
Changes by Tim Graham :
--
nosy: +Tim.Graham
___
Python tracker
<http://bugs.python.org/issue22931>
___
___
Python-bugs-list mailing list
Unsubscribe:
Tim Graham added the comment:
Patch updated to fix conflict in NEWS. Could we have it committed to ensure it
gets fixed in the next 3.2 released?
--
Added file: http://bugs.python.org/file38609/secure-httponly-3.2-backport.diff
___
Python tracker
Tim Graham added the comment:
Here's an exception in Django after the latest patch. The Django code block in
the last exception catches ValueError, but this doesn't seem to work any longer
since it's "wrapped" in SystemError. As Berker mentioned, some upgrade tips
Tim Graham added the comment:
That last commit fixed compatibility with Django.
--
___
Python tracker
<http://bugs.python.org/issue23571>
___
___
Python-bug
Tim Golden added the comment:
Unless someone comes back who remembers what the ulterior motive was: I
agree; remove the check and just the crash happen.
--
___
Python tracker
<http://bugs.python.org/issue23
Tim Golden added the comment:
I think they stopped using them a while back in favour of a pywin32.pth
file.
I don't think I even knew you could use the registry for sys.path.
If no-one's shouted since the changes to importlib (which was 3.3?) I
think we can quietly drop this and h
Tim Golden added the comment:
Adding Mark Hammond in case I'm wrong about the (lack of) impact on pywin32
--
nosy: +mhammond
___
Python tracker
<http://bugs.python.org/is
Tim Graham added the comment:
Will this regression be fixed in Python 2.7, 3.2, and 3.3? If not, Django may
need to vendor Python's cookie class to workaround this bug to prevent users
from losing sessions and/or being unable to login to Django powered sites as
reported in
Tim Golden added the comment:
Turns out to be non-issue after all! I was working through the import code for
other reasons and noticed that the WindowsRegistryFinder was there. I'll spare
you the complications of debugging the _bootstrap part of import, but basically
the code in _bootstr
New submission from Tim Golden:
PCBuild\build.bat takes an argument of -e to pull in external libraries.
Either by accident or by design the main build will run in addition. However if
you'd run pcbuild -e simply to pull in externals, you might not have specified
extra build params, su
Tim Golden added the comment:
Fair enough
--
resolution: -> not a bug
stage: patch review -> resolved
status: open -> closed
___
Python tracker
<http://bugs.python.or
Tim Golden added the comment:
Are we talking about re-implementing StdPrinter in terms of
OutputDebugString? (Either always, on Windows, or as a fallback?)
--
___
Python tracker
<http://bugs.python.org/issue23
Tim Golden added the comment:
Sounds good to me. It's really a question as to the point where
practicality beats purity...
--
___
Python tracker
<http://bugs.python.org/is
Tim Golden added the comment:
Well, in the interests of due diligence, I checked out & built each of the four
flavours (32/64 Release/Debug) independently and without any errors. I then
rebuilt each with the "wrong" Platform (ie for Win32 in the x64 directory and
vice versa) wi
Tim Golden added the comment:
Adding Paul Moore as he's essentially the intersection between distutils &
Windows
--
nosy: +paul.moore
___
Python tracker
<http://bugs.python.or
Tim Golden added the comment:
One small thing to bear in mind is that the existing code (ie with the extra
linefeed) raises an IndentationError if cut-and-pasted into the interactive
interpreter; with the OP's change, it succeeds. Might not have been their
intention, but certainly is the
Tim Golden added the comment:
(Laughs). I admit, I was so close to the trees, I missed the fact that
the doc is, as you say, a What's New, and for Python 2.4. Agree that to
change this now would be somewhat ludicrous.
If some similar patch were proposed to some more current, rel
Tim Golden added the comment:
I can't see anything here which is clearly a Python bug. If the OP or anyone
else cares to come back (after more than 4 years!) with a clearly-reproducible
problem I'm happy to revisit.
I apologise for "waking up" this issue after so long; w
Tim Golden added the comment:
Perhaps unsurprisingly, I can't reproduce this on Python 2.7.9 32-bit running
on Win7 Home Premium.
Python doesn't handle CapsLock/Shift interaction directly: it just gets what it
gets from the underlying OS or framework. So I'm at a loss to
Tim Pierce added the comment:
Adding Python 2.7 to the affected versions (from #23341 which was closed as a
duplicate of this bug). We are very interested to know whether this will be
fixed in a Python 2.7 patch as well.
--
nosy: +twpierce
versions: +Python 2.7
Tim Peters added the comment:
FYI, my results match Serhiy's, on Windows, under Pythons 3.4.2 and 2.7.8.
It's not surprising to me. Since IEEE 754 standardized sqrt, most vendors
complied, delivering a square root "as if infinitely precise" with one anally
correct round
Tim Peters added the comment:
I don't care about the ULP. I don't care about exactly reproducing
floating-point results across releases either, but I'd bet someone else does ;-)
--
___
Python tracker
<http://bugs.pyt
Tim Peters added the comment:
Good catch, Mark!
--
___
Python tracker
<http://bugs.python.org/issue24059>
___
___
Python-bugs-list mailing list
Unsubscribe:
Tim Golden added the comment:
Jaivish Kothari,
Thanks for making the effort to contribute. Can I suggest you have a
look at the Core Mentorship site:
http://pythonmentors.com/
and perhaps join the Core Mentorship list:
http://mail.python.org/mailman/listinfo/core-mentorship
TJG
Tim Golden added the comment:
To eliminate pip from the equation, can you just try running: "py" on its own
command line?
Also: what platform are you on? Win7? Win8.1? 32-bit or 64-bit? Are you running
in an unusually restrictive user e
Tim Graham added the comment:
I noticed this is backwards incompatible for a small feature in Django. If you
want to leave this feature in Python 2.7 and 3.4, it'll break things unless we
push out a patch for Django; see https://github.com/django/django/pull/4637.
--
nosy: +Tim.G
Tim Graham added the comment:
I didn't find any problems while testing your proposed new patch for cpython
and your proposed patch for Django together.
--
___
Python tracker
<http://bugs.python.org/is
Tim Golden added the comment:
Tests failed on Windows probably because of NamedTemporaryFile
--
nosy: +tim.golden
___
Python tracker
<http://bugs.python.org/issue21
Tim Golden added the comment:
@RDM I'm sitting with Greg at a London Python session and we've run through
these tests on 3.4/3.5. I know you were reviewing this code at PyCon. Are you
happy for me to commit from here?
--
___
Python trac
Tim Golden added the comment:
Serhiy's offered a review and we can take it from here. :)
--
___
Python tracker
<http://bugs.python.org/issue21916>
___
___
Tim Golden added the comment:
My reluctance to commit the os.access patch is because it will cause
such a behaviour change in a function which has been pretty stable for a
long while. It'll certainly be more correct, but at the undoubted
expense of breaking someone's long-wo
Tim Golden added the comment:
That is a possibility which hadn't occurred to me. @eryksun, would you
mind eyeballing the patch over on issue2582? It almost certainly won't
apply cleanly as it's been almost two years since I last refreshed it,
but you can hopefully g
Tim Golden added the comment:
Thanks for the very thorough review. This isn't going to make it into
3.5, but I'll rework it in the light of your comments and see if people
are happy with it in the optional argument variation.
--
___
Pyth
Tim Peters added the comment:
Attched file "roots.py" you can run to get a guess as to how bad pow(x, 1/n)
typically is on your box.
Note that it's usually "pretty darned good" the larger `n` is. There's a
reason for that. For example, when n=1000, all x satis
Tim Peters added the comment:
BTW, add this other way of writing a native-precision Newton step to see that
it's much worse (numerically) than writing it in the "guess + small_correction"
form used in roots.py. Mathematically they're identical, but numerically they
behav
Changes by Tim Peters :
--
resolution: -> not a bug
stage: -> resolved
status: open -> closed
versions: +Python 3.2 -Python 3.4
___
Python tracker
<http://bugs.python.or
Tim Peters added the comment:
I'm at best -0 on the idea: very easy to get the effect without it, and hard
to imagine it's needed frequently. `sorted()` is also very easy to mimic, but
is used often by all sorts of code. For example, to display output in a `for
key in sorted(di
Tim Peters added the comment:
The only sane way to do things "like this" is to allow types to define their
own special methods (like `__isnan__()`), in which case the math module defers
to such methods when they exist. For example, this is how
`math.ceil(Fraction)` works, by de
Tim Golden added the comment:
Applies, builds & tests ok for me for Win32 Release build (ie build.bat
-e) on Win 8.1 x64.
--
___
Python tracker
<http://bugs.python.org/iss
2201 - 2300 of 2346 matches
Mail list logo
