-
Notifications
You must be signed in to change notification settings - Fork 29
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
pytest warnings #57
Comments
Hi Tomasz. I think the concept of a "normal build, install, and test cycle" is mutable, and in this case the steps for setting up a Typogrify development environment (including how to run the tests) are clearly proscribed in the README. When following those steps, I cannot replicate the problem described here. As far as issuing a new release, nearly all the recent changes relate to tooling/infrastructure and don't impact Typogrify's behavior. That said, I will do my best to issue a new release as soon as I can. |
I'm not developing any module. Whatever is in that file has nothing to do with those pytest warnings. |
Just in case .. in top part of the pytest output you have all necessary details of the build env. |
Be that as it may, the tests pass just fine for me via this project's canonical instructions, and I don't have time to dig into this issue any further. Would you propose a pull request to address what you perceive as areas in need of improvement? |
I fully understand that. Just please have look one more time on that output to see list of pytest extensions used by pytest in that test. If you have no time now maybe later .. no rush. |
Any update about his issue? 😃 |
Looks like typogrify is not fullly pytest 4.0 ready.
Just normal build, install and test cycle:
BTW: do you have any plans to make new release?
The text was updated successfully, but these errors were encountered: