8000 Far future: get rid of doctest options inline · Issue #1253 · scikit-learn/scikit-learn · GitHub
[go: up one dir, main page]
Skip to content

Far future: get rid of doctest options inline #1253

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.

Sign up for GitHub

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

Jump to bottom
Closed
amueller opened this issue Oct 19, 2012 · 5 comments
Closed

Far future: get rid of doctest options inline #1253

amueller opened this issue Oct 19, 2012 · 5 comments
Labels
Enhancement

Comments

@amueller
Copy link
Member

In recent versions of nose, the options NORMALIZE_WHITESPACE and ELLIPSIS can be set globally. That would be awesome.
This is only available in nose 1.2, though. As removing the flags inline would break them on older versions, I'm not sure we can ever make the switch :-/

Should we try to monkey-patch?
@GaelVaroquaux
Copy link
Member

Should we try to monkey-patch?

I'd rather not :$.

I thought that the standard Python doctest module has a way of
registering options that we could use.

@amueller
Copy link
Member Author
8000

i think the options are usually passed in the call, and we call using nose. it is possible to set options on file level, but i'd rather set them globally. i'll have another look.
?

Gael Varoquaux notifications@github.com schrieb:

Should we try to monkey-patch?

I'd rather not :$.

I thought that the standard Python doctest module has a way of
registering options that we could use.

Reply to this email directly or view it on GitHub:
#1253 (comment)

Diese Nachricht wurde von meinem Android-Mobiltelefon mit K-9 Mail gesendet.

@GaelVaroquaux
Copy link
Member

i think the options are usually passed in the call, and we call using nose. it
is possible to set options on file level, but i'd rather set them globally.
i'll have another look.

I had another close look, and I really didn't see a clean way to do this
:(. I think that this is indeed going to be a 'far future' ticket.

@amueller
Copy link
Member Author

So should we switch to file-level at least? that should be possible (I hope).

@amueller amueller mentioned this issue Nov 1, 2012
Closed
@amueller
Copy link
Member Author
amueller commented Dec 5, 2012

Far future is approximately never. closing.

@amueller amueller closed this as completed Dec 5, 2012
@jnothman jnothman mentioned this issue Oct 1, 2017
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Enhancement
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@GaelVaroquaux @amueller
0