Michael Foord added the comment:
The test now passes for me on Mac OS X and yes - looks like the same issue as
issue 8447.
--
resolution: -> invalid
stage: needs patch -> committed/rejected
status: open -> closed
___
Python track
Michael Foord added the comment:
Sorry for the late reply. I don't think the patch as provided is sufficient as
it would interfere with people causing unittest.main() directly from a test
module. Checking that TestProgram.loader is None is the way to detect we have
been launched fro
Michael Foord added the comment:
Committed revision 86649.
--
resolution: -> accepted
stage: needs patch -> committed/rejected
status: open -> closed
___
Python tracker
<http://bugs.python.or
Michael Foord added the comment:
Eli - I quite agree. TestProgram is a *particularly* obscure part of unittest.
A much better solution (well - both would be ideal) would be to refactor the
code so that it isn't so obscure.
TestProgram is an artefact of unittest's history and s
New submission from Michael Foord :
Add the unittestgui test runner, built with Tk, to the Tools directory.
It would be good to have this script included in the bin/ directory of the Mac
installer as well.
The unittestgui runner can be found at:
https://bitbucket.org/markroddy
Michael Foord added the comment:
It will need documenting, or at least pointing to in the documentation,
probably with a note recommending Hudson for production use - unittestgui is a
tool for beginners / convenience.
Note also that Brian Curtin has contributed a patch to make unittestgui
Michael Foord added the comment:
Bringing back callable but with a different name is horrible. Just bring it
back for goodness sake.
--
nosy: +michael.foord
___
Python tracker
<http://bugs.python.org/issue10
Michael Foord added the comment:
Well, Guido has already approved its return - so further debate is relatively
pointless. (Not that that usually stops us...)
--
___
Python tracker
<http://bugs.python.org/issue10
Michael Foord added the comment:
It was on python-ideas in the recent thread about bringing back callable. Feel
free to post a link here for the record.
--
___
Python tracker
<http://bugs.python.org/issue10
New submission from Michael Foord :
As discussed with tarek. It shouldn't be up to distutils2 to decide whether or
not a Python file that has been included in the package should be installed or
not if it is included in the set of files the developer has *asked* to be
installed.
Possibl
Michael Foord added the comment:
I would love this functionality (I almost always initialise defaultdict with a
lambda that just returns a concrete value).
Unfortunately it seems like adding a keyword argument isn't possible because
defaultdict takes arbitrary keyword args (and populate
Michael Foord added the comment:
Well, I was perfectly aware of __missing__ - it's just a three liner to do it
when using a lambda isn't *that* bad... I'm sure the documentation could be
improved to highlight __missing__ though. It's almost always the case that
documenta
New submission from Michael Foord :
This is because jython creates bytecode files with names like
"tests/testwith$py.class". unittest test discovery splits the extension off
__file__ to compare module.__file__ to the expected path.
--
messages: 122467
nosy: michael.foor
Changes by Michael Foord :
--
assignee: -> michael.foord
components: +Library (Lib)
type: -> behavior
versions: +Python 2.7, Python 3.2
___
Python tracker
<http://bugs.python.org/i
Michael Foord added the comment:
Won't need fixing in 3.2. The __pycache__ changes mean that the module.__file__
no longer points to the compiled bytecode file.
--
versions: -Python 3.2
___
Python tracker
<http://bugs.python.org/is
Michael Foord added the comment:
"I'm also thinking that it might be better to include the name of the
deprecated method in the message and use three filters for fail* methods,
assert* methods, and the assert*Regexp* methods that will be deprecated."
That sounds good, w
New submission from Michael Foord :
Reported by Konrad Delong.
class MyTest(unittest.TestCase):
def setUp(self):
raise Exception
@unittest.expectedFailure
def testSomething(self):
assert False, "test method failed"
This code will report error, no
Michael Foord added the comment:
Scanning with Microsoft Security Essentials says "no threat detected".
--
nosy: +michael.foord
___
Python tracker
<http://bugs.python.o
Michael Foord added the comment:
We follow engineering which uses j.
(I was about to close this as wontfix but Antoine is particularly keen that
Mark deals with this issue...)
--
nosy: +michael.foord
___
Python tracker
<http://bugs.python.
Michael Foord added the comment:
The same is also true for tearDown and cleanUp functions.
--
___
Python tracker
<http://bugs.python.org/issue10548>
___
___
Pytho
Michael Foord added the comment:
FWIW (which isn't much I guess) it annoys me that I have to protect calls to
issubclass with if isinstance(obj, type).
--
nosy: +michael.foord
___
Python tracker
<http://bugs.python.org/is
Michael Foord added the comment:
Note that if an error is raised in a tearDown or cleanUp then
unexpected-success should not be reported either. Not very important but might
as well be fixed at the same time.
--
___
Python tracker
<h
New submission from Michael Foord :
Having tests in Lib/test instead of inside the package makes it easier to grep
the unittest package without grepping the tests. The Windows installer has an
"install without tests" option which is easier to honour if the tests aren't
New submission from Michael Foord :
The unittest documentation, argument names and implementation need to be
consistent about the order of (actual, expected) for TestCase.assert methods
that take two arguments.
This is particularly relevant for the methods that produce 'diffed'
Michael Foord added the comment:
__unittest needs to die (with appropriate deprecation).
I agree that a nicer API for marking functions and methods as needing to be
excluded from unittest stacktraces would be useful. A decorator is a good way
to expose that API to developers. Internally
Michael Foord added the comment:
Raymond - I created a new issue for moving the tests: issue 10572
However, it seems that you are incorrect in saying that Python practise is to
avoid putting tests inside standard library packages. In fact current Python
practise seems to be that where tests
Michael Foord added the comment:
The same is true for 2.7 though, and that is getting bug fixes. svnmerge would
no longer work (and to making the change would mean moving the tests in a point
release).
--
___
Python tracker
<h
Michael Foord added the comment:
That list of examples was non-exhaustive, there is also tkinter.
--
___
Python tracker
<http://bugs.python.org/issue10
Michael Foord added the comment:
Works for me too. Great!
--
___
Python tracker
<http://bugs.python.org/issue9227>
___
___
Python-bugs-list mailing list
Unsub
Michael Foord added the comment:
Committed revision 86944.
--
resolution: -> fixed
stage: needs patch -> committed/rejected
status: open -> closed
___
Python tracker
<http://bugs.python.o
New submission from Michael Foord :
Reported by a unittest2 user.
A SystemExit (or GeneratorExit) will cause a test run to stop in 2.7 / 3.2.
This would just be reported as an error in 2.6.
>>> from unittest import TestCase
>>> def test(s):
... raise GeneratorExit
...
&g
Changes by Michael Foord :
--
title: sys.exit() in a test causes the run to stp -> sys.exit() in a test
causes a test run to die
___
Python tracker
<http://bugs.python.org/issu
New submission from Michael Foord :
It is hard for test infrastructure to halt a test run unless it has access to
the result object.
A StopTestRun exception could be provided. This could be caught in TestCase.run
and call TestResult.stop().
It could be parameterized so that StopTestRun
Changes by Michael Foord :
--
nosy: -michael.foord
___
Python tracker
<http://bugs.python.org/issue10562>
___
___
Python-bugs-list mailing list
Unsubscribe:
New submission from Michael Foord :
If a test module fails to load during unittest test discovery (SyntaxError or
other exception) then the error is reported during the test run.
Due to the way the exception is re-raised the traceback is lost.
Originally reported as unittest2 issue 29:
https
New submission from Michael Foord :
Feature request against unittest2. Issue 18:
https://code.google.com/p/unittest-ext/issues/detail?id=18
As providing a file path instead of module name to the unittest command line
runner currently fails there is no backwards compatibility issue with making
Michael Foord added the comment:
Committed revision 87003.
--
resolution: -> fixed
stage: -> committed/rejected
___
Python tracker
<http://bugs.python.org/i
Michael Foord added the comment:
(made slightly redundant by Holger's comment but I'll continue anyway)
I think the issue is that setUp / tearDown are used for two different purposes.
The first is setting up and tearing down test infrastructure - where you do
want to see to er
Michael Foord added the comment:
Well, the original report is here:
http://code.google.com/p/unittest-ext/issues/detail?id=21
I copied all the details provided into this issue though. Obviously the
original reporter feels that they have a genuine use case.
There is also issue 9857 where
Michael Foord added the comment:
So from the stackframe you can only get to the code object not to the function
object and although the code object is also reachable from a decorator it isn't
mutable so we can't "mark it" in any way. We could in theory 're-build&#x
Michael Foord added the comment:
Global registry of code objects, hmmm... Could work. I'll prototype it and test
it with IronPython / Jython / pypy.
--
___
Python tracker
<http://bugs.python.org/issu
Michael Foord added the comment:
At the moment exception handling for setUp / tearDown / testMethod and cleanUp
functions are all handled separately. They all have to call addError and as a
result we have inconsistent handling of skips, expected failures (etc). There
are separate issues for
Changes by Michael Foord :
--
nosy: +michael.foord
___
Python tracker
<http://bugs.python.org/issue2212>
___
___
Python-bugs-list mailing list
Unsubscribe:
Michael Foord added the comment:
Presumably not an issue for 3.1/3.2.
(Terry - I assume Sean means the fix is in the bug report comment when he says
'inline'.) A patch and a test would still be nice.
--
versions: +Python 2.7 -Python 2.6
Changes by Michael Foord :
--
versions: +Python 2.6
___
Python tracker
<http://bugs.python.org/issue2212>
___
___
Python-bugs-list mailing list
Unsubscribe:
Michael Foord added the comment:
The argument order doesn't match the name (which isn't a huge deal I don't
think) - but subset in dict does match the element in container order of
assertIn.
--
___
Python tracker
<http
Michael Foord added the comment:
Committed revision 87390.
It is a stretch to see this as a bugfix rather than a new feature so probably
*shouldn't* be backported to 2.7. On the other hand the fix is combined with
the fix for issue 9857 which *is* a bugfix and *should* be backport
Michael Foord added the comment:
Correction, the fix is combined with the fix for issue 10611.
--
___
Python tracker
<http://bugs.python.org/issue9857>
___
___
Michael Foord added the comment:
Committed to Python 2.7 in revision 87406.
--
resolution: -> fixed
stage: patch review -> committed/rejected
status: open -> closed
___
Python tracker
<http://bugs.python.or
Michael Foord added the comment:
Committed to py3k in revision 87390.
--
___
Python tracker
<http://bugs.python.org/issue10611>
___
___
Python-bugs-list mailin
Michael Foord added the comment:
Improved implementation committed to 2.7 revision 87407. Method name unchanged
there.
--
___
Python tracker
<http://bugs.python.org/issue10
Michael Foord added the comment:
This is committed to 2.7 and 3.2 (using the old name assertItemsEqual in 2.7).
As we're well into the beta cycle I don't think we can change the name in 3.2.
The current failure output is very nice for comparing sequences like [1, 2, 3]
v
New submission from Michael Foord :
sysconfig assumes there will be a makefile if the platform is posix, which
isn't always true. For example IronPython on Mac OS X with mono.
This leads to a traceback on startup with IronPython 2.7:
$ ipy27
Traceback (most recent call last):
File &qu
Michael Foord added the comment:
TextTestRunner is initialised with a stream to output messages on that defaults
to sys.stderr. The correct way to redirect messages is to construct it with a
different stream.
If you want a redirectable stream then construct the runner with a stream that
Michael Foord added the comment:
Actually I can't see a good reason why not to just lookup the *current*
sys.stderr at instantiation time instead of binding at import time as is the
current behaviour.
Patch with tests will make it more likely that this change goes in sooner
rather
Michael Foord added the comment:
No, issue 9878 can't be implemented for Python 2.7 whereas the issues other
implementations have with sysconfig *could* still be resolved in 2.7 as a
bugfix. (Specifically for IronPython on Mac OS X it would mean not assuming
that being on a posix pla
Michael Foord added the comment:
Committed to py3k in revision 87582.
--
___
Python tracker
<http://bugs.python.org/issue10786>
___
___
Python-bugs-list mailin
Michael Foord added the comment:
Thanks Terry. Done. Doc changes committed revision 87679.
--
keywords: -patch
nosy: -MarkRoddy, terry.reedy
resolution: -> accepted
stage: needs patch -> committed/rejected
status: open -> closed
type: feature request -&
Michael Foord added the comment:
I'm fine with this functionality being added in 3.3.
--
___
Python tracker
<http://bugs.python.org/issue10775>
___
___
Pytho
Michael Foord added the comment:
Committed revision 87685.
It would be nice to see this included in the Mac OS X and Windows distribution,
but I guess that applies to the *whole* Tools/ directory.
--
resolution: -> accepted
stage: needs patch -> committed/rejected
status
Michael Foord added the comment:
This doesn't appear to be true on py3k (traceback.format_exc is used to
preserve the original traceback). Need to check on Python 2.7.
--
versions: -Python 3.2
___
Python tracker
<http://bugs.python.org/is
Michael Foord added the comment:
In Python 3.2 assertItemsEqual has been replaced with assertCountEqual that has
a completely different implementation and error format. The implementation and
error output will be backported to the assertItemsEqual method of 2.7 (and to
unittest2).
Error
Michael Foord added the comment:
Same is true of Python 2.7 - looks like an invalid error report.
--
resolution: -> invalid
stage: needs patch -> committed/rejected
status: open -> closed
___
Python tracker
<http://bugs.python.or
Changes by Michael Foord :
--
status: open -> closed
___
Python tracker
<http://bugs.python.org/issue10620>
___
___
Python-bugs-list mailing list
Unsubscri
Michael Foord added the comment:
It isn't in __all__ and it is undocumented - so I'd say its private already.
--
___
Python tracker
<http://bugs.python.o
Michael Foord added the comment:
There was a discussion on python-dev about naming conventions in the standard
library. There was no clear consensus that everything non-public should start
with an underscore. Several developers thought that merely being undocumented
or not present in
Michael Foord added the comment:
I have no objection to a rename that adds a leading underscore.
--
___
Python tracker
<http://bugs.python.org/issue10
Changes by Michael Foord :
--
nosy: -michael.foord
___
Python tracker
<http://bugs.python.org/issue10859>
___
___
Python-bugs-list mailing list
Unsubscribe:
Michael Foord added the comment:
This looks good Ned. My main concern is that we make it clear from the
*Download* page that users who want IDLE to "just work" (even on 10.6) they
should install the 32 bit version.
Noting that Activestate Tcl/Tk 8.5 is a *requirement* for Tkinter
Michael Foord added the comment:
For what it's worth I prefer Raymond's original wording. Installing the
Activestate Tcl/Tk will never be a *bad* thing to do for using Python, so I
don't see a problem with stating it as a requirement. Users are unlikely to see
the current wa
Michael Foord added the comment:
There are a few issues here.
X11 is not installed by *default* on Mac OS X (it is supplied separately) so it
doesn't provide an "out of the box" solution.
Starting IDLE as 32bit alone doesn't solve the problem as it launches a
subpro
Changes by Michael Foord :
--
assignee: -> michael.foord
___
Python tracker
<http://bugs.python.org/issue10979>
___
___
Python-bugs-list mailing list
Unsubscri
Michael Foord added the comment:
There was a BDFL ruling on python-dev mailing list that assert argument names
should be (first, second).
See:
http://mail.python.org/pipermail/python-dev/2010-December/106954.html
I'm basically reverting the patch to go back to (first, second) in the
Michael Foord added the comment:
Note that I looked at making the sequence comparison code symmetric - but it
generates nice diffs for even nested containers by using prettyprint and
difflib. Switching to a symmetric output ("in first, not in second" etc) would
be very difficu
Michael Foord added the comment:
Activestate has said (replying to me on Twitter as it happens) that a patch is
available and they will do a new 8.5 release before 3.2 final.
--
___
Python tracker
<http://bugs.python.org/issue10
Michael Foord added the comment:
Ronald: The subprocess also uses Tkinter (right?) so would also require 32bit.
FWIW I'm -1 on X11 as well.
--
___
Python tracker
<http://bugs.python.org/is
Michael Foord added the comment:
The reason I think it is an issue is that a previous release of Python 2.7
could start IDLE (the initial window would appear), but a dialog would also
appear saying that it could not connect to the subprocess and IDLE would exit.
IDLE itself had been set to
Michael Foord added the comment:
Patch to docs and minor change to assertCountEqual to not use actual / expected
internally.
--
Added file: http://bugs.python.org/file20580/expected-actual.diff
___
Python tracker
<http://bugs.python.org/issue10
Changes by Michael Foord :
--
resolution: -> fixed
stage: commit review -> committed/rejected
status: open -> closed
___
Python tracker
<http://bugs.python.or
New submission from Michael Foord :
Looks like some unittest doc changes got incorrectly backported to Python 3.1.
For example the command line features using -m are new in 3.2 and don't work
with 3.1:
http://docs.python.org/py3k/library/unittest.html#command-line-inte
Michael Foord added the comment:
This incorrect section on unittest command line features was added by Eric
according to svn blame.
--
nosy: +eric.araujo
___
Python tracker
<http://bugs.python.org/issue11
Michael Foord added the comment:
The fix is to use dict methods rather than accessing members through the
instance. It will have to wait until 3.2 is out now though.
--
___
Python tracker
<http://bugs.python.org/issue11
Changes by Michael Foord :
--
assignee: -> michael.foord
___
Python tracker
<http://bugs.python.org/issue11133>
___
___
Python-bugs-list mailing list
Unsubscri
Michael Foord added the comment:
Care to provide a patch Noufal?
--
nosy: +michael.foord
___
Python tracker
<http://bugs.python.org/issue11151>
___
___
Python-bug
New submission from Michael Foord :
Reported by a user and verified by me with both Python 2.7 and 3.2.
Trying to run tests by module or package name seems to fail.
directory structure:
project root: C:\Users\hpierson\Projects\pytest
\test
__init__.py (empty
Michael Foord added the comment:
__dict__ as a property is documented as an exception to the "no code execution"
claim.
The patch is not sufficient - instances may have a class member "__dict__"
whilst still having an instance __dict__. Alternatively the "__dict__&q
New submission from Michael Foord :
When building releases with sdist (and other distribution building options)
missing metadata should not cause warnings. For public projects this is useful
(i.e. projects uploaded to PyPI), but not for internally built distributions.
(If a distribution is
Michael Foord added the comment:
skip* functions are missing 'new in' documentation. These need to be correct
for 2.7 and 3.1 / 3.2 as well.
Plus the example of assertRaises as a context manager sucks.
http://docs.python.org/dev/library/unittest.html#unittest.TestCase.as
Michael Foord added the comment:
Yes. The standard tests should be wrapped in a suite before being passed into
load_tests. That's a bug - thanks for catching it.
--
assignee: -> michael.foord
nosy: +michael.foord
___
Python tracke
Michael Foord added the comment:
The list in your example is a *class attribute* not an instance attribute, so
yes it is only initialised once. You can still access it through the instance
(self) because of Python member lookup rules.
If you want one list per instance then initialise it in
Michael Foord added the comment:
Because strings are immutable. Your list access (self.list.append) mutates the
existing list in place.
Because strings are immutable you += is exactly equivalent to the following
code:
self.string = self.string + str(i)
The first lookup of self.string
Michael Foord added the comment:
Damn. If assertSameElements has already shipped with the existing
implementation then we can't change it. The documentation really needs
clarifying to make it clear that it ignores duplicates.
I would be happy with a 'check_order&#x
Changes by Michael Foord :
--
assignee: -> ezio.melotti
___
Python tracker
<http://bugs.python.org/issue7837>
___
___
Python-bugs-list mailing list
Unsubscri
Michael Foord added the comment:
Hmm... assertTrue(...) is semantically different from assertEqual(True, ...).
--
___
Python tracker
<http://bugs.python.org/issue7
Michael Foord added the comment:
Dino - if you use assertRaises as a context manager the exception is kept as an
attribute on the context. You can make assertions about the exception after the
with block has executed.
--
___
Python tracker
<h
Michael Foord added the comment:
assertSameElements doc issue fixed in revision 77997. Also improved example for
assertRaises as a context manager and added versionadded to the test skipping
section. Revisions 77999-78002.
Thanks for sorting the version changed / added in the Py3k docs Ezio
Michael Foord added the comment:
What made you think that would work? In your example foo.test_suite is neither
a test nor a suite but a function.
--
___
Python tracker
<http://bugs.python.org/issue7
Michael Foord added the comment:
The problem this fix was trying to fix was that if you provide a docstring for
your test then the test name is ommitted in the report.
This could be fixed in the _TextTestResult instead - changing the
getDescription() method to always include str(test
Michael Foord added the comment:
So it's a feature request then...
--
___
Python tracker
<http://bugs.python.org/issue7501>
___
___
Python-bugs-list m
Michael Foord added the comment:
Fixed in revision 78010.
--
resolution: -> fixed
stage: test needed -> committed/rejected
status: open -> closed
___
Python tracker
<http://bugs.python.o
201 - 300 of 1077 matches
Mail list logo
