Skip to content
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

Fix docs on traceback styles #1417

Merged
merged 2 commits into from
Feb 27, 2016

Conversation

hackebrot
Copy link
Member

Fix traceback style docs to describe all of the available options (auto/long/short/line/native/no), with auto being the default since pytest v2.6

@hackebrot hackebrot added the type: docs documentation improvement, missing or needing clarification label Feb 27, 2016
@nicoddemus
Copy link
Member

Thanks! 😄

nicoddemus added a commit that referenced this pull request Feb 27, 2016
@nicoddemus nicoddemus merged commit 4194ddd into pytest-dev:master Feb 27, 2016
@hackebrot hackebrot deleted the fix-docs-on-traceback-styles branch February 27, 2016 21:30
@hackebrot
Copy link
Member Author

Not at all. I am thinking about creating a repo to gather user feedback on the docs...what do you think about that? (we can also talk on IRC)

@nicoddemus
Copy link
Member

How about just using the pytest's issue tracker for that? We have a docs label that can be used to track that.

@hackebrot
Copy link
Member Author

TBH I am thinking of re-organizing the user docs as a whole. Gathering feedback, thinking about a structure and coming up with actual tasks is something that I would like. Not sure how I feel about doing this on the core issue tracker, we have so many open issues already.

@nicoddemus
Copy link
Member

I think using the existing tracker is a good idea because of its high visibility plus there's already a discussion going on about this subject in #1112. We could add to that discussion and gather further feedback there (possibly by sending an email to the mailing list).

@nicoddemus
Copy link
Member

But of course feel free to create a separate repository if you think it's best. 😄

@hackebrot
Copy link
Member Author

hmmmm..you have a point there 😃

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type: docs documentation improvement, missing or needing clarification
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants