Eli Bendersky added the comment:
I don't have time, unfortunately. So other folks can pick this up.
I don't remember if I made any progress on this - will post whatever I have if
I find something.
--
___
Python tracker rep...@bugs.python.org
New submission from Alexey:
Just one test failed for python-3.4.3
...
test_invalid_offset (test.test_os.TestSendfile) ... FAIL
...
--
files: test_os_log
messages: 236574
nosy: avoevodkin
priority: normal
severity: normal
status: open
title: test_os failed (python-3.4.3)
Alex Shkop added the comment:
It seems to me that OSS device doesn't accept more than SNDCTL_DSP_GETOSPACE.
Looks like this depends on OSS version because OSS docs state that since 4.x
one shouldn't use SNDCTL_DSP_GETOSPACE at all
Baptiste Mispelon added the comment:
I wasn't sure if that was going to be out of scope or not.
Here's an attached patch that fixes the remaining usages of `open` inside
`Doc/includes` to always use a context manager.
--
Added file:
R. David Murray added the comment:
There is a github mirror of the hg repository
(https://github.com/python/cpython). Patches produced from it don't
automatically get review links in the tracker, but at least they would then be
against the most current source (and someone else could
R. David Murray added the comment:
Looks like the example wasn't updated during the python3 transition.
As long as we are changing it, we might as well make it use the file as a
context manager.
--
___
Python tracker rep...@bugs.python.org
Changes by Serhiy Storchaka storch...@gmail.com:
--
components: +Extension Modules
nosy: +giampaolo.rodola, rosslagerwall
type: - behavior
versions: +Python 3.5
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue23520
R. David Murray added the comment:
Most likely this was a rounding fix (ie: not a bug), but hopefully Alexander
will know for sure.
--
nosy: +r.david.murray
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue23517
Changes by Serhiy Storchaka storch...@gmail.com:
--
components: +Argument Clinic
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue20187
___
___
Changes by Serhiy Storchaka storch...@gmail.com:
--
components: +Argument Clinic
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue20179
___
___
Changes by Serhiy Storchaka storch...@gmail.com:
--
components: +Argument Clinic
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue20175
___
___
Changes by Serhiy Storchaka storch...@gmail.com:
--
components: +Argument Clinic
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue20461
___
___
Changes by Serhiy Storchaka storch...@gmail.com:
--
components: +Argument Clinic
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue20178
___
___
Changes by Serhiy Storchaka storch...@gmail.com:
--
components: +Argument Clinic
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue20168
___
___
Changes by Serhiy Storchaka storch...@gmail.com:
--
components: +Argument Clinic
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue20177
___
___
Changes by Serhiy Storchaka storch...@gmail.com:
--
components: +Argument Clinic
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue20182
___
___
Changes by Serhiy Storchaka storch...@gmail.com:
--
components: +Argument Clinic
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue20396
___
___
Roundup Robot added the comment:
New changeset 325aec842e3e by Benjamin Peterson in branch '2.7':
fix merge_collapse to actually maintain the invariant it purports to (closes
#23515)
https://hg.python.org/cpython/rev/325aec842e3e
New changeset 620cb13008b7 by Benjamin Peterson in branch '3.4':
Changes by Serhiy Storchaka storch...@gmail.com:
--
components: +Argument Clinic
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue20304
___
___
Changes by Serhiy Storchaka storch...@gmail.com:
--
components: +Argument Clinic
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue20410
___
___
Changes by Serhiy Storchaka storch...@gmail.com:
--
components: +Argument Clinic
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue20173
___
___
Changes by Serhiy Storchaka storch...@gmail.com:
--
components: +Argument Clinic
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue20171
___
___
Changes by Serhiy Storchaka storch...@gmail.com:
--
components: +Argument Clinic
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue20172
___
___
Changes by Serhiy Storchaka storch...@gmail.com:
--
components: +Argument Clinic
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue20264
___
___
Changes by Alexander Belopolsky alexander.belopol...@gmail.com:
--
nosy: +haypo
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue23517
___
___
Zachary Ware added the comment:
The problem is, the interpreter can't know what you meant to do, so it can only
point out what it can't compile. We did recently add a special case for print
without parentheses, but adding special cases for everything is just not
feasible. Besides, where
Changes by Serhiy Storchaka storch...@gmail.com:
--
components: +Argument Clinic
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue20159
___
___
Changes by Serhiy Storchaka storch...@gmail.com:
--
components: +Argument Clinic
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue23500
___
___
Alexander Belopolsky added the comment:
Victor's motivation for the change was (msg154811):
I chose this rounding method because it is the method used by int(float) and
int(time.time()) is a common in programs (more than round(time.time()).
Rounding towards zero avoids also producing
Roundup Robot added the comment:
New changeset 89c6a6c2dd1f by Berker Peksag in branch '3.4':
Issue #23511: Port email-simple.py to Python 3.
https://hg.python.org/cpython/rev/89c6a6c2dd1f
New changeset cb911e1fb3dc by Berker Peksag in branch 'default':
Issue #23511: Port email-simple.py to
Alexander Belopolsky added the comment:
Let me dig up the history, but this does not look like correct rounding to me:
datetime.utcfromtimestamp(1424817268.274)
datetime.datetime(2015, 2, 24, 22, 34, 28, 273999)
decimal.Decimal(1424817268.274)
Decimal('1424817268.273294281005859375')
Changes by Serhiy Storchaka storch...@gmail.com:
--
components: +Argument Clinic
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue20260
___
___
Changes by Serhiy Storchaka storch...@gmail.com:
--
components: +Argument Clinic
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue20346
___
___
Alexander Belopolsky added the comment:
It looks like it was an intentional change. See #14180 (changeset
75590:1e9cc1a03365).
I am not sure what the motivation was. Note that this change made
utcfromtimestamp(t) different from datetime(1970,1,1) + timedelta(seconds=t).
--
keywords:
Changes by Serhiy Storchaka storch...@gmail.com:
--
components: +Argument Clinic
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue20341
___
___
Changes by Serhiy Storchaka storch...@gmail.com:
--
components: +Argument Clinic
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue20174
___
___
Changes by Serhiy Storchaka storch...@gmail.com:
--
components: +Argument Clinic
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue23501
___
___
Changes by Serhiy Storchaka storch...@gmail.com:
--
components: +Argument Clinic
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue20148
___
___
Changes by Serhiy Storchaka storch...@gmail.com:
--
components: +Argument Clinic
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue23283
___
___
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 test. Thank you - perfect :-)
--
Zack Weinberg added the comment:
In terms of the formal grammar of the language, you are correct. However, the
position of the caret should be chosen based *not* on the formal grammar, but
on a heuristic estimation of what the most probable mistake actually is. In
both of the cases I
Changes by Serhiy Storchaka storch...@gmail.com:
--
components: +Argument Clinic
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue20256
___
___
Changes by Serhiy Storchaka storch...@gmail.com:
--
components: +Argument Clinic
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue20303
___
___
Cyd Haselton added the comment:
Thanks for that suggestion R. David...that would be ideal given the 2.x
requirements of Mercurial would mean i'd need to re-port Python before tackling
a port of Mercurial.
I'll wait until Ryan chimes in before I start serious work with git, just in
case.
Changes by Serhiy Storchaka storch...@gmail.com:
--
components: +Argument Clinic
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue20586
___
___
Changes by Serhiy Storchaka storch...@gmail.com:
--
components: +Argument Clinic
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue20180
___
___
Changes by Serhiy Storchaka storch...@gmail.com:
--
components: +Argument Clinic
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue20183
___
___
Changes by Serhiy Storchaka storch...@gmail.com:
--
components: +Argument Clinic
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue20184
___
___
Changes by Serhiy Storchaka storch...@gmail.com:
--
components: +Argument Clinic
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue23492
___
___
Changes by Serhiy Storchaka storch...@gmail.com:
--
components: +Argument Clinic
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue20181
___
___
Changes by Serhiy Storchaka storch...@gmail.com:
--
components: +Argument Clinic
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue20185
___
___
Alexander Belopolsky added the comment:
I noticed that the rounding mode of datetime is currently wrong.
What do you mean by currently? What versions of python have it wrong?
--
___
Python tracker rep...@bugs.python.org
Changes by Serhiy Storchaka storch...@gmail.com:
--
components: +Argument Clinic
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue20459
___
___
Changes by Serhiy Storchaka storch...@gmail.com:
--
components: +Argument Clinic
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue20432
___
___
Changes by Serhiy Storchaka storch...@gmail.com:
--
components: +Argument Clinic
nosy: +steve.dower, tim.golden
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue20323
___
Changes by Serhiy Storchaka storch...@gmail.com:
--
components: +Argument Clinic
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue20291
___
___
Changes by Serhiy Storchaka storch...@gmail.com:
--
components: +Argument Clinic
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue20186
___
___
Changes by Serhiy Storchaka storch...@gmail.com:
--
components: +Argument Clinic
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue21314
___
___
STINNER Victor added the comment:
I started a large change set to support nanoseconds in the C pytime API: see
the issue #22117. While working on this change, I noticed that the rounding
mode of datetime is currently wrong. Extract of a private patch:
typedef enum {
/* Round towards zero.
Berker Peksag added the comment:
Thanks for the patch, Baptiste.
--
resolution: - fixed
stage: commit review - resolved
status: open - closed
type: - enhancement
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue23511
Zachary Ware added the comment:
That may be for the best.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue20323
___
___
Python-bugs-list mailing
Changes by Alexander Belopolsky alexander.belopol...@gmail.com:
--
nosy: +bdkearns, benjamin.peterson
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue23521
___
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 part of
Changes by Alexander Belopolsky alexander.belopol...@gmail.com:
--
keywords: +3.3regression -3.2regression
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue23517
___
James Rutherford added the comment:
The fix for this still doesn't set Content-Length to zero when body is None,
but I don't see any reason why this should be the case. For example, the
following snippet would work for any 'empty' body:
if 'content-length' not in header_names:
Ryan Gonzalez added the comment:
That's what I was saying; I'll update the patches myself. I highly doubt Cyd
wants to re-port Python again. :0
I'll ask on python-dev on which would be preferred: configure.ac edits or macro
tests.
--
___
Python
Larry Hastings added the comment:
Perhaps, now that Guido allows us to redirect into a separate file, we should
simply abandon the two-pass approach.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue20323
Serhiy Storchaka added the comment:
Thank you for your explanation Tim.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue23515
___
___
Serhiy Storchaka added the comment:
How additional test affects performance? May be just increase MAX_MERGE_PENDING?
--
nosy: +serhiy.storchaka
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue23515
Guido van Rossum added the comment:
I recall discussing this before (maybe on the tulip list). I am firmly against.
It is a slippery slope -- why inspect a partial but not a lambda? Plus there is
no use case.
--
___
Python tracker
Steve Dower added the comment:
Not sure how helpful this is, but the following code compiles fine for me (VC
12.0 and 14.0):
#include stdio.h
char myStr[];
struct { char* a; } myStruct = { myStr };
int main() {
printf(%s, myStruct.a);
return 0;
}
static char myStr[] = 123456789;
Serhiy Storchaka added the comment:
What if add const in PyDoc_VAR?
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue20323
___
___
Steve Dower added the comment:
You need to leave static out of the forward definition and then add it in the
initialization. The variable is not accessible from other object files - I
checked.
const char[] and static const char[] should work the same, though I haven't
tried it.
--
Changes by Aaron Meurer asmeu...@gmail.com:
--
nosy: +Aaron.Meurer
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue18199
___
___
Python-bugs-list
Vandana Rao added the comment:
Since the program depends on receiving a raw ^C == 0x03 on stdin, it will never
be running under Idle because the Idle process tk gui normally keeps control of
keyboard input and the Idle process code intercepts ^C and turns it into
KeyboardInterrupt raised in
Alexander Belopolsky added the comment:
For example, in my local patch, I'm using ROUND_FLOOR for:
- datetime.date.fromtimestamp()
- datetime.datetime.fromtimestamp()
These should use ROUND_HALF_EVEN
- datetime.datetime.now()
- datetime.datetime.utcnow()
These should not involve
Zachary Ware added the comment:
(My last comment was aimed at Larry's comment about abandoning two-pass...)
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue20323
___
New submission from Alexander Belopolsky:
import sys
sys.modules['_datetime'] = None
from datetime import timedelta
timedelta(seconds=1)*0.6112295
Traceback (most recent call last):
File stdin, line 1, in module
File /Users/a/Work/cpython/Lib/datetime.py, line 519, in __mul__
return
Alexander Belopolsky added the comment:
Attached patch fixes the issue, but produces a slightly different result:
timedelta(seconds=1)*0.6112295
datetime.timedelta(0, 0, 611230)
Note that C implementation is probably buggy:
from datetime import *
timedelta(seconds=1)*0.6112295
STINNER Victor added the comment:
What do you mean by currently? What versions of python have it wrong?
I search for ROUND in Modules/_datetimemodule.c: in the Python development
branch (default), I found _PyTime_ROUND_DOWN (Round towards zero). Since a bug
was reported, I understand that
Alexander Belopolsky added the comment:
I don't understand nearest.
Sorry for using loose terms. I was hoping the in the context of going back,
it would be clear.
I believe the correct mode is ROUND_HALF_EVEN. This is the mode used by the
builtin round() function:
round(0.5)
0
Alexander Belopolsky added the comment:
Victor,
Would you consider going back to round to nearest? Mark and I put in a lot of
effort to get the rounding in the datetime module right. (See for example,
#8860.)
Sub-microsecond timesources are still rare and users who work with such should
Serhiy Storchaka added the comment:
You forgot static in the declaration Steve.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue20323
___
___
STINNER Victor added the comment:
Would you consider going back to round to nearest?
I don't understand nearest. I prefer to use names of decimal rounding modes:
https://docs.python.org/dev/library/decimal.html#rounding-modes
In my local patch, I'm using ROUND_FLOOR in _decimal: Round towards
Serhiy Storchaka added the comment:
LGTM. But the bug in C implementation should be fixed.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue23521
___
Alexander Belopolsky added the comment:
You can use self._to_microseconds().
Right. Did that and added a simple test.
--
Added file: http://bugs.python.org/file38235/issue23521-2.patch
___
Python tracker rep...@bugs.python.org
New submission from Jake:
In the statistics module documentation, there is a note that states that
The mean is strongly affected by outliers and is not a robust estimator for
central location: the mean is not necessarily a typical example of the data
points. For more robust, although less
Serhiy Storchaka added the comment:
You can use self._to_microseconds().
--
nosy: +serhiy.storchaka
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue23521
___
Changes by SilentGhost ghost@gmail.com:
--
nosy: +steven.daprano
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue23522
___
___
Python-bugs-list
Mark Lawrence added the comment:
I can reproduce this on Windows 8.1 with 3.4.3 but cannot do so with 3.5.0a1.
--
nosy: +BreamoreBoy
versions: +Python 3.5
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue20703
Mark Lawrence added the comment:
What is wrong with the example given here
https://docs.python.org/3/tutorial/classes.html#scopes-and-namespaces-example ?
--
nosy: +BreamoreBoy
___
Python tracker rep...@bugs.python.org
Terry J. Reedy added the comment:
I sent a note to the lead author Stijn de Gouw and mentioned that the
repository has moved from svn to hg.python.org.
This change may be moot, but I think it worth our effort to keep our code as
clean as possible and to encourage automated code checks, as we
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 this one :-)
--
Mark Lawrence added the comment:
@Senthil what is your opinion of this?
--
nosy: +BreamoreBoy
type: behavior - resource usage
versions: +Python 3.4, Python 3.5 -Python 3.1, Python 3.2
___
Python tracker rep...@bugs.python.org
Mark Lawrence added the comment:
Can someone review the patch with a view to commit please. It's a change to
one line as explained in msg215934.
--
nosy: +BreamoreBoy
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue21201
Mark Lawrence added the comment:
@Steven would you like to formally review the patch please. At a very quick
glance it looks okay to me.
--
nosy: +BreamoreBoy
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue20780
Benjamin Peterson added the comment:
The duplicate tests have been renamed already.
--
nosy: +benjamin.peterson
resolution: - out of date
status: open - closed
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue20780
Changes by Mark Lawrence breamore...@yahoo.co.uk:
--
type: - resource usage
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue20936
___
___
Alexander Belopolsky added the comment:
the bug in C implementation should be fixed.
In the past (see #8860) we were not able to reach a consensus on which behavior
is correct and which has a bug:
timedelta(seconds=1)*0.6112295
datetime.timedelta(0, 0, 611229)
timedelta(seconds=0.6112295)
Mark Lawrence added the comment:
I've taken a bit of a liberty and picked the names of the last three guys
who've worked on this file as I assume they're best qualified to comment.
--
nosy: +BreamoreBoy, haypo, ncoghlan, pitrou
___
Python tracker
1 - 100 of 134 matches
Mail list logo
