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
. 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
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.org
https://mail.python.org
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 copying
to 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
the 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 <florian.schu...@gmx.
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
.
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 are so
different
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 Schulze
.
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
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@python.org
https
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 Schulze
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 delegation
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
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.
Rega
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 as
licenses
for
leaks.
Regards,
Florian Schulze
___
pytest-dev mailing list
pytest-dev@python.org
https://mail.python.org/mailman/listinfo/pytest-dev
.
Regards,
Florian Schulze
___
pytest-dev mailing list
pytest-dev@python.org
https://mail.python.org/mailman/listinfo/pytest-dev
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
itself
-- Ronny
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 w
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
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 2016, at 21:59
sn'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
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
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
/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://mail.python.org
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
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
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 thoroughly, i.e all
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
version control system 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
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 list
pytest-dev@python.org
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 m...@florian-schulze.net [2015-05-21 10:16:03
+0200]:
On 21 May 2015
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 level integration tests with a DB and data
fixtures
More
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 clearly stated
On 11.10.2013, at 12:57, holger krekel hol...@merlinux.eu 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
missing something
46 matches
Mail list logo
