Skip to content

Conversation

blueyed
Copy link
Contributor

@blueyed blueyed commented Nov 15, 2019

  • Setting PYTHONDONTWRITEBYTECODE in the environment does not change it
    for the current process.
  • Revisit tests in general, mainly formatting.

Setting PYTHONDONTWRITEBYTECODE in the environment does not change it
for the current process.
@blueyed blueyed changed the title tests: use sys.dont_write_bytecode tests: revisit test_cacheprovider Nov 15, 2019
@blueyed blueyed force-pushed the tests-dont_write_bytecode branch from 3a3a9e5 to d7dbbaf Compare November 15, 2019 22:48
"""
)
)
testdir.makepyfile(**{"test_a.py": "def test_always_passes(): pass"})
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is the .py in test_a.py still needed with makepyfile (rather than makefile)?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No, and can also use kwargs directly. Amended.

test_b="""\
def test_b1():
assert 0
**{
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Here can use regular kwargs I suppose?

@blueyed blueyed force-pushed the tests-dont_write_bytecode branch from d7dbbaf to 4848a5a Compare November 16, 2019 22:23
@blueyed blueyed force-pushed the tests-dont_write_bytecode branch from 4848a5a to b9a3ba1 Compare November 16, 2019 22:29
@blueyed blueyed merged commit bac6eeb into pytest-dev:features Nov 17, 2019
@blueyed blueyed deleted the tests-dont_write_bytecode branch November 17, 2019 18:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants