On 16 Jul 2024, at 1:36, Oscar Benjamin wrote:
> I like this idea. I would want it to have behaviour that
> --lf=failed.txt checks if the file exists and if not populates it with
> the contents from the pytest ---lf cache. Then you could do:
>
> $ pytest
> < runts tests, some fail >
> $ pytest --l
>> How would one access ``.pytest_cache/lastfailed`` from GitHub Actions for
>> example? Just copy'n'paste from the log output seems more intuitive for most
>> people, so the parsing should be kept.
>>
>> I'm not sure how user-friendly it is to explain how to copy
>> ``.pytest_cache/lastfailed``
``.pytest_cache/lastfailed``, so I think ``--dump-lf`` would still be useful.
> I know this is not exactly the feedback you wanted, but thought I would throw
> the idea in there for your consideration.
Totally valid feedback. Thanks!
Regards,
Florian
>
> Cheers,
> Bruno
>
ytest report summary
syntax, are there any other formats that would be useful to support for
cut'n'paste from CI?
If you try the plugin, please give feedback on whether you found it useful and
understand how it works.
Regards,
Florian Schulze
___
the same.
Regards,
Florian Schulze
On 21 Mar 2021, at 23:46, Brian Okken wrote:
Yep. I think that’s it. I totally forgot about raising. I’ll try
it out.
- Brian
On Mar 21, 2021, at 1:06 PM, Bruno Oliveira
wrote:
there is no option to only accept existing keys.
I'm not sure what
first. Is that a bug? Also is it possible to get a native stack trace
for that? --tb=native has no effect on --full-trace.
Regards,
Florian Schulze
___
pytest-dev mailing list
pytest-dev@python.org
https://mail.python.org/mailman/listinfo/pytest-dev
plugin and can eventually be
moved to core.
The issues showed me several use cases I didn't think about and I think
it's not trivial to find a good cli ui for all of them.
Regards,
Florian Schulze
___
pytest-dev mailing list
pytest-dev@python.or
On 2 May 2019, at 11:28, Florian Bruhin wrote:
Hey,
On Thu, May 02, 2019 at 11:22:08AM +0200, Florian Schulze wrote:
Is there a way to run a bunch of tests like with --lf but don't clear
the cache when they pass? This would be mighty helpful for git
bisect.
For now I helped myself by co
o the command line.
Regards,
Florian Schulze
___
pytest-dev mailing list
pytest-dev@python.org
https://mail.python.org/mailman/listinfo/pytest-dev
On 31 Jul 2018, at 1:42, Bruno Oliveira wrote:
The pytest team is proud to announce the 3.7.0 release!
The new deprecation for directly called fixture functions promptly
revealed cases where I accidentally did that.
Thanks!
Regards,
Florian Schulze
change in transfer behaviour makes it 4.0, because it
*will* affect people. It changed things in devpi-server which
necessitates (small) changes. For others it might have way more far
reaching effects.
Regards,
Florian Schulze
2018-03-20 16:03 GMT+01:00 Florian Schulze :
On 20 Mar 2018, at 15
ss is
also marked as slow. The PR fixes that.
Regards,
Florian Schulze
___
pytest-dev mailing list
pytest-dev@python.org
https://mail.python.org/mailman/listinfo/pytest-dev
s way off topic.
Regards,
Florian Schulze
Am 14.03.2018 um 10:07 schrieb Florian Schulze:
On 14 Mar 2018, at 10:00, RonnyPfannschmidt wrote:
Sounds reasonable,
Ok
i would like to note that by now i believe integrating linting into
normal testing is a step back since the reporting needs ar
haven't seen
anything that works server side (or as a bot) on a per commit base (Open
Source and not only as a GitHub Service).
Regards,
Florian Schulze
Am 14.03.2018 um 09:35 schrieb Florian Schulze:
Hi!
I'd like to propose moving pytest-pep8 from pytest-dev on Bitbucket
to
Git
Hi!
I'd like to propose moving pytest-pep8 from pytest-dev on Bitbucket to
GitHub and my pytest-flakes from my GitHub repository to pytest-dev.
Since I use both myself all the time, I would continue maintaining them.
Thoughts? Process?
Regards,
Florian Sc
eps every once in a while.
The goal will be the same, but with less disruption.
Regards,
Florian Schulze
___
pytest-dev mailing list
pytest-dev@python.org
https://mail.python.org/mailman/listinfo/pytest-dev
users
Hidden things are not seen (duh). Before deprecation warnings were
shown, no one cared. I think it's better if it's easy for people to hide
warnings in their own code bases.
Regards,
Florian Schulze
___
pytest-dev mailing list
pytest-dev@p
know whether this trailing dot missing there
too?
I don't think that is related. It might be used for URL generation.
I noticed that the blog url in publishconf.py is http://pytest.org/blog,
not sure if that is used for URL generation somewhere.
Regards,
Florian Sc
On 29 Nov 2017, at 23:44, Maik Figura wrote:
> @Florian should contents/CNAME also contain a trailing dot?
Not sure what you mean.
Regards,
Florian Schulze
___
pytest-dev mailing list
pytest-dev@python.org
https://mail.python.org/mailman/listi
The missing trailing dot in the CNAME was the issue, should work again.
TTL is one hour, so some DNS caches might still need to catch up.
Regards,
Florian Schulze
On 29 Nov 2017, at 17:27, Florian Schulze wrote:
We moved the domain to another provider, I thought I copied everything
over
We moved the domain to another provider, I thought I copied everything
over. I'll check, maybe I missed a trailing dot or something.
Regards,
Florian Schulze
On 29 Nov 2017, at 15:05, Maik Figura wrote:
Hello Bruno,
I am experiencing the same.
To me it seems that the DNS delegati
I had to do:
pip install --no-cache-dir -U
https://devpi.net/nicoddemus/dev/+f/e50/b5a054e0007ca/pytest-3.2.0-py2.py3-none-any.whl
This works with devpi tests as well.
Regards,
Florian Schulze
___
pytest-dev mailing list
pytest-dev@python.org
tried 3.1.x.
Regards,
Florian Schulze
___
pytest-dev mailing list
pytest-dev@python.org
https://mail.python.org/mailman/listinfo/pytest-dev
easy to find docs on how
to actually fix it, even if the old stuff was undocumented. An example
diff is often enough.
Regards,
Florian Schulze
On 14 Jul 2017, at 0:45, Bruno Oliveira wrote:
Hi everyone,
I have prepared a package for the 3.2.0 release and it would be great
if
people could
Could this issue be related, or even be the same?
https://github.com/tox-dev/tox/issues/426
Regards,
Florian Schulze
On 24 Jun 2017, at 15:39, RonnyPfannschmidt wrote:
> Hi everyone,
>
> after investigating the issue i pretty much had to deduce that a
> horrible mistake happened
Fixed
Regards,
Florian Schulze
On 31 May 2017, at 17:51, Bruno Oliveira wrote:
> Hi everyone,
>
> An issue has been raised in the bug tracker asking to redirect
> docs.pytest.org/latest/* to docs.pytest.org/en/latest/*:
>
> https://github.com/pytest-dev/pytest/issues/24
ngs.
Here, "pytest.raises" deals with the dependent code block's exception
raising behaviour -- allowing None (to signal: no exception expected)
does not change or much extend this functionality.
I think it also reads well. Which exceptions are expected to be raised?
None.
Hi!
Personally I disable the line length limit and keep all other warnings.
For old projects I only fix pep8 issues in code I edit in a commit. A
massive cleanup disrupts history and especially "blame" too much IMHO.
Regards,
Florian Schulze
On 17 Mar 2017, at 10:09, Ronny Pf
Hi!
The v16 is because it uses time based version numbering.
Regards,
Florian Schulze
On 6 Dec 2016, at 12:52, Floris Bruynooghe wrote:
Hi,
Personally I also don't mind the dependency. Though I know in the past
we've had a policy of keeping dependencies to a minimum as well a
for
leaks.
Regards,
Florian Schulze
___
pytest-dev mailing list
pytest-dev@python.org
https://mail.python.org/mailman/listinfo/pytest-dev
rging.
Regards,
Florian Schulze
___
pytest-dev mailing list
pytest-dev@python.org
https://mail.python.org/mailman/listinfo/pytest-dev
I don't think it's urgent at all. The plugin works and pytest
deprecations are visible since 3.0, the rest is just nice to have.
Regards,
Florian Schulze
On 22 Sep 2016, at 12:30, Ronny Pfannschmidt wrote:
Hi Florian,
thanks for the update.
im currently not too familiar with the
ons differently from in test warnings (the thing
pytest-warnings does atm but doesn't separate).
Regards,
Florian Schulze
On 22 Sep 2016, at 10:00, Ronny Pfannschmidt wrote:
im not aware of anyone signing up for that
as far as i remember there also was no further development on the
plugin
I'd say it depends on how much work a release is. If it's ok for you,
then do a release. If it takes too much time in comparison to the
severity of the issues, then old back a bit longer.
Regards,
Florian Schulze
On 23 Aug 2016, at 18:12, Bruno Oliveira wrote:
Hi everyone,
Since
Besides one issue in devpi-server where we use monkeypatch in a non
regular way (which Holger already warned me about) pytest 3.0.0 works
fine with devpi tests!
None of my other stuff is anywhere near the complexity of devpi. So from
my side pytest 3.0.0 looks good.
Regards,
Florian Schulze
For some reason I had to use this to get it installed:
pip install -U -i https://devpi.net/nicoddemus/dev pytest==3.0.0
Regards,
Florian Schulze
On 18 Aug 2016, at 20:11, Bruno Oliveira wrote:
> Hello everyone,
>
> The pytest team has generated a 3.0.0 release candidate and woul
Is it possible to preview the blog post somewhere?
> On 17.08.2016, at 02:52, Bruno Oliveira wrote:
>
> Hi everyone!
>
> There are now 4 open PRs which handle the last remaining issues for 3.0:
>
> * WIP Change outcome to 'passed' for xfail unless it's strict:
> https://github.com/pytest-dev/
Hi!
Since this is not a breaking change, but a feature, it can easily be
added in 3.1, right? If so, I'd say postpone it.
Regards,
Florian Schulze
On 15 Aug 2016, at 3:15, Bruno Oliveira wrote:
Hi everyone,
I've worked on the weekend on the issue discovered by Florian on the
q
Hi!
I know Holger is on vacation for a while. I doubt he got time to handle
this in August.
I would be available for development work. I got no experience with
organizational and legal stuff in regard to US based foundations when
living in Germany.
Regards,
Florian Schulze
On 8 Aug 2016
On 11 Jul 2016, at 23:16, Daniel Hahler wrote:
On 09.07.2016 13:02, Florian Schulze wrote:
I just released https://pypi.python.org/pypi/pytest-pdb
It adds a ``whichtest`` command to pdb. It prints identifying
information about the current test you are in. Much easier than
looking through
Hi!
I just released https://pypi.python.org/pypi/pytest-pdb
It adds a ``whichtest`` command to pdb. It prints identifying
information about the current test you are in. Much easier than looking
through the stack trace of ``which`` and it prints info on parameters.
Regards,
Florian Schulze
During one of the discussions I agreed to work on a small bit. Problem
is, I didn't make a note and can't remember and I'm not on the list in
the wiki
(https://github.com/pytest-dev/pytest/wiki/pytest-3.0-checklist). Does
anyone remember?
Regards,
Florian Schulze
On 8 Jul
drawbacks for example.
Regards,
Florian Schulze
___
pytest-dev mailing list
pytest-dev@python.org
https://mail.python.org/mailman/listinfo/pytest-dev
> thing. Maybe there isn't. Haven't given it much thought yet.
I would like if @pytest.mark.parametrize works with fixtures.
Regards,
Florian Schulze
___
pytest-dev mailing list
pytest-dev@python.org
https://mail.python.org/mailman/listinfo/pytest-dev
Ahh, I knew I read about such an option at some point. Thanks for the
reminder.
Looks like pytest doesn't have the necessary hooks to measure fixture
calls.
Regards,
Florian Schulze
On 28 Apr 2016, at 14:00, Bruno Oliveira wrote:
On Thu, Apr 28, 2016 at 7:57 AM Florian Schulze
Hi!
Is there a plugin to measure the execution time of tests and fixtures
and the usage count of fixtures? There seems to be a profile plugin, but
that is way to detailed for my need. I want to find slow tests and
fixtures to see if I can optimize them.
Regards,
Florian Schulze
rd to figure
out. Not sure I actually used the correct one in the end, but it worked
for me at least.
Regards,
Florian Schulze
___
pytest-dev mailing list
pytest-dev@python.org
https://mail.python.org/mailman/listinfo/pytest-dev
anguage
itself seems to be too restrictive to manipulate the content further.
Regards,
Florian Schulze
___
pytest-dev mailing list
pytest-dev@python.org
https://mail.python.org/mailman/listinfo/pytest-dev
On 12 Apr 2016, at 6:19, Brianna Laugher wrote:
> Nice! Could someone add a link to the github repo/instructions about how to
> add a new feed, and maybe also an explicit link to the planet rss feed?
On my todo list already :)
Regards,
Florian S
//blog.dbrgn.ch/tags/pytest/
PR for that merged.
I switched from genshi to the default planet template thingy and that
seems to got rid of the rendering issues.
Regards,
Florian Schulze
___
pytest-dev mailing list
pytest-dev@python.org
https://
side.
I doubt it would be very useful, because outside http resources are
embedded and probably blocked by browsers.
Regards,
Florian Schulze
___
pytest-dev mailing list
pytest-dev@python.org
https://mail.python.org/mailman/listinfo/pytest-dev
se.
When this setup is finished, I'd like to transfer the repository to the
pytest-dev organization. I'll add proper documentation before that.
Regards,
Florian Schulze
___
pytest-dev mailing list
pytest-dev@python.org
https://mail.python.
I talked to Holger and will setup a Planet VM over the weekend. If it
goes as planned, there will be a repository where people can make a PR
to add their feed and the rest is automatic. If it's not fully
automatic, it will at least be very easy to update :)
Regards,
Florian Schulze
On
On 23 Feb 2016, at 13:58, Florian Schulze wrote:
On 23 Feb 2016, at 11:54, Bruno Oliveira wrote:
Hey Florian,
Thanks for taking the time to try it out.
On Tue, Feb 23, 2016 at 4:57 AM Florian Bruhin
wrote:
Other than pytest-hypothesis breaking because it doesn't expect the
dash i
on number,
>
>
> That's strange, as having that dash is correct for pre-releases according
> to the semver spec[1].
Relevant is PEP404. The version should be 2.9.0.rc1 if I'm not mistaken.
Regards,
Florian Schulze
___
pytest-dev m
iding the info, but not directly in the
files.
Regards,
Florian Schulze
___
pytest-dev mailing list
pytest-dev@python.org
https://mail.python.org/mailman/listinfo/pytest-dev
just fix any problems
myself, or whether I ask for a followup.
Regards,
Florian Schulze
___
pytest-dev mailing list
pytest-dev@python.org
https://mail.python.org/mailman/listinfo/pytest-dev
ch at all.
Regards,
Florian Schulze
___
pytest-dev mailing list
pytest-dev@python.org
https://mail.python.org/mailman/listinfo/pytest-dev
won't lead to errors, so it's pretty much a waste of your
time and CPU time.
Regards,
Florian Schulze
On 7 Feb 2016, at 4:53, Goncalo Morgado wrote:
Hi,
Thank you for this great lib!
I have an app that takes a config file with key/value pairs, that I
would
like to test thoroughl
Looks good overall. I think the perks are just fine.
I think there is a typo: Brianna Laughner should be Brianna Laugher if
I'm not mistaken.
Regards,
Florian Schulze
On 3 Feb 2016, at 11:00, holger krekel wrote:
Hey all,
i've done a indiegogo sprint page which is still in
I'd say letsencrypt. I wrote a tool to make it easy to create a
certificate locally without giving their tool root access:
https://pypi.python.org/pypi/letsencrypt-remote
Regards,
Florian Schulze
On 22 Jan 2016, at 23:30, Holger Krekel wrote:
Hi,
Not sure I get to this before I tak
I just list the usernames after the change and if the user contributed
for the first time, the fullname as well. See this for example:
https://github.com/fschulze/mr.developer/blob/master/CHANGES.rst
Regards,
Florian Schulze
On 11 Dec 2015, at 16:14, holger krekel wrote:
On Fri, Dec 11
stly a dropin replacement.
It doesn't support Python 2.6 though, so we either have to drop support
for that as well, or restore compatibility. For now it looks like one
place is affected in catchlog.
Unfortunately catchlog doesn't fix the pypy test failures in
devpi-server, but at least there
that Holger is away for at least another 2 hours. I don't know
whether he will be able to take a look then.
Regards,
Florian Schulze
___
pytest-dev mailing list
pytest-dev@python.org
https://mail.python.org/mailman/listinfo/pytest-dev
tem or if you have a lot of
constant changes in the same files in each commit (I backup database
dumps with git to keep some history).
Regards,
Florian Schulze
___
pytest-dev mailing list
pytest-dev@python.org
https://mail.python.org/mailman/listinfo/pytest-dev
Sounds reasonable, thanks for the list! Maybe we should put that
somewhere findable? The tox docs, or at least link from there?
Regards,
Florian Schulze
On 21 May 2015, at 10:52, Florian Bruhin wrote:
* Florian Schulze [2015-05-21 10:16:03
+0200]:
On 21 May 2015, at 9:17, raph
installation
because of unicode in the long_description. With passenv = LC_ALL, LANG
it works. Question is, should these envvars be added by default or does
everyone have to update their tox.ini?
Regards,
Florian Schulze
___
pytest-dev mailing l
ed
quite a few other python packages of mine to pytest though.
Regards,
Florian Schulze
On 7 May 2015, at 17:49, Aryé H wrote:
Hi,
Our question is on the right approach to testing such a framework ?
1) start with low level unit tests and strive to mock out the DB
2) continue with higher leve
I tested a bit and had no issues so far.
Regards,
Florian Schulze
On 26 Mar 2015, at 9:38, holger krekel wrote:
Hi everybody,
You can install either form trunk or with:
pip install
https://devpi.net/hpk/dev/+f/14c/de91b1106c937/pytest-2.7.0.tar.gz
Please install it and work with it
aclasses, mocks
etc? Python is very dynamic as you most likely know :)
Regards,
Florian Schulze
___
pytest-dev mailing list
pytest-dev@python.org
https://mail.python.org/mailman/listinfo/pytest-dev
Hi!
Same here. Also using the hash, will the PR update if you make further
commits, like it does with a branch?
Regards,
Florian Schulze
On 13 Aug 2014, at 18:11, Anatoly Bubenkov wrote:
That's true that hg branches are not meant to be used for feature
branches,
and that's clea
I think you should go for the orange links, the black ones don't stand
out enough.
Regards,
Florian Schulze
On 2 Jun 2014, at 8:58, holger krekel wrote:
I am not sure about colors everywhere. For now, i went with only
black
text (links get underlined). Second best i like orange lin
I like the colored version, but maybe the sites colors should be
adjusted to use colors from the logo now.
Regards,
Florian Schulze
On 1 Jun 2014, at 12:09, holger krekel wrote:
Hi all,
i just put the new pytest logo online:
http://pytest.org/latest/
Wondering if it's too colorful a
goat in some way in it?
If animals are used, then they should be very stylized, so the logo
works with few or only one color as well.
- any colors you'd prefer?
Maybe fitting to the current docs.
- any testing tool related logos you like?
No idea.
Regards,
Florian Schulze
_
Hi!
You didn't include the test_method, maybe you just forgot the 'self' as
first parameter?
Regards,
Florian Schulze
On 10 Feb 2014, at 4:51, Nikolaus Rath wrote:
Hello,
I don't understand why the following test fixture works for the test
function, but fails for t
e
> script to automate the download/unpack/test/post-results steps?
I'd say the biggest advantage is to not execute stuff on your own server. They
have to deal with that anyway.
Regards,
Florian Schulze
___
Pytest-dev mailing list
Pytest-dev@python.org
https://mail.python.org/mailman/listinfo/pytest-dev
ssion', dir=1)
> elif request.scope == 'function':
> return _basetmp.ensure('tests', dir=1)\
> .make_numbered_dir(request.function__name__)
If something like this is chosen, then please use a list or tuple, not a comma
separated string.
Regards,
Florian Schulze
On 11.10.2013, at 12:57, holger krekel wrote:
> On Fri, Oct 11, 2013 at 12:51 +0200, Florian Schulze wrote:
>> I would expect the behaviour you describe for scope="each" to be the default
>> for a fixture without a scope. Why introduce a new scope for that? Am I
ould expect the
new behaviour instead of the current one. But maybe I'm missing something,
because of the abstract example.
Regards,
Florian Schulze
On 11.10.2013, at 10:40, holger krekel wrote:
> Hi pytest users and developers,
>
> I'd like to discuss and get feedback on
On 29.09.2013, at 13:15, holger krekel wrote:
> On Sun, Sep 29, 2013 at 11:41 +0200, Florian Schulze wrote:
>> On 29.09.2013, at 08:58, holger krekel wrote:
>>
>>> TLDR, i suggest to go for ``yield_fixture`` for pytest-2.4.
>>
>> +1
>
> coming b
On 29.09.2013, at 08:58, holger krekel wrote:
> TLDR, i suggest to go for ``yield_fixture`` for pytest-2.4.
+1
___
Pytest-dev mailing list
Pytest-dev@python.org
https://mail.python.org/mailman/listinfo/pytest-dev
t introducing a new "replace"
> method name? IMO it's rather intuitive to just make setattr accept
> the new signature, although the docstring will need a bit of explaining.
You can easily support both, so I would say go for it
82 matches
Mail list logo
