It's hard to miss contributing.md. When you create a new issue
or PR, a friendly yellow bar appears with the message:
Please review the [guidelines for
contributing](https://github.com/Pylons/pyramid/issues/new) to
this repository.
www.pylonsproject.org is limping along. It's on the
Ok, here's an attempt for the PR: https://github.com/Pylons/pyramid/pull/2545
Thank you for your patience, and thank you Steve for pointing me the
right document! I wasn't aware of its existence, as it seems not
integrated to HTML documentation (?). (I've previously found the
I totally agree, Steve, that there is much more to explore with
py.test than simple invocation we describe here. And I better
understand how you come to the pattern ``py.test mymodule/mytests.py
-q``. My experience took an other path, where I was sure that using
``py.test`` alone should work,
In this case, py.test was totally new to me. I had always used
``nose`` or ``tox`` that someone else wrote or setup.py'ed for
me. I was a beginner to py.test and test discoverability.
When I tried running tests out of the box following that pattern
via ``py.test``, it didn't work. Hmm, I
Thank you, Michael and Steve, for the quick responses.
I will open a PR on github with changes to take in consideration what you said.
@Steve:
Sure you can explicitly tell py.test to run a specific test module,
but the whole point of my suggestion is to not pass test module path
to py.test. It's
