Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • Jan 07 2019 09:21
  • Dec 15 2018 21:40
  • Sep 10 2018 11:23
  • Sep 01 2018 11:51
  • Jun 24 2018 19:37
    The-Compiler closed #76
  • Jun 24 2018 19:37
    The-Compiler commented #76
  • Jun 24 2018 15:27
    thisch commented #76
  • Jun 24 2018 15:26
    thisch commented #76
  • Jun 02 2018 07:23
    gloc-mike starred eisensheng/pytest-catchlog
  • May 30 2018 16:32
    marc1n commented #44
  • Mar 30 2018 13:32
    hlef commented #76
  • Mar 30 2018 13:14
    The-Compiler commented #76
  • Mar 30 2018 13:05
    hlef opened #76
  • Feb 23 2018 16:38
    The-Compiler closed #14
  • Feb 23 2018 16:38
    The-Compiler commented #14
  • Feb 23 2018 16:15
    thisch commented #14
  • Feb 09 2018 11:08
    lukas-bednar closed #38
  • Feb 09 2018 11:08
    lukas-bednar commented #38
  • Feb 09 2018 11:08
    lukas-bednar closed #39
  • Feb 09 2018 11:08
    lukas-bednar commented #39
Arthur Skowronek
@eisensheng
Hum
I'll comment this on the PR.
ah, this is what the script does, neat. Nevermind what I was babbling above.
Eldar Abusalimov
@abusalimov
No, I came up with it myself. It infers TOXENVfrom a Python version running inside the container, yes. And tox respects TOXENV
Eldar Abusalimov
@abusalimov
BTW I made a PR to pytest-plugin cookiecutter template some time ago (pytest-dev/cookiecutter-pytest-plugin#13) and used a similar trick to infer TOXENV from TRAVIS_PYTHON_VERSION: https://github.com/pytest-dev/cookiecutter-pytest-plugin/pull/13/files#diff-354f30a63fb0907d4ad57269548329e3R14
Arthur Skowronek
@eisensheng
i like the short form. :smiley:
Eldar Abusalimov
@abusalimov
I decided to make it more explicit and verbose (+ announce() stuff)
Arthur Skowronek
@eisensheng
yes, this is also a favorable approach
Arthur Skowronek
@eisensheng
other than this I can't find anything else aside from the evil usage of eval but oh well. :shipit:
Eldar Abusalimov
@abusalimov
:smile: I'm not who invented this, pytest itself uses a similar eval trick within its marker handling logic.
Thank you!
Eldar Abusalimov
@abusalimov
OK, everything seems to work, I'll rebase and merge then
Arthur Skowronek
@eisensheng
ok. :+1:
Eldar Abusalimov
@abusalimov
Hi, could someone take a look at #42, please? Nothing interesting there, but it hinders some more useful changes...
Michael Aquilina
@MichaelAquilina
Hi, is pytest-catchlog basically a near drop in replacement for pytest-capturelog? I have a pytest warning about a deprecated argument. Would changing to this package remove that?
Eldar Abusalimov
@abusalimov
@MichaelAquilina pretty much. That deprecation warning is fixed, though catchlog itself might warn about legacy usage of caplogfixture, like caplog.records() should be replaced with plain caplog.records, etc.
Tibo Beijen
@TBeijen
Discovered there's a gitter right after creating a PR, otherwise I'd discuss here first.
Anyway, I just added eisensheng/pytest-catchlog#54 , thoughts most welcome.
Johann Kellerman
@kellerza
Hi, is there any way to stop logger messages from the std-out print portion? All messages seem to be duplicated between std-out and the catchlog output
Pedro Algarvio
@s0undt3ch
So guys, have you thought about the project rename? Context https://github.com/saltstack/pytest-logging/issues/6#issuecomment-280744689
Tony
@Anxuae
Hi, did you plan to release a new version of this wonderful plugin pytest-catchlog? There is lots of new features but not yet available in pypi.. :(
Florian Bruhin
@The-Compiler
Hey @abusalimov and @eisensheng, we haven't talked in ages!
I took the freedom of closing some issues and PRs now that the pytest-catchlog functionality has been merged to the pytest core, I hope that's fine with you
Eldar Abusalimov
@abusalimov
@The-Compiler sure, thanks for taking care of it!
Tibo Beijen
@TBeijen
TIL pytest-catchlog is integrated into pytest