-
Notifications
You must be signed in to change notification settings - Fork 12
Sprint post #10
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Sprint post #10
Conversation
| * [missing evaluated value in report when asserting a boolean attribute](https://github.com/pytest-dev/pytest/issues/1503) | ||
| * [improved determination of rootdir](https://github.com/pytest-dev/pytest/pull/1621) | ||
|
|
||
|
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
While you said that this is work started/finished on the sprint, perhaps it is worth to emphasize that this is not a complete list of features that will go into 3.0:
It is worth noting that this is not an exhaustive list of all features that will go into pytest-3.0; a separate post after the release will be made with all major highlights.
What do you think?
|
Nice @pfctdayelise! 😄 |
| | {.img-rounded} | {.img-rounded} | | ||
|
|
||
|
|
||
| We also spent some time designing the [stickers](https://twitter.com/pytestdotorg/status/745528947736092672) and [t-shirts](https://github.com/kvas-it/pytest-design/blob/master/tshirt_example.png). Surveys will be going out to backers who chose these perks in the fundraising campaign very soon. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
They got out last week FWIW 😉
|
ping |
|
I already gave it a 👍, so it looks good to be merged. 😁 Waiting for @pelme I guess. |
|
I assigned it to him, I didn't realise other people would see it, so I don't think he will mind if you beat him to it :) |
|
Hopefully @pelme will forgive me then! 😨 |
I evidently screwed up my master branch a bit somehow. Tried a lot of git-pulling to get it to match upstream but without success. Nevertheless, the changes shown are those relating to the new blog post and nothing else, so I give up at this point.