[Python-Dev] Purpose of Doctests [Was: Best practices for Enum]
Olemis Lang
olemis at gmail.com
Tue May 21 01:59:11 CEST 2013
More information about the Python-Dev mailing list
Tue May 21 01:59:11 CEST 2013
- Previous message: [Python-Dev] Purpose of Doctests [Was: Best practices for Enum]
- Next message: [Python-Dev] Purpose of Doctests [Was: Best practices for Enum]
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On 5/20/13, Olemis Lang <olemis at gmail.com> wrote: [...] > On 5/20/13, Michael Foord <fuzzyman at voidspace.org.uk> wrote: [...] > >> * Tool support for editing within doctests is *generally* worse > > this is true , let's do it ! > [...] >> * Typing >>> and ... all the time is really annoying > > ... I have faith ... there should be something like this for vim ... I > have faith ... ;) > FWIW ... an option could be to combine >>> auto-completion (in the end that's yet another indentation ;) to this http://architects.dzone.com/articles/real-time-doctest-checking-vim ... and I could better enjoy my vim + python development experience ;) -- Regards, Olemis. Apache⢠Bloodhound contributor http://issues.apache.org/bloodhound Blog ES: http://simelo-es.blogspot.com/ Blog EN: http://simelo-en.blogspot.com/ Featured article:
- Previous message: [Python-Dev] Purpose of Doctests [Was: Best practices for Enum]
- Next message: [Python-Dev] Purpose of Doctests [Was: Best practices for Enum]
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Python-Dev mailing list