| /dports/devel/cquery/cquery-20180718/third_party/doctest/doc/markdown/ |
| H A D | stringification.md | 3 **doctest** needs to be able to convert types you use in assertions and logging expressions into st…
8 …the chances are you may already provide this for your own purposes. If you're not familiar with th…
30 ## ```doctest::toString``` overload
38 doctest::String toString(const udt& value) {
46 ## ```doctest::StringMaker<T>``` specialisation
51 namespace doctest {
66 return doctest::String(ex.message());
75 // adding a lambda - the signature required is `doctest::String(exception_type)`
76 doctest::registerExceptionTranslator<int>([](int in){ return doctest::toString(in); });
84 …e string type **doctest** works with. ```std::string``` is not an option because doctest would hav…
[all …]
|
| /dports/devel/doctest/doctest-2.4.7/doc/markdown/ |
| H A D | stringification.md | 6 For stringifying enums checkout [this issue](https://github.com/onqtam/doctest/issues/121).
10 …the chances are you may already provide this for your own purposes. If you're not familiar with th…
32 ## ```doctest::toString``` overload
40 doctest::String toString(const udt& value) {
48 ## ```doctest::StringMaker<T>``` specialisation
53 namespace doctest {
68 return doctest::String(ex.message());
77 // adding a lambda - the signature required is `doctest::String(exception_type)`
78 doctest::registerExceptionTranslator<int>([](int in){ return doctest::toString(in); });
88 …e string type **doctest** works with. ```std::string``` is not an option because doctest would hav…
[all …]
|
| /dports/lang/python-legacy/Python-2.7.18/Doc/tutorial/ |
| H A D | stdlib.rst | 66 instance the following output results from running ``python demo.py one two
98 The :mod:`re` module provides regular expression tools for advanced string
102 >>> import re
103 >>> re.findall(r'\bf[a-z]*', 'which foot or hand fell fastest')
105 >>> re.sub(r'(\b[a-z]+) \1', r'\1', 'cat in the the hat')
254 cutting-and-pasting a typical call along with its results into the docstring.
256 allows the doctest module to make sure the code remains true to the
267 import doctest
268 doctest.testmod() # automatically validate the embedded tests
270 The :mod:`unittest` module is not as effortless as the :mod:`doctest` module,
[all …]
|
| /dports/lang/python27/Python-2.7.18/Doc/tutorial/ |
| H A D | stdlib.rst | 66 instance the following output results from running ``python demo.py one two
98 The :mod:`re` module provides regular expression tools for advanced string
102 >>> import re
103 >>> re.findall(r'\bf[a-z]*', 'which foot or hand fell fastest')
105 >>> re.sub(r'(\b[a-z]+) \1', r'\1', 'cat in the the hat')
254 cutting-and-pasting a typical call along with its results into the docstring.
256 allows the doctest module to make sure the code remains true to the
267 import doctest
268 doctest.testmod() # automatically validate the embedded tests
270 The :mod:`unittest` module is not as effortless as the :mod:`doctest` module,
[all …]
|
| /dports/lang/rust/rustc-1.58.1-src/compiler/rustc_error_codes/src/error_codes/ |
| H A D | E0210.md | 37 named `ForeignTrait2` that takes two type parameters. Then this `impl` results
40 ```ignore (cannot-doctest-multicrate-project)
46 the `impl` header, both as parameters for `ForeignTrait2`. The first appearance
51 ```ignore (cannot-doctest-multicrate-project)
81 [RFC 2451]: https://rust-lang.github.io/rfcs/2451-re-rebalancing-coherence.html
|
| /dports/databases/py-gdbm/Python-3.8.12/Doc/tutorial/ |
| H A D | stdlib.rst | 68 instance the following output results from running ``python demo.py one two
113 The :mod:`re` module provides regular expression tools for advanced string
117 >>> import re
118 >>> re.findall(r'\bf[a-z]*', 'which foot or hand fell fastest')
120 >>> re.sub(r'(\b[a-z]+) \1', r'\1', 'cat in the the hat')
285 cutting-and-pasting a typical call along with its results into the docstring.
287 allows the doctest module to make sure the code remains true to the
298 import doctest
299 doctest.testmod() # automatically validate the embedded tests
301 The :mod:`unittest` module is not as effortless as the :mod:`doctest` module,
[all …]
|
| /dports/databases/py-sqlite3/Python-3.8.12/Doc/tutorial/ |
| H A D | stdlib.rst | 68 instance the following output results from running ``python demo.py one two
113 The :mod:`re` module provides regular expression tools for advanced string
117 >>> import re
118 >>> re.findall(r'\bf[a-z]*', 'which foot or hand fell fastest')
120 >>> re.sub(r'(\b[a-z]+) \1', r'\1', 'cat in the the hat')
285 cutting-and-pasting a typical call along with its results into the docstring.
287 allows the doctest module to make sure the code remains true to the
298 import doctest
299 doctest.testmod() # automatically validate the embedded tests
301 The :mod:`unittest` module is not as effortless as the :mod:`doctest` module,
[all …]
|
| /dports/lang/python38/Python-3.8.12/Doc/tutorial/ |
| H A D | stdlib.rst | 68 instance the following output results from running ``python demo.py one two
113 The :mod:`re` module provides regular expression tools for advanced string
117 >>> import re
118 >>> re.findall(r'\bf[a-z]*', 'which foot or hand fell fastest')
120 >>> re.sub(r'(\b[a-z]+) \1', r'\1', 'cat in the the hat')
285 cutting-and-pasting a typical call along with its results into the docstring.
287 allows the doctest module to make sure the code remains true to the
298 import doctest
299 doctest.testmod() # automatically validate the embedded tests
301 The :mod:`unittest` module is not as effortless as the :mod:`doctest` module,
[all …]
|
| /dports/lang/python37/Python-3.7.12/Doc/tutorial/ |
| H A D | stdlib.rst | 68 instance the following output results from running ``python demo.py one two
113 The :mod:`re` module provides regular expression tools for advanced string
117 >>> import re
118 >>> re.findall(r'\bf[a-z]*', 'which foot or hand fell fastest')
120 >>> re.sub(r'(\b[a-z]+) \1', r'\1', 'cat in the the hat')
285 cutting-and-pasting a typical call along with its results into the docstring.
287 allows the doctest module to make sure the code remains true to the
298 import doctest
299 doctest.testmod() # automatically validate the embedded tests
301 The :mod:`unittest` module is not as effortless as the :mod:`doctest` module,
[all …]
|
| /dports/lang/python310/Python-3.10.1/Doc/tutorial/ |
| H A D | stdlib.rst | 68 instance the following output results from running ``python demo.py one two
113 The :mod:`re` module provides regular expression tools for advanced string
117 >>> import re
118 >>> re.findall(r'\bf[a-z]*', 'which foot or hand fell fastest')
120 >>> re.sub(r'(\b[a-z]+) \1', r'\1', 'cat in the the hat')
285 cutting-and-pasting a typical call along with its results into the docstring.
287 allows the doctest module to make sure the code remains true to the
298 import doctest
299 doctest.testmod() # automatically validate the embedded tests
301 The :mod:`unittest` module is not as effortless as the :mod:`doctest` module,
[all …]
|
| /dports/lang/python-tools/Python-3.8.12/Doc/tutorial/ |
| H A D | stdlib.rst | 68 instance the following output results from running ``python demo.py one two
113 The :mod:`re` module provides regular expression tools for advanced string
117 >>> import re
118 >>> re.findall(r'\bf[a-z]*', 'which foot or hand fell fastest')
120 >>> re.sub(r'(\b[a-z]+) \1', r'\1', 'cat in the the hat')
285 cutting-and-pasting a typical call along with its results into the docstring.
287 allows the doctest module to make sure the code remains true to the
298 import doctest
299 doctest.testmod() # automatically validate the embedded tests
301 The :mod:`unittest` module is not as effortless as the :mod:`doctest` module,
[all …]
|
| /dports/lang/python39/Python-3.9.9/Doc/tutorial/ |
| H A D | stdlib.rst | 68 instance the following output results from running ``python demo.py one two
113 The :mod:`re` module provides regular expression tools for advanced string
117 >>> import re
118 >>> re.findall(r'\bf[a-z]*', 'which foot or hand fell fastest')
120 >>> re.sub(r'(\b[a-z]+) \1', r'\1', 'cat in the the hat')
285 cutting-and-pasting a typical call along with its results into the docstring.
287 allows the doctest module to make sure the code remains true to the
298 import doctest
299 doctest.testmod() # automatically validate the embedded tests
301 The :mod:`unittest` module is not as effortless as the :mod:`doctest` module,
[all …]
|
| /dports/x11-toolkits/py-tkinter/Python-3.8.12/Doc/tutorial/ |
| H A D | stdlib.rst | 68 instance the following output results from running ``python demo.py one two
113 The :mod:`re` module provides regular expression tools for advanced string
117 >>> import re
118 >>> re.findall(r'\bf[a-z]*', 'which foot or hand fell fastest')
120 >>> re.sub(r'(\b[a-z]+) \1', r'\1', 'cat in the the hat')
285 cutting-and-pasting a typical call along with its results into the docstring.
287 allows the doctest module to make sure the code remains true to the
298 import doctest
299 doctest.testmod() # automatically validate the embedded tests
301 The :mod:`unittest` module is not as effortless as the :mod:`doctest` module,
[all …]
|
| /dports/lang/python311/Python-3.11.0a3/Doc/tutorial/ |
| H A D | stdlib.rst | 68 instance the following output results from running ``python demo.py one two
113 The :mod:`re` module provides regular expression tools for advanced string
117 >>> import re
118 >>> re.findall(r'\bf[a-z]*', 'which foot or hand fell fastest')
120 >>> re.sub(r'(\b[a-z]+) \1', r'\1', 'cat in the the hat')
285 cutting-and-pasting a typical call along with its results into the docstring.
287 allows the doctest module to make sure the code remains true to the
298 import doctest
299 doctest.testmod() # automatically validate the embedded tests
301 The :mod:`unittest` module is not as effortless as the :mod:`doctest` module,
[all …]
|
| /dports/biology/pyfasta/pyfasta-0.5.2/ |
| H A D | PKG-INFO | 26 (for fseek/mmap) locations of each header in the fasta file for internal use.
94 >>> f['chr1'][:10] # doctest: +NORMALIZE_WHITESPACE
102 >>> a[10:14] # doctest: +NORMALIZE_WHITESPACE
173 $ pyfasta **split** --header "%(seqid)s.fasta" original.fasta
189 **extract** sequence from the file. use the header flag to make
192 $ pyfasta **extract** --header --fasta test/data/three_chrs.fasta seqa seqb seqc
200 $ pyfasta extract --header --fasta input.with.keys.fasta --space --file seqids.txt
267 * dont re-flatten the file every time!
268 * allow spaces before and after the header in the orginal fasta.
275 * get rid of memmap (results in faster parsing).
[all …]
|
| /dports/biology/pyfasta/pyfasta-0.5.2/pyfasta.egg-info/ |
| H A D | PKG-INFO | 26 (for fseek/mmap) locations of each header in the fasta file for internal use.
94 >>> f['chr1'][:10] # doctest: +NORMALIZE_WHITESPACE
102 >>> a[10:14] # doctest: +NORMALIZE_WHITESPACE
173 $ pyfasta **split** --header "%(seqid)s.fasta" original.fasta
189 **extract** sequence from the file. use the header flag to make
192 $ pyfasta **extract** --header --fasta test/data/three_chrs.fasta seqa seqb seqc
200 $ pyfasta extract --header --fasta input.with.keys.fasta --space --file seqids.txt
267 * dont re-flatten the file every time!
268 * allow spaces before and after the header in the orginal fasta.
275 * get rid of memmap (results in faster parsing).
[all …]
|
| /dports/mail/py-pyspf/pyspf-2.0.14/ |
| H A D | spf.py | 66 import re
105 if resp.header['tc'] == True:
113 if resp.header['rcode'] != 0 and resp.header['rcode'] != 3:
114 … raise IOError('Error: ' + resp.header['status'] + ' RCODE: ' + str(resp.header['rcode']))
177 RE_SPF = re.compile(br'^v=spf1$|^v=spf1 ',re.IGNORECASE)
180 RE_MODIFIER = re.compile(r'^([a-z][a-z0-9_\-\.]*)=', re.IGNORECASE)
216 }, re.IGNORECASE)
1471 for resobj in arobj.results:
1656 results = [authres.SPFAuthenticationResult(result = tag, \
1952 import doctest, spf
[all …]
|
| /dports/lang/python-legacy/Python-2.7.18/Doc/library/ |
| H A D | doctest.rst | 362 with confusing results.
485 ordinary output rarely begins with a traceback header line, so this doesn't
498 * The interactive shell omits the traceback header line for some
499 :exc:`SyntaxError`\ s. But doctest uses the traceback header line to
502 manually add the traceback header line to your test example.
1142 you're writing a :mod:`unittest` framework, :mod:`unittest` ultimately controls
1216 |module| --DocTestFinder-> | DocTest | --DocTestRunner-> results
1545 results using the writer function *out*.
1557 output checker, and the results are formatted by the
1889 and produces different results, blurring the distinction between testing and
[all …]
|
| /dports/lang/python27/Python-2.7.18/Doc/library/ |
| H A D | doctest.rst | 362 with confusing results.
485 ordinary output rarely begins with a traceback header line, so this doesn't
498 * The interactive shell omits the traceback header line for some
499 :exc:`SyntaxError`\ s. But doctest uses the traceback header line to
502 manually add the traceback header line to your test example.
1142 you're writing a :mod:`unittest` framework, :mod:`unittest` ultimately controls
1216 |module| --DocTestFinder-> | DocTest | --DocTestRunner-> results
1545 results using the writer function *out*.
1557 output checker, and the results are formatted by the
1889 and produces different results, blurring the distinction between testing and
[all …]
|
| /dports/databases/py-sqlite3/Python-3.8.12/Doc/library/ |
| H A D | doctest.rst | 419 The expected output for an exception must start with a traceback header, which
467 ordinary output rarely begins with a traceback header line, so this doesn't
480 * The interactive shell omits the traceback header line for some
481 :exc:`SyntaxError`\ s. But doctest uses the traceback header line to
484 manually add the traceback header line to your test example.
1102 you're writing a :mod:`unittest` framework, :mod:`unittest` ultimately controls
1174 |module| --DocTestFinder-> | DocTest | --DocTestRunner-> results
1497 results using the writer function *out*.
1509 output checker, and the results are formatted by the
1823 and produces different results, blurring the distinction between testing and
[all …]
|
| /dports/databases/py-gdbm/Python-3.8.12/Doc/library/ |
| H A D | doctest.rst | 419 The expected output for an exception must start with a traceback header, which
467 ordinary output rarely begins with a traceback header line, so this doesn't
480 * The interactive shell omits the traceback header line for some
481 :exc:`SyntaxError`\ s. But doctest uses the traceback header line to
484 manually add the traceback header line to your test example.
1102 you're writing a :mod:`unittest` framework, :mod:`unittest` ultimately controls
1174 |module| --DocTestFinder-> | DocTest | --DocTestRunner-> results
1497 results using the writer function *out*.
1509 output checker, and the results are formatted by the
1823 and produces different results, blurring the distinction between testing and
[all …]
|
| /dports/lang/python37/Python-3.7.12/Doc/library/ |
| H A D | doctest.rst | 421 The expected output for an exception must start with a traceback header, which
469 ordinary output rarely begins with a traceback header line, so this doesn't
482 * The interactive shell omits the traceback header line for some
483 :exc:`SyntaxError`\ s. But doctest uses the traceback header line to
486 manually add the traceback header line to your test example.
1104 you're writing a :mod:`unittest` framework, :mod:`unittest` ultimately controls
1176 |module| --DocTestFinder-> | DocTest | --DocTestRunner-> results
1499 results using the writer function *out*.
1511 output checker, and the results are formatted by the
1825 and produces different results, blurring the distinction between testing and
[all …]
|
| /dports/lang/python38/Python-3.8.12/Doc/library/ |
| H A D | doctest.rst | 419 The expected output for an exception must start with a traceback header, which
467 ordinary output rarely begins with a traceback header line, so this doesn't
480 * The interactive shell omits the traceback header line for some
481 :exc:`SyntaxError`\ s. But doctest uses the traceback header line to
484 manually add the traceback header line to your test example.
1102 you're writing a :mod:`unittest` framework, :mod:`unittest` ultimately controls
1174 |module| --DocTestFinder-> | DocTest | --DocTestRunner-> results
1497 results using the writer function *out*.
1509 output checker, and the results are formatted by the
1823 and produces different results, blurring the distinction between testing and
[all …]
|
| /dports/lang/python-tools/Python-3.8.12/Doc/library/ |
| H A D | doctest.rst | 419 The expected output for an exception must start with a traceback header, which
467 ordinary output rarely begins with a traceback header line, so this doesn't
480 * The interactive shell omits the traceback header line for some
481 :exc:`SyntaxError`\ s. But doctest uses the traceback header line to
484 manually add the traceback header line to your test example.
1102 you're writing a :mod:`unittest` framework, :mod:`unittest` ultimately controls
1174 |module| --DocTestFinder-> | DocTest | --DocTestRunner-> results
1497 results using the writer function *out*.
1509 output checker, and the results are formatted by the
1823 and produces different results, blurring the distinction between testing and
[all …]
|
| /dports/lang/python39/Python-3.9.9/Doc/library/ |
| H A D | doctest.rst | 419 The expected output for an exception must start with a traceback header, which
467 ordinary output rarely begins with a traceback header line, so this doesn't
480 * The interactive shell omits the traceback header line for some
481 :exc:`SyntaxError`\ s. But doctest uses the traceback header line to
484 manually add the traceback header line to your test example.
1102 you're writing a :mod:`unittest` framework, :mod:`unittest` ultimately controls
1174 |module| --DocTestFinder-> | DocTest | --DocTestRunner-> results
1497 results using the writer function *out*.
1509 output checker, and the results are formatted by the
1823 and produces different results, blurring the distinction between testing and
[all …]
|