holger krekel added the comment:
On Sun, Feb 10, 2013 at 12:43 PM, Nick Coghlan wrote:
>
> Nick Coghlan added the comment:
>
> You can use subtests to build parameterized tests, you can't use
> parameterized tests to build subtests.
I doubt you can implement parametrize
holger krekel added the comment:
On Sun, Feb 10, 2013 at 12:41 PM, Antoine Pitrou wrote:
>
> Antoine Pitrou added the comment:
>
> > Please don't commit I think we still need a discussion as to whether
> > subtests or paramaterized tests are a better approach. I ce
Changes by holger krekel :
--
nosy: +hpk
___
Python tracker
<http://bugs.python.org/issue7897>
___
___
Python-bugs-list mailing list
Unsubscribe:
http://mail.pyth
New submission from holger krekel :
Seems like pypi.python.org does not properly maintain download counters
anymore, at least for a few packages i looked at like pytest,execnet,tox,nose.
--
components: None
messages: 148447
nosy: hpk
priority: normal
severity: normal
status: open
title
holger krekel added the comment:
Michael, if you have it i'd like to see the original post/concrete use case.
thanks, holger
--
___
Python tracker
<http://bugs.python.org/is
holger krekel added the comment:
FWIW i tend to agree and would probably prefer setup/teardown to result in an
error rather than be subsumed in an expected-to-fail marked test. I guess if
one regards setup/teardown as a place to implement pre/post-conditions than the
changes suggested by
Changes by holger krekel :
--
nosy: +hpk
___
Python tracker
<http://bugs.python.org/issue10548>
___
___
Python-bugs-list mailing list
Unsubscribe:
holger krekel added the comment:
Seems the inspect.getsourcefile regression now is in the RC1 of Python2.7 as
well. I suggest to apply the "getsourcefile.patch" patch which was attached
from David. I tested it and it works fine for Python2.7 and Python3.1.
--
st
holger krekel added the comment:
Great. Also to be backported to 2.x?
holger
On Fri, May 21, 2010 at 11:32 PM, Benjamin Peterson
wrote:
>
> Benjamin Peterson added the comment:
>
> Fixed in r81432 by making linecache smarter.
>
> --
> nosy: +benjamin.peterson
&g
New submission from holger krekel :
Executing the attached "inspect_failure.py" under python2.6 or python3.1
results in an assertion error: Python fails to obtain the source code of a
function that is defined at the end of a module whose last line does not
contain a line ending
holger krekel added the comment:
Well, maybe we could introduce a "linecache.setlines" function to give
the linecache module control over its internal caching and data
handling. What do you think?
--
___
Python tracker
<http://bu
holger krekel added the comment:
David, your getsourcefile.patch looks fine (and better than mine) to me.
--
___
Python tracker
<http://bugs.python.org/issue8
holger krekel added the comment:
Thanks for helping with this! Attached is a patch that adds a keyword
"check=True" to getsourcefile so that findsource can defer existence-checking
until after cache lookup. Eventually, findsource will still raise an IOError
if it can't find
New submission from holger krekel :
Somewhere between python 3.0.1 and 3.1.2 the behaviour of inspect.findsource
changed: it does not find the source code anymore for a code object whose
filename/source is in the linecache.cache because instead of the previous::
file = getsourcefile
Changes by holger krekel :
--
nosy: +hpk
___
Python tracker
<http://bugs.python.org/issue8564>
___
___
Python-bugs-list mailing list
Unsubscribe:
http://mail.pyth
holger krekel added the comment:
FWIW checking if an imported module really comes from a certain location and
erroring out is also how py.test does it.
--
nosy: +hpk
___
Python tracker
<http://bugs.python.org/issue8
holger krekel added the comment:
Ah, thanks for the pointer. So indeed, for me truncate(0)+seek(0)
works fine for all interpreters i care for (python2.4 - 3.1.X),
previously truncate(0) was enough.
--
___
Python tracker
<http://bugs.python.
New submission from holger krekel :
Running the attached file with python3.1.1 works fine, all assertions pass.
Running it with 3.1.2 gives me this output:
$ python3.1.2/bin/python3.1 stringio_fail.py
Traceback (most recent call last):
File "stringio_fail.py", line 12, in
holger krekel added the comment:
Actually py.test catches stdout separately for setup and for the test
code. Moreover, functional or integration test code (py.test is not
only for unittests) can easily trigger some implicit logging-module
usage which cannot eaysily be factored into a testcase
holger krekel added the comment:
To recap the use case: stdout is redirected during a test function run
which might trigger arbitrary usage of logging-functionality. Not
closing the temporary file would mean that there could be as many open
files as there are test functions - or one needs to
holger krekel added the comment:
I think the issue is unrelated to py.test - it just presents a use case
as it wants to run 1000's of tests and capture stdout/stderr per each
test function, cannot guess about a test's logging-usage yet wants to
minimize memory/resource usage and
21 matches
Mail list logo
