the the new async api
that's not materialized yet i think.
holger
>
> best,
> Ronny
>
> On 12/21/2012 10:51 AM, holger krekel wrote:
> > Hi testing folks, hi Jason,
> >
> > i am looking at some recent pytest issues and would like to simplify
> > pytest's
Hi folks,
this list is going to move to move python.org, probably even today.
The new list address is:
pytest-...@python.org
the commit list will be:
pytest-com...@python.org
The old addresses (py-dev@codespeak.net,py-...@codespeak.net) will
continue to function so the move shouldn't
Hi testing folks, hi Jason,
i am looking at some recent pytest issues and would like to simplify
pytest's internal fixture handling. One obstacle/complication are
yield-tests, i.e. the style of producing tests with a generator::
def test_gen(self):
for x in range(10):
yie
plicit ones.
All autouse=True fixtures are implicit - they are not requested explicitely
through a funcarg or a @pytest.mark.usefixtures(...) decoration.
best,
holger
> On Wed, Dec 19, 2012 at 1:42 AM, holger krekel wrote:
>
> > On Tue, Dec 18, 2012 at 21:11 +0100, Floris Bruynooghe
On Tue, Dec 18, 2012 at 21:11 +0100, Floris Bruynooghe wrote:
> On 16 December 2012 12:23, holger krekel wrote:
> > Currently, if you define e.g. an autouse fixture function it is going to
> > be called _after_ the xUnit setup functions. This is especially
> > surprising
On Mon, Dec 17, 2012 at 12:24 +0200, Tomi Pieviläinen wrote:
> I have a a simulation that has different kinds of forces to simulate,
> each a different function. I have implemented those functions in
> several modules: baseline python (Numpy), C (accessed via ctypes) and
> PyCUDA. I need to make su
Hi lahwran, all,
On Sun, Dec 16, 2012 at 23:34 -0700, lahwran wrote:
> Hi, I've got a bit of a problem related to how pytest determines the fully
> qualified name for a module. I have a django 1.3 layout project which has
> an __init__.py at its root, due to oddities in how django functions. so I
ilable.
Do you know that you can use @pytest.fixture(autouse=True) on xUnit
setup methods already with the current release? We could think about
introducing a ``@pytest.setup`` shortcut, but i don't think it's worth it.
best,
holger
> On Sun, Dec 16, 2012 at 12:24 PM, holger krekel
...):
...
In this case there is no positional argument but you can get the
current function under test via ``request.function``.
I think it's clearer to add that extra line.
holger
> On 12/16/2012 12:23 PM, holger krekel wrote:
> >Hi all,
> >
> >Currently, if you d
Hi all,
Currently, if you define e.g. an autouse fixture function it is going to
be called _after_ the xUnit setup functions. This is especially
surprising when you do a session-scoped autouse fixture. I am wondering
if we could reverse the order, i.e. call fixture functions (including
autouse-f
Hi Adam,
On Mon, Nov 26, 2012 at 11:25 -0500, Adam Goucher wrote:
> If I wanted to try and add https://github.com/adamgoucher/pytest-marks
> to the main pytest distribution. Is there a process for consideration,
> code style rules, etc.?
posting here is just fine. After discussion and agreemen
se discovery and calling
Thanks in particular to Thomas Waldmann for spotting and reporting issues.
See
http://pytest.org/
for general information. To install or upgrade pytest:
pip install -U pytest # or
easy_install -U pytest
best,
holger krekel
___
On Tue, Nov 20, 2012 at 09:52 +, Floris Bruynooghe wrote:
> On 19 November 2012 22:04, holger krekel wrote:
> > A tmpdir requested in function-scope and a tmpdir requested with session
> > scope would be two different directories. I don't see a problem with this,
> &
On Mon, Nov 19, 2012 at 22:04 +, holger krekel wrote:
> > > the one in ``something(monkeypatch)`` above. monkeypatch-finalizers
> > > would raher be called after a test function using the "other"
> > > fixture has finalized. I am not sure if there is
On Mon, Nov 19, 2012 at 21:53 +, Floris Bruynooghe wrote:
> > @pytest.fixture(scope="any")
> > def monkeypatch(...):
> > # unmodified builtin monkeypatch implementation
> >
> > @pytest.fixture(scope="module")
> > def something(monkeypatch):
> > ...
> >
> > This
Hi folks,
while writing tests on a new project using pytest-2.3 i noticed again an
inconvience: fixtures such as tmpdir or monkeypatch could implementation-wise
easily support being called from non-function scoped fixtures. But
currently if you do::
@pytest.fixture(scope="module")
def so
est_*(...)" it is a call to such a hook, basically a 1:N
relation because there might be multiple hook functions involved coming
from multiple plugins.
best,
holger
>
> 2012/11/19 holger krekel
>
> > Hello Philipp,
> >
> > On Mon, Nov 19, 2012 at 12:41 +0100, Philipp
Hello Philipp,
On Mon, Nov 19, 2012 at 12:41 +0100, Philipp Konrad wrote:
> Hello,
>
> my name is Philipp Konrad, I am a computer science student, a young Python
> programmer and researcher from Vienna, Austria.
welcome!
> My developer experience started around two years ago in Java, but half y
, Thomas Waldmann, Ronny Pfannschmidt, Pavel Repin
and Andreas Taumoefolau for providing patches and all for the issues.
See
http://pytest.org/
for general information. To install or upgrade pytest:
pip install -U pytest # or
easy_install -U pytest
best,
holger krekel
Changes
Hi Matt,
On Fri, Nov 02, 2012 at 10:12 -0400, Matt Davis wrote:
> Hi all,
>
> I work on the AstroPy project (http://astropy.org). We bundle py.test with
> our distribution and for an upcoming release we need the fixture features
> in py.test 2.3, but we also need the bug fix from
> https://bitbuc
On Sat, Oct 27, 2012 at 23:53 +0100, Floris Bruynooghe wrote:
> On 26 October 2012 21:19, Ronny Pfannschmidt
> wrote:
> > i think just having the name setup will make people
> > wonder about the teardown again
> >
> > if i correctly recall the name setup did
> > cause people to misunderstand alre
Hi,
I find myself providing examples with "autouse" fixtures and am now
wondering if to introduce a @pytest.setup(...) decorator as a shortcut
for @pytest.fixture(..., autouse=True). Many people are used to the
concept of "setup" functions getting automatically called so i think
naming-wise it s
information. To install or upgrade pytest:
pip install -U pytest # or
easy_install -U pytest
best,
holger krekel
Changes between 2.3.1 and 2.3.2
---
- fix issue208 and fix issue29 use new py version to avoid long pauses
when printing tracebacks in long
On Mon, Oct 22, 2012 at 10:44 +0200, Ralf Schmitt wrote:
> holger krekel writes:
>
> >
> > interesting little plugin. On a general note, using "pytest_configure"
> > is not the best way to setup global state. It's better to do this::
> >
> >
Hi Ralf,
On Mon, Oct 22, 2012 at 00:53 +0200, Ralf Schmitt wrote:
> Hi,
>
> I've upload pytest-twisted to pypi [1]. It's a plugin which allows to test
> twisted code with pytest. The code is also available on github [2].
>
>
> [1] http://pypi.python.org/pypi/pytest-twisted
> [2] https://github.
method
which uses the fixture sees)
- skip pexpect using tests (test_pdb.py mostly) on freebsd* systems
due to pexpect not supporting it properly (hanging)
- link to web pages from --markers output which provides help for
pytest.mark.* usage.
On Fri, Oct 19, 2012 at 09:44 +, holger
d Alex Gaynor for helping
to get the new features right and well integrated. Ronny and Floris
also helped to fix a number of bugs and yet more people helped by
providing bug reports.
have fun,
holger krekel
Changes between 2.2.4 and 2.3.0
---
- fix issue202 - b
Hi Anto,
On Thu, Oct 11, 2012 at 22:10 +0200, Antonio Cuni wrote:
> Hi Holger, Sebastian,
>
> On 10/11/2012 03:16 PM, holger krekel wrote:
> > ah, now i get it. You want to assign the function back.
> > That is indeed not going to work as pytest then sees the rollback
>
Hi Sebastian,
On Thu, Oct 11, 2012 at 14:44 +0200, Sebastian Rahlf wrote:
> Hi Holger!
>
> >> At work we use a decorator @rollback on selected test functions which
> >> will rollback any db changes made during that test.
> >>
> >> I've recently started using pytest's dependency injection for a fe
Hi Sebastian,
On Thu, Oct 11, 2012 at 11:47 +0200, Sebastian Rahlf wrote:
> Hi!
>
> At work we use a decorator @rollback on selected test functions which
> will rollback any db changes made during that test.
>
> I've recently started using pytest's dependency injection for a few
> use cases, bot
Hi all,
a quick heads up: i am trying hard to finalize the pytest-2.3 release.
Help appreciated as documementation and code are starting to be up to a
release (i hope). What you could do is:
* read http://pytest.org/dev/fixture.html and give feedback
on readability and sense.
* try installing
On Tue, Oct 09, 2012 at 00:33 -, astrofrog wrote:
> --- you can reply above this line ---
>
> New issue 200: disable the creation of the __pycache__ directory
> https://bitbucket.org/hpk42/pytest/issue/200/disable-the-creation-of-the-__pycache__
>
> astrofrog:
>
> Is there a way to disable t
On Sat, Oct 06, 2012 at 01:08 +0100, Floris Bruynooghe wrote:
> On 6 October 2012 00:02, holger krekel wrote:
> > Hi Floris,
> >
> > On Fri, Oct 05, 2012 at 23:42 +0100, Floris Bruynooghe wrote:
> >> Hi Holger,
> >>
> >> One nice feature of
Hi Floris,
On Fri, Oct 05, 2012 at 23:42 +0100, Floris Bruynooghe wrote:
> Hi Holger,
>
> One nice feature of the funcarg/setup merge into fixture is that you
> can now return a value from an autoactive fixture and request it
> anywhere else. I didn't think of this before but this is surprisingl
Hi Anton,
On Sun, Sep 30, 2012 at 19:16 +0300, Anton P wrote:
> Hi All,
>
> I'd like to use standard logging module with py.test. Messages
> generated from test functions are visible on stdout if -s option is
> set. But log messages generated from conftest.py or other custom
> modules used inside
Hi Floris,
On Sun, Sep 30, 2012 at 12:57 +0100, Floris Bruynooghe wrote:
> Hi all,
>
> While pytest-timeout was targeting hanging/deadlocked code there have
> been various requests which relate to failing tests based on
> performance. Another issue which came up is the control of timeouts
> duri
Hi Floris,
On Sun, Sep 23, 2012 at 17:45 +0100, Floris Bruynooghe wrote:
> Hi Holger,
>
> The new api tried to make it possible to know in advance which
> funcargs are required for a test function which is a very nice thing
> to have. However I'm not sure how to get to the full list:
>
> @pytes
Hi Floris,
On Sun, Sep 23, 2012 at 21:23 +0100, Floris Bruynooghe wrote:
> Hello,
>
> As I understand it the order of setup functions being called is:
>
> pytest_runtest_setup
> funcarg resources
> @setup marked functions
>
> And if you mark pytest_runtest_setup with trylast it will be moved
>
Hi Brianna, Floris, Carl, Ronny, all,
first, let me thank for all the useful feedback you already provided.
I am back trying to finalize the next pytest release -- FYI trunk is actually
fully functional and implements all previously discussed features.
However, I am still pondering Brianna's feed
On Fri, Aug 17, 2012 at 17:32 +1000, Brianna Laugher wrote:
> Also,
>
> Would this be a roughly equivalent old-style to the smtp examples in
> http://pytest.org/dev/funcargs.html ?
>
> def pytest_funcarg__smtpMerLinux(request):
> smtp = smtplib.SMTP("merlinux.eu")
> def teardown(smtp):
>
Hi Brianna,
On Thu, Aug 16, 2012 at 18:58 +1000, Brianna Laugher wrote:
> Hi,
>
> I just spent some time reading the dev docs so these comments are just
> based on the docs and not actually using the new API. In general it
> looks pretty sensible.
thanks for your time and your feedback, I apprec
Hi Brianna,
On Thu, Aug 23, 2012 at 13:39 +1000, Brianna Laugher wrote:
> Hi,
>
> So I gave my talk on pytest at PyCon AU on the weekend :) Thought it
> might be of interest to folks here.
>
> info: http://2012.pycon-au.org/schedule/52/view_talk?day=sunday
> slides: http://www.slideshare.net/pfc
Hi Floris,
On Tue, Aug 14, 2012 at 23:41 +0100, Floris Bruynooghe wrote:
> Hello Holger,
>
> I've started experimenting a bit more with the new resource api in
> pytest-django, I haven't got very far yet but do have already some
> feedback and questions.
>
> Firstly my main issue, I don't know h
On Sun, Aug 05, 2012 at 17:31 -0400, Adam Goucher wrote:
> Whoops. Didn't look at the list reply-to settings so pulling the list
> back in. This does seem to be the cause. I commented out the
> sys.path.append in the wrapper and added
>
> def pytest_configure(config):
> sys.path.append(os.p
On Mon, Aug 06, 2012 at 21:55 +0100, Floris Bruynooghe wrote:
> On 6 August 2012 08:50, holger krekel wrote:
> > On Sun, Aug 05, 2012 at 17:14 +0200, Floris Bruynooghe wrote:
> >> On 4 August 2012 14:13, holger krekel wrote:
> >> > On Sat, Jun 30, 2012 at 12:26
Hi Floris,
On Sun, Aug 05, 2012 at 17:14 +0200, Floris Bruynooghe wrote:
> Hello Holger,
>
> On 4 August 2012 14:13, holger krekel wrote:
> > On Sat, Jun 30, 2012 at 12:26 +0100, Floris Bruynooghe wrote:
> >> As an aside however, one of my usecases for merged request/it
Hi Shay,
i agree this would be a very useful addition.
Holger
P.S.: also testing if bitbucket's issue-reply address routes my message to the
issue ...
On Sun, Aug 05, 2012 at 07:47 -, Shay Weiss wrote:
> --- you can reply above this line ---
>
> New issue 174: Configuration Files - Add a
Hi Floris, all,
i think the below from an earlier thread is an outstanding issue for the
new API ...
On Sat, Jun 30, 2012 at 12:26 +0100, Floris Bruynooghe wrote:
> As an aside however, one of my usecases for merged request/item
> objects was so I could put setup in a session-wide scoped funcarg
Hi everybody,
i am subscribed to testing questions regarding pytest on
http://stackoverflow.com/questions/tagged/py.test
and i increasingly consider it the main FAQ system. Maybe some of you
also want to subscribe (just hoover over the tag and hit "subscribe" if
you have an SO account) to s
On Thu, Aug 02, 2012 at 20:03 +, holger krekel wrote:
> On Thu, Aug 02, 2012 at 19:47 +0100, Floris Bruynooghe wrote:
> > On 2 August 2012 18:24, holger krekel wrote:
> > > On Thu, Aug 02, 2012 at 13:50 +0100, Floris Bruynooghe wrote:
> > >> Would it not make se
On Fri, Aug 03, 2012 at 09:53 +0200, Ralf Schmitt wrote:
> holger krekel writes:
>
> >
> > If we are to optionally allow pytest_funcarg__ naming with @pytest.factory
> > i wonder if renaming @pytest.factory to @pytest.funcarg would make sense
> > and contribute
On Thu, Aug 02, 2012 at 19:47 +0100, Floris Bruynooghe wrote:
> On 2 August 2012 18:24, holger krekel wrote:
> > On Thu, Aug 02, 2012 at 13:50 +0100, Floris Bruynooghe wrote:
> >> @pytest.factory(scope='session')
> >> def pytest_funcarg__foo():
> >>
Hi Adam,
On Thu, Aug 02, 2012 at 14:49 -0400, Adam Goucher wrote:
> I have a WebDriver framework that wraps Py.Test and after a bunch of
> setup stuff calls into things with
>
> run_status = pytest.main(args=arguments, plugins=[marks.MarksDecorator()])
>
> which works fine for a single executio
On Thu, Aug 02, 2012 at 19:47 +0100, Floris Bruynooghe wrote:
> On 2 August 2012 18:24, holger krekel wrote:
> > On Thu, Aug 02, 2012 at 13:50 +0100, Floris Bruynooghe wrote:
> >> On 2 August 2012 11:44, holger krekel wrote:
> >> > http://pytest.org/dev/set
On Thu, Aug 02, 2012 at 13:50 +0100, Floris Bruynooghe wrote:
> On 2 August 2012 11:44, holger krekel wrote:
> > http://pytest.org/dev/setup.html
> >
> > Hope the latter begins to make more sense.
>
> Yes, it does. I now see the power @setup. One thing you mig
On Thu, Aug 02, 2012 at 14:54 +0200, Ronny Pfannschmidt wrote:
> Hi Holger,
>
> >
> >I was thinking about allowing a function for "params":
> >
> > @pytest.factory(params=func)
> >
> >That function would receive the "config" object and maybe some
> >marker information. (It would be called at
Hi Ronny,
On Thu, Aug 02, 2012 at 13:32 +0200, Ronny Pfannschmidt wrote:
> Hi Holger,
>
> i don't see a way to determine parametrization of a global resource
> at pytest_configure time (or later)
>
> it would be nice to be able to determine them after configure for
> considering cli args
I was
Hi Again,
On Thu, Aug 02, 2012 at 07:36 +, holger krekel wrote:
> Hi Floris,
>
> On Wed, Aug 01, 2012 at 23:21 +0100, Floris Bruynooghe wrote:
> > Hello Holger,
> >
> > Apologies for not responding earlier, but I've been on holiday.
>
> You are just-i
e
> process (probably not, but that will be Django's fault, not
> py.test's).
Your feedback as always is very valuable, thanks for taking the time!
As to Django, maybe Carl can help by stating his guess if it's possible at all
to successively instantiate Django with differen
Hi all,
I've just uploaded new docs and my latest changes to the newstyle funcargs
and setup mechanism. I am getting increasingly happy about it and think
i solved most of the implementation problems now. I also moved to
writing direct release-relevant documentation now. The new main doc is
Hi Laurent,
On Thu, Jul 26, 2012 at 12:39 -0700, Brack, Laurent P. wrote:
> I was wondering if there was any way for a test case to retrieve a
> property containing arbitrary data that could be set by a hook?
Funcargs look like the natural place for this,
http://pytest.org/latest/funcargs.html
>
Hi Carl,
On Fri, Jul 20, 2012 at 12:08 -0600, Carl Meyer wrote:
> Hi Holger,
>
> I love the pytest.mark.funcarg decorator.
Good to hear! I also like it :) And i think it makes sense to just
extend the funcargs system rather than to invent a parallel "resources" one.
> I think pytest.mark.setup
Hi Floris, Ronny, Carl, all,
i've managed to do a first round of implementation of the recently
discussed resources API. For an example on what is now possible see:
http://pytest.org/dev/example/newexamples.html
As far as i see the new features did not break backward-compatibility
with exis
x27;app'
> > )
> >
> >
> >Now, during setup(), when the process is waiting for the app to boot, if
> >a keyboardinterrupt is raised (say by the user during from the test
> >execution summary screen) then it will not call the teardown() of this
> >
Hi Pärham,
On Thu, Jul 12, 2012 at 11:46 +0200, Pärham Fazelzadeh H wrote:
> Hi all,
>
> I am using py.test to perform integration and functional testing of an
> application and had some issues with interrupts and was advised to submit
> my use case.
>
> Basically the problem is related to funca
Hi Stefan,
On Tue, Jul 10, 2012 at 10:20 +0200, Stefan Scherfke wrote:
> Hi Holger,
>
> I really like the idea. However, I found one bug and have one note:
>
> > Generating and selecting variants
> > --
> >
> > …
> >
> > Without much further introduc
Hi tox users,
I'd like to find a good way to introduce multi-dimensional configuration
to tox.ini files. I have written up a draft idea on how to do it and
would appreciate feedback. I provide two examples of transformed tox.ini
files. If you have suggestions (or example tox.ini which you would
Hi John,
thanks for fixing it - i committed it to the trunk docs.
best,
holger
On Fri, Jul 06, 2012 at 22:30 -0500, John Anderson wrote:
> Turns out it was the documented setup.py PyTestCommand I found:
>
> class PyTest(TestCommand):
> def finalize_options(self):
> TestCommand.final
Hi Carl,
thanks. I agree on your points and they also connect to comments from Floris.
On Thu, Jul 05, 2012 at 17:35 -0600, Carl Meyer wrote:
> Hello Holger,
>
> On 06/29/2012 04:55 AM, holger krekel wrote:
> > I believe that the new resource parametrization facilities are a
On Sat, Jun 30, 2012 at 12:26 +0100, Floris Bruynooghe wrote:
> > On Sat, Jun 30, 2012 at 01:23 +0100, Floris Bruynooghe wrote:
> > > On Fri, Jun 29, 2012 at 10:55:23AM +, holger krekel wrote:
> > > >
> > > > def setup_directory(db):
> >
Hi Floris,
some preliminary notes, i'll probably think some more about your feedback ...
On Sat, Jun 30, 2012 at 01:23 +0100, Floris Bruynooghe wrote:
> Hello Holger,
>
> On Fri, Jun 29, 2012 at 10:55:23AM +, holger krekel wrote:
> [...]
> > Direct scopi
Hi all, particularly Floris and Carl,
i have finally arrived at the V2 resource-API draft based on the very valuable
feedback you gave to the first version. The document implements a largely
changed approach, see the "Changes from V1 to V2" at the beginning, and
focuses on usage-level documentati
On Thu, Jun 28, 2012 at 13:08 +0100, Floris Bruynooghe wrote:
> On 28 June 2012 09:15, holger krekel wrote:
> > /me does "import this" and sees: Although practicality beats purity ...
> >
> > I am still fine to consider e. g. the introduction of a pytest.current
&
On Thu, Jun 28, 2012 at 08:15 +, holger krekel wrote:
> I am still fine to consider e. g. the introduction of a pytest.current
> namespace. It could lead to make setup_X methods more powerful::
>
> import pytest
> def setup_module(): # pytest accepts it to k
On Thu, Jun 28, 2012 at 08:47 +0100, Floris Bruynooghe wrote:
> On 27 June 2012 19:36, holger krekel wrote:
> > On Wed, Jun 27, 2012 at 16:59 +0100, Floris Bruynooghe wrote:
> >> On 27 June 2012 13:57, holger krekel wrote:
> >> > Setting
ote, i now notice that it's unclear how this whole api
discussion relates to the recently introduced @parametrize decorator and
the pytest_generate_tests hook and metafunc.parametrize() call.
hum'ly yours,
holger
> On 06/27/2012 06:15 PM, holger krekel wrote:
> > On Wed, Jun 2
sy.
Right, the grep-ability was intended behaviour. It would remain
possible with the new resourcefactory markers i pondered in my
reply to Carl. Otherwise you would need to invoke "py.test --funcargs"
to get the locations.
> Other then that I've got only one comment really:
&g
On Wed, Jun 27, 2012 at 08:43 -0600, Carl Meyer wrote:
> I like it! In particular the parametrization support by passing a list
> is a quite intuitive extension of the API.
>
> "atnode" seems like an opaque arg name - what's wrong with "scope"? The
> latter name seems more intuitive to me. Would t
Hi all,
based on on initial discussions with Ronny and Floris i have now written
a usage-level document for a new test resource management API. It aims
to better support plugin and test writers in managing cross-test-suite
resources such as databases, temporary directories, etc. It generalizes
t
n, feel free to stop me :)
holger
> Regards,
> Floris
>
>
> On 25 June 2012 16:23, holger krekel wrote:
> > On Mon, Jun 25, 2012 at 15:21 +0100, Floris Bruynooghe wrote:
> >> On 25 June 2012 14:29, holger krekel wrote:
> >> > On Mon, Jun 25, 2012 at 10:
On Tue, Jun 26, 2012 at 15:07 +0100, Floris Bruynooghe wrote:
> On 25 June 2012 16:23, holger krekel wrote:
> > On Mon, Jun 25, 2012 at 15:21 +0100, Floris Bruynooghe wrote:
> >> On 25 June 2012 14:29, holger krekel wrote:
> >> > On Mon, Jun 25, 2012 at 10:55
On Mon, Jun 25, 2012 at 18:11 +0100, Floris Bruynooghe wrote:
> On 25 June 2012 15:36, holger krekel wrote:
> > On Mon, Jun 25, 2012 at 16:09 +0200, Ronny Pfannschmidt wrote:
> >> given the nature of the problem,
> >> i think its wrong to go for terminal width th
On Mon, Jun 25, 2012 at 15:21 +0100, Floris Bruynooghe wrote:
> On 25 June 2012 14:29, holger krekel wrote:
> > On Mon, Jun 25, 2012 at 10:55 +0100, Floris Bruynooghe wrote:
> >> The concrete example I have now is that it could be nice in
> >> pytest-django to be
isplay more nicely.
It's indeed true that a frontend-independent format that can be
rendered on the master would be nice ... um, html? (not sure it's a joke).
holger
> On 06/25/2012 03:54 PM, holger krekel wrote:
> >On Mon, Jun 25, 2012 at 11:06 +0100, Floris Bruynooghe wro
On Mon, Jun 25, 2012 at 11:06 +0100, Floris Bruynooghe wrote:
> On 21 June 2012 07:16, holger krekel wrote:
> > On Thu, Jun 21, 2012 at 00:16 +0100, Floris Bruynooghe wrote:
> >> An annoyance of the pytest_assertrepr_compare hook is that it can not
> >> normally acce
Hi Floris,
On Mon, Jun 25, 2012 at 10:55 +0100, Floris Bruynooghe wrote:
> Hi Holger, everyone,
>
> Yesterday a resource provider API was considered on IRC, unfortunately
> I have no logs and forgot the details already. But today I remembered
> a, possibly invalid, use case which might want to b
I quickly released a pytest-pep8-1.0.1 which includes an explicit dependency on
pytest-cache. Thanks to Hynek Schlawack for reporting.
On Wed, Jun 20, 2012 at 20:52 +, holger krekel wrote:
> i just released two new plugins:
>
> * pytest-cache-0.9 (initial) for easy caching of valu
On Thu, Jun 21, 2012 at 00:16 +0100, Floris Bruynooghe wrote:
> An annoyance of the pytest_assertrepr_compare hook is that it can not
> normally access the terminal width since usually it is called while
> stdout and stderr are being captured which breaks
> py.io.get_terminal_width(). Since I thin
i just released two new plugins:
* pytest-cache-0.9 (initial) for easy caching of values across test runs
and a new --lf option to rerun the failing tests of a previous run. Install,
basic example and API (for use by other plugins) is here:
http://packages.python.org/pytest-cache/readme.h
abenc_test.py
> schemes/test/abenc_test.py:1: in
> > from schemes.abenc.abenc_adapt_hybrid import HybridABEnc as HybridABEnc
> schemes/abenc/abenc_adapt_hybrid.py:6: in
> > from charm.toolbox.symcrypto import AuthenticatedCryptoAbstraction
&g
ary/Frameworks/Python.framework/Versions/3.2/lib/python3.2/site-packages/pytest-2.2.4-py3.2.egg/_pytest/core.py",
> line 350, in execute
> INTERNALERROR> res = method(**kwargs)
> INTERNALERROR> File
> "/opt/local/Library/Frameworks/Python.framework/Versions/3.2/l
I just did a quick release of pytest-pep8, version 0.9.1 which fixes
compatibility issues with the recent pep8 package (1.3).
See http://pypi.python.org/pypi/pytest-pep8 for more info.
best,
holger
___
py-dev mailing list
py-dev@codespeak.net
http://c
Hi Ian,
On Fri, Jun 15, 2012 at 20:32 -0400, Ian Miers wrote:
> Hi, I just started using pytest. It's lovely.
> The TLDR on this is we are getting intermittent non reproducible errors
> that change and sometimes disappear between test runs like the following :
> > import os.path
> E TypeError
Morning all,
be the goats with you.
I've finally released detox-0.9 to PYPI which brings parallelizing
tox/test runs to your console, driving the test runner of your choice.
detox has the same options and invocation as the good old
one-step-after-the-other tox, the virtualenv-based generic test r
e operations for documentation workflow
> >> if we started to use Sphinx i18n feature. I don't know you want it or
> >> not, in this time.
> >>
> >> Though I haven't used Sphinx i18n feature, I'm willing to investigate
> >> the functiona
On Wed, Jun 06, 2012 at 15:41 +0200, Ronny Pfannschmidt wrote:
> > Which plugins do you have in mind that directly could/would use it?
> >
>
> pytest-couchdbkit -> db dumps and later on db logs as well
> pytest-ghost/mozwebqa -> browser screenshots
>
> also it would be interesting for logcapture/
On Wed, Jun 06, 2012 at 15:22 +0200, Ronny Pfannschmidt wrote:
> On 06/06/2012 03:18 PM, holger krekel wrote:
> >Hi Ronny, CCing py-dev again, was lost in between,
> >
> >On Wed, Jun 06, 2012 at 14:44 +0200, Ronny Pfannschmidt wrote:
> >>On 06/06/2012 02:35 PM, ho
Hi Ronny, CCing py-dev again, was lost in between,
On Wed, Jun 06, 2012 at 14:44 +0200, Ronny Pfannschmidt wrote:
> On 06/06/2012 02:35 PM, holger krekel wrote:
> >On Tue, Jun 05, 2012 at 08:18 +0200, Ronny Pfannschmidt wrote:
> >>Hi Holger,
> >>
> >>i was
sent a pull request. Confirm it!
> >
> >https://bitbucket.org/hpk42/pytest/pull-request/14/added-japanese-translation-documentation
> >
> >thanks,
> >Tetsuya
> >
> >On Sat, Jun 2, 2012 at 8:35 PM, holger krekel wrote:
> >>Hi Tetsuya,
> >>
&
n-documentation
>
> thanks,
> Tetsuya
>
> On Sat, Jun 2, 2012 at 8:35 PM, holger krekel wrote:
> > Hi Tetsuya,
> >
> > On Sat, Jun 02, 2012 at 20:15 +0900, Tetsuya Morimoto wrote:
> >> Hi Holger,
> >>
> >> I merged the changes of 2.2.4 into m
1 - 100 of 564 matches
Mail list logo
