- https://docs.python.org/2/library/
- https://docs.python.org/2/library/re.html
- https://docs.python.org/2/library/glob.html
- https://docs.python.org/2/library/fnmatch.html
- https://docs.python.org/3/library/
- https://docs.python.org/3/library/re.html
- https://docs.python.org/3/library/glob.html
- https://docs.python.org/3/library/fnmatch.html
Blog
-
Python and regular expressions and “globbing”
-
O’Reilly Media book: Python & XML
- published in 2001
- http://shop.oreilly.com/product/9780596001285.do
- https://library.oreilly.com/book/9780596001285/python-amp-xml/toc — behind a paywall
- https://library.oreilly.com/book/9780596001285/python-amp-xml/83.xhtml — Chapter 5. Querying XML with XPath
Being published in 2001 the examples in the book (I mostly focused on XPath resp. chapter 5; so example 5-1 already made me “wake up”) make use of software that was available then but no longer nowadays in 2016, e.g. 4DOM — that did not astonish me a lot.
I am discussing “Python and XPath” in a separate article on this blog [link].
-
O’Reilly Media book: RTF Pocket Guide
- https://en.wikipedia.org/wiki/Rich_Text_Format
- http://shop.oreilly.com/product/9780596004750.do
- http://search.cpan.org/search?dist=RTF-Writer
- http://search.cpan.org/dist/RTF-Writer/lib/RTF/Cookbook.pod
- https://metacpan.org/pod/distribution/XML-SAX-RTF/RTF.pm – “… generates XML that closely matches the structure of RTF …” — tells me “not well-formed (invalid token) …” with my very 1st sample — gave up on it
-
the Jenkins automation server and disabling security when locked out
- http://www.eclipse.org/hudson/the-hudson-book/book-hudson.pdf — where I found the hint originally
recipe:
- open your $JENKINS_HOME/config.xml
- find <useSecurity>…</useSecurity> and set it to false for the time being
- then change to a new security realm and/or authorisation
-
the Jenkins automation server and shell build steps started using “-xe”
Q: Why “automation server” and not “continuous integration …“?
A: Because Jenkins’ business is no longer just “continuous integration” but the very wide field of automation in general. Whatever you started before through a crontab entry, is so much more comfortable to start through a Jenkins job. Log files are being preserved (and purged automatically, if you want so), artefact as well, …Jenkins starts all shell build steps using “-xe”, that’s like “set -x” and “set -e” within a shell script. “-xe” gets passed on to shell scripts called from within a shell build step — but you usually don’t want to show its internals and get the commands within your shell script displayed command by command — and there is a way to revert this effect: insert “/bin/bash +xe” before the call to the shell script!