Prashanth noble prashanth.b...@gmail.com added the comment:
please find the testcase i am using
--
Added file:
http://bugs.python.org/file16208/Aura_Test_Scripts_FCT_ACTUSER_EVENT_L.tsv
___
Python tracker rep...@bugs.python.org
Dagobert Michelsen d...@opencsw.org added the comment:
I verified patch_2.diff on Solaris 10 w/SOS11 and it actually resolves a number
of issues I had with Mercurial.
--
nosy: +dagobert Michelsen
___
Python tracker rep...@bugs.python.org
Florent Xicluna la...@yahoo.fr added the comment:
Similar failures with or without argv 0:
~ $ sh -c 'exec -a missing ./python -c import sys; print sys.executable'
/home/user/dev/python/trunk/
~ $ sh -c 'exec -a ./python -c import sys; print sys.executable'
Could not find platform
Changes by Nick Coghlan ncogh...@gmail.com:
--
nosy: +ncoghlan
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue4037
___
___
Python-bugs-list mailing
Ronald Oussoren ronaldousso...@mac.com added the comment:
I've added the tests to the 2.6 branch and have ported the #ifdef guard around
the prototype for completion_matches to the trunk and 3.2.
I'm therefore closing the issue.
--
status: open - closed
Ronald Oussoren ronaldousso...@mac.com added the comment:
Ned: I fixed the ARCH_RUN_32BIT definition for 3-way universal builds in
r78150.
Also ported the patch to 2.6, 3.2 and 3.1.
--
status: open - closed
___
Python tracker
New submission from Zsolt Cserna zsolt.cse...@morganstanley.com:
Python 2.6.4
On my system which is solaris 8/sparc, float(INFI) returns inf instead of
raising ValueError, both 32 and 64-bit. (since it's case-insensitive it applies
to any upper/lower combination of letters).
This issue breaks
Meador Inge mead...@gmail.com added the comment:
On Thu, Feb 11, 2010 at 7:16 AM, Ronald Oussoren rep...@bugs.python.orgwrote:
I've added the tests to the 2.6 branch and have ported the #ifdef guard
around the prototype for completion_matches to the trunk and 3.2.
Verified in trunk.
New submission from patraulea patra...@gmail.com:
http://docs.python.org/library/_winreg.html
This page references CreateKeyEx which doesn't exist (Python uses CreateKey).
--
assignee: georg.brandl
components: Documentation
messages: 99208
nosy: georg.brandl, patraulea
severity: normal
Changes by Zsolt Cserna zsolt.cse...@morganstanley.com:
--
nosy: +csernazs
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue1471934
___
___
Changes by Brian Curtin cur...@acm.org:
--
components: +Windows
keywords: +needs review, patch
priority: - normal
stage: - patch review
type: - behavior
versions: +Python 3.1, Python 3.2 -Python 2.5
Added file: http://bugs.python.org/file16210/issue7907.diff
New submission from Ronald Oussoren ronaldousso...@mac.com:
The attached patch removes all traces to os.name == 'mac' from the source tree
(setup.py and stdlib), that is the leftover traces for MacOS9 support.
A simular patch needs to be created of the 3.x tree.
--
assignee:
Changes by Ronald Oussoren ronaldousso...@mac.com:
--
versions: +Python 2.7, Python 3.2
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue7908
___
___
Changes by Eric Smith e...@trueblade.com:
--
nosy: +eric.smith, mark.dickinson
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue7906
___
___
Brian Curtin cur...@acm.org added the comment:
Prashanth, I'm not even sure what to do with that file.
Can you provide a Python script which demonstrates your issue? It should be
something that myself or others could run on their computer, free of any third
party packages. This will isolate
johns j...@cox.net added the comment:
Perhaps 1.x was never considered. OpenBSD 2.0 was released in 1996. The OS
developers only support the current release version and one minor release
back anyway. The major release number isn't significant. It's just
incremented after the minor release
New submission from Arno Bakker abak...@users.sourceforge.net:
I encountered this when somebody used:
logging.basicConfig(level=logging.CRITICAL,
format='%(asctime)s %(levelname)-8s %(message)s',
datefmt='%a, %d %b %Y %H:%M:%S',
Antoine Pitrou pit...@free.fr added the comment:
If these 8 million records are loaded into memory, it can be normal to get a
MemoryError. It depends on the complexity of the records (number of fields) and
the way they are kept in memory (tuples? dicts?); and of course of the amount
of
Mark Dickinson dicki...@gmail.com added the comment:
Thanks for the report, and for the analysis.
I'd call this a bug in the Solaris strtod function (though that doesn't
preclude adding a workaround for Python): the C standards (well, C99, anyway;
I don't have access to C89 at the moment)
Antoine Pitrou pit...@free.fr added the comment:
I'm not sure what this brings. It is easy to write a loop iterating over test
data.
What parametric testing could bring is precise progress and error display
(displaying the parameters for each run), but this doesn't seem to be the case
here,
Michael Foord mich...@voidspace.org.uk added the comment:
By the way - I have no opinion on whether or not using yield is the right way
to support parameterized tests. It may be better for the test method to take
arguments, and be decorated as a parameterized test, with the decorator
Jean-Paul Calderone exar...@divmod.com added the comment:
With paramterized tests *all* the tests are run and *all* failures reported.
With testing in a loop the tests stop at the first failure.
+1 to this justification. Parameterized tests are a big win over a simple for
loop in a test.
New submission from Matthew Russell matt.horiz...@gmail.com:
Tuples, as we know are designed to immutable.
Hence I'm questioning if the following behavior is considered a defect:
t = (1, 2)
t += (1, 2, 3)
t
(1, 2, 3)
?
--
components: Interpreter Core
messages: 99219
nosy:
Jean-Paul Calderone exar...@divmod.com added the comment:
Your output looks fishy. Anyway, the behavior of += isn't a bug:
a = b = (1, 2)
a += (1, 2, 3)
a
(1, 2, 1, 2, 3)
a is b
False
It's confusing, to be sure, but no mutation is going on. += is only in-place
if applied to something
Tim Golden m...@timgolden.me.uk added the comment:
Just think about it for a minute:
t = (1, 2)
print id (t), t
t += (1, 2, 3)
print id (t), t
Not mutating, merely creating a new new object
and giving it the same name
--
nosy: +tim.golden
___
Brian Curtin cur...@acm.org added the comment:
It may be better for the test method to take arguments, and
be decorated as a parameterized test, with the decorator
providing the parameters.
+1 on something like this. That's also how NUnit supports parameterized tests.
--
nosy:
Antoine Pitrou pit...@free.fr added the comment:
With paramterized tests *all* the tests are run and *all* failures
reported. With testing in a loop the tests stop at the first failure.
+1 to this justification. Parameterized tests are a big win over a
simple for loop in a test.
Ah,
Michael Foord mich...@voidspace.org.uk added the comment:
Antoine: the failure message would include a repr of the parameters used in the
particular test that failed. So you can tell which test failed and with what
parameters.
--
___
Python tracker
Matthew Russell matt.horiz...@gmail.com added the comment:
Yes, the output is fishy indeed my bad (paste error).
Tim: I hadn't thought for long enough or thought to check with the id builtin -
nice catch.
--
status: open - closed
___
Python tracker
Jean-Paul Calderone exar...@divmod.com added the comment:
Something else I think it would be nice to consider is what the id() (and
shortDescription(), heh) of the resulting tests will be.
It would be great if the id were sufficient to identify a particular test *and*
data combination.
In
Changes by Ronald Oussoren ronaldousso...@mac.com:
--
keywords: +needs review
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue7908
___
___
Ronald Oussoren ronaldousso...@mac.com added the comment:
The reason I'd like a patch review is that it affects a lot of files and want a
second pair of eyes to check that I haven't been too agressive.
The patch itself doesn't cause regressions in the unittests.
--
Zsolt Cserna zsolt.cse...@morganstanley.com added the comment:
I was not able to compile 3.1.1 due to issue6236, but with 2.7a3 it raises the
expected ValueError, which is correct.
Is there any chance to get those changes you mentioned backported to 2.6?
--
Changes by Raymond Hettinger rhettin...@users.sourceforge.net:
--
resolution: - invalid
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue7910
___
mARK python.mblo...@xoxy.net added the comment:
i have attached an svn diff of my (very simple!) fix and added unit test for
python 2.7.
--
title: urllib.urlparse mishandles novel schemes - urlparse.urlsplit mishandles
novel schemes
Added file:
Changes by Michael Foord mich...@voidspace.org.uk:
--
assignee: michael.foord
keywords: easy
nosy: michael.foord
severity: normal
stage: needs patch
status: open
title: unittest.TestCase.longMessage should default to True in Python 3.2
versions: Python 3.2
New submission from James Sparenberg linuxre...@gmail.com:
Python produces rounding errors when adding decimals.
ython 2.6.4 (r264:75706, Dec 7 2009, 18:43:55)
[GCC 4.4.1] on linux2
Type help, copyright, credits or license for more information.
13.04 + 158.00
171.03
13 +158
171
R. David Murray rdmur...@bitdance.com added the comment:
Read this:
http://docs.python.org/tutorial/floatingpoint.html?highlight=rounding
And then perhaps take a look at the Decimal package.
--
nosy: +r.david.murray
priority: - low
resolution: - invalid
stage: - committed/rejected
Mark Dickinson dicki...@gmail.com added the comment:
Is there any chance to get those changes you mentioned backported to 2.6?
Actually, to be honest, I'm not sure that backporting these changes to the
release branch is a good idea. Is this bug causing problems in real code
(besides the
New submission from R. David Murray rdmur...@bitdance.com:
Cmd currently has undocumented support for using the docstrings of 'do_'
methods as the documentation for those methods. This is a very convenient
facility, except that it leads to documentation being printed with a lot of
leading
Raymond Hettinger rhettin...@users.sourceforge.net added the comment:
I concur with Mark.
--
nosy: +rhettinger
resolution: - wont fix
status: open - closed
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue7906
Antoine Pitrou pit...@free.fr added the comment:
Retrograding to critical after popular python-dev demand.
--
nosy: +pitrou
priority: release blocker - critical
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue6608
New submission from R. David Murray rdmur...@bitdance.com:
+1
--
nosy: +r.david.murray
priority: - normal
type: - feature request
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue7911
___
Matthew Barnett pyt...@mrabarnett.plus.com added the comment:
The re module is addressed in issue #2636.
BTW, my regex module behaves like Ruby:
regex.sub(r((x|y)*)*, (\\1, \\2), xyyzy, count=1)
'(, y)zy'
regex.sub(r((x|y+)*)*, (\\1, \\2), xyyzy, count=1)
'(, yy)zy'
--
nosy:
New submission from Nick nick.allg...@gmail.com:
I tried to run the attached code and it seems IntVar() dies in the Tkinter
module. After discussion with several other coworkers they seem to agree this
may be a bug in Tkinter. If you need more info feel free to let me know and I
can help with
Marc-Andre Lemburg m...@egenix.com added the comment:
Brian Curtin wrote:
Brian Curtin cur...@acm.org added the comment:
I'll look into whatever other trickery could be applied to 2.6/3.1.
The patch against trunk works correctly for Win7, Win 2003 Server SP1, Win XP
SP2, and Win 2000
Nick nick.allg...@gmail.com added the comment:
Ok this was my own mistake and not a bug.. really sorry about this.
Moving the following code ABOVE the IntVar() calls allows it to work:
app = Tk()
app.title(TESTING)
app.geometry('300x100+200+100')
See revised attached
--
status: open
Marc-Andre Lemburg m...@egenix.com added the comment:
Marc-Andre Lemburg wrote:
Marc-Andre Lemburg m...@egenix.com added the comment:
Brian Curtin wrote:
Brian Curtin cur...@acm.org added the comment:
I'll look into whatever other trickery could be applied to 2.6/3.1.
The patch
Changes by Brian Curtin cur...@acm.org:
--
resolution: - invalid
type: compile error - behavior
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue7914
___
Roumen Petrov bugtr...@roumenpetrov.info added the comment:
r78136 completely broke this build.
before was enough to add old workdir in first place as library directory to
make test_get_outputs happy
--
nosy: +rpetrov
___
Python tracker
Changes by Ezio Melotti ezio.melo...@gmail.com:
--
nosy: +ezio.melotti
priority: - normal
stage: - test needed
type: - behavior
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue7909
___
Fernando Perez fdo.pe...@gmail.com added the comment:
I should probably have clarified better our reasons for using this type of
code. The first is the one Michael pointed out, where such parametric tests
all execute; it's very common in scientific computing to have algorithms that
only fail
Mathew Martineau m...@martineau.name added the comment:
I can submit a patch, but my employer has an involved process for doing this
(even for small fixes like this). It will take a few more days to get to a
point where I can post the patch, but I will do so as soon as I can.
--
Ezio Melotti ezio.melo...@gmail.com added the comment:
Fixed in r78162 (trunk), r78163 (release26-maint), r78164 (py3k) and r78165
(release31-maint), thanks for the report and the patch!
--
assignee: georg.brandl - ezio.melotti
nosy: +ezio.melotti
resolution: - fixed
stage: patch
Brian Harring ferri...@gmail.com added the comment:
@benjamin:
Tests can be written; the reason this patch doesn't bundle tests up front is
that I wasn't going to burn the time till I knew they were needed since I
expected the concept to require some debate.
As for the hacks angle, there
Craig McQueen pyt...@craig.mcqueen.id.au added the comment:
There's also this one which caught me out:
def outer():
x = 0
y = (x for i in range(10))
del x # SyntaxError
--
nosy: +cmcqueen1975
___
Python tracker rep...@bugs.python.org
Meador Inge mead...@gmail.com added the comment:
The re module is addressed in issue #2636.
Wow, that issue thread is massive... What about the 're' module is addressed?
Is 'regex' replacing 're'? Is 'regex' being rolled into 're'? Are they both
going to exist?
--
components:
New submission from Alex Coventry throwa...@mit.edu:
I feel like I must be on crack, here. I apologize if so. English version:
sorting this long list leaves in place element 580395, which is less than
element 0. Restricting to a list of just those two elements, sorting does what
I'd
Ezio Melotti ezio.melo...@gmail.com added the comment:
Could you provide the list in another format (e.g. in a plain .py script or as
a .txt file)?
--
nosy: +ezio.melotti
priority: - normal
stage: - test needed
versions: -Python 2.5
___
Python
Changes by Ezio Melotti ezio.melo...@gmail.com:
Removed file: http://bugs.python.org/file16216/list.pickle.gz
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue7915
___
Matthew Barnett pyt...@mrabarnett.plus.com added the comment:
The issue started about updating the re module and adding features that other
languages already possess in their regex implementations (the last time any
significant work was done on it was in 2003).
The hope is that the new regex
Alex Coventry throwa...@mit.edu added the comment:
No. It's 10M, gzipped. It's constructed from genome-wide association
data, which is also huge, intrinsically complex, and protected by rules
regarding research on humans. If the bug tracker won't take it do I
have any other options?
Alex Coventry throwa...@mit.edu added the comment:
Oh, I guess I could make it a gzipped text file. Hang on.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue7915
___
Thomas Wouters tho...@python.org added the comment:
You have a nan in your list of tuples, which screws up the sorting. After the
first sort, elements 580395-7 are:
(0.99257340581672904, 551095),
(nan, 551371),
(6.6494600485570754e-14, 551526),
--
nosy: +twouters
resolution: -
Changes by Ezio Melotti ezio.melo...@gmail.com:
--
stage: test needed - committed/rejected
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue7915
___
Alex Coventry throwa...@mit.edu added the comment:
Ah, I guess I *was* on crack. Thanks for the explanation.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue7915
___
Changes by Ezio Melotti ezio.melo...@gmail.com:
--
nosy: +ezio.melotti
priority: - normal
stage: - needs patch
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue7888
___
Senthil Kumaran orsent...@gmail.com added the comment:
Hello Mark,
Thanks for the patch.
However there are reasons why the check is:
if scheme in uses_netloc and url[:2] == '//':
It cannot be replaced by just url[:2] == '//' as in your patch.
Different protocols have different parsing
68 matches
Mail list logo
