summaryrefslogtreecommitdiffstats
path: root/bin/update-release-info.py
Commit message (Collapse)AuthorAgeFilesLines
* syntax fixups suggested by PyCharmMats Wichmann2019-12-231-20/+6
| | | | | | | | | | | | | | Drop unneeded parens. Drop trailing semicolons. Triple double-quote docstrings. Regexes drop unneeded escapes. Spaces around parens, braces: remove/add. Some one-tuples get their missing closing comma. A couple of sets use set init syntax {foo} instead of set([iter]) now. And a fiddle in Node to reduce lookup time on md5 signature functions (came about because of a line-too-long issue, initially) Signed-off-by: Mats Wichmann <mats@linux.com>
* Clean up some file opens, regex stringsMats Wichmann2019-03-071-12/+17
| | | | | | | | | | | | | | | | | | Most recent Python (3.8 alpha) spews warnings aplenty about two subjects: unclosed files and strings which look like they have embedded escapes that Python does not recognize. The latter are usually regexes, and it provides a reminder that regular expressions should normally be specified as raw strings, so Python does not attempt to interpret them. Irritating is that even docstrings are flagged, it's not obvious what the right answer is for a docstring which contains, say, a Windows-style path with backslashes. This converts a bunch of opens that are not closed into context manager usage and regex patterns into raw strings. This eliminate about 4000 warnings spewed by Py3.8 (9200 remain). Signed-off-by: Mats Wichmann <mats@linux.com>
* move test files from QMTest to testing/framework. QMtest hasn't been used in ↵William Deegan2018-04-301-5/+5
| | | | quite some time
* Remove 'U' flag to open() which is deprecated.Craig Rodrigues2017-03-111-1/+1
|
* Post merge commit for safety. Building Fortran code works, but tests fail.Russel Winder2015-12-241-0/+1
|\
| * change tree back to development mode and bring back changes from release branchWilliam Deegan2015-09-211-0/+1
| |
* | Merged with [default]Stefan Zimmermann2014-03-311-2/+2
|\ \ | |/
| * Put back into develop mode post-2.3.1 release;Gary Oberbrunner2014-03-041-2/+2
| | | | | | | | also improve update-release-info.py to use shorter copyright year strings.
* | Merged with [default]Stefan Zimmermann2014-03-311-8/+9
|\ \ | |/
| * update-release-info: fixed date updating for doc/user/main.xml.Gary Oberbrunner2013-12-271-8/+9
| | | | | | | | | | Also added note that doc/user/main.in is no longer needed/used and prevent that from stopping the doc gen process.
* | Made former 2to3 changes Python 2.7 compatible (or removed unneeded changes).Stefan Zimmermann2014-03-311-1/+2
| |
* | Result of raw 2to3 run (2to3-2.7); checkpoint for python3 conversion.Gary Oberbrunner2013-09-221-15/+15
|/
* Merged pull request #44 (make README a ReStructuredText file)Gary Oberbrunner2012-10-131-4/+3
| | | | I added a few test fixes and tweaks to Russels version.
* New upload-release-files script, and fixed up update-release-info.Gary Oberbrunner2012-08-051-2/+5
| | | | | update-release-info: allow regular 3-digit releases (not .final.0) upload-release-files: new, does a lot of the heavy lifting for a release.
* Move update-release-info.py from src/ to tests/update_release-info/Greg Noel2010-06-111-0/+15
|
* Remove the rest of the logic for the noqmtest keywordGreg Noel2010-06-081-12/+12
|
* Fixed a bug in the regression test to use the right filenames for eachGreg Noel2010-06-071-1/+34
| | | | | | | | | | | platform; it was causing the test to fail on Windows. Added some documentation to bin/update-release-info.py. In my last log message, I forgot to mention that QMTest/TestRuntest.py was tweaked to make it less specialized for testing runtest.py. It can now be used to test other programs; in this case, bin/update-release-info.py. The defaults are unchanged so that it will normally test runtest.py.
* Initial drop of bin/update-release-info.py.Greg Noel2010-06-071-0/+306
This program automates the process of inserting the release configuration information that is currently done by hand. The configuration data now all lives in a file, 'ReleaseConfig'. Change the configuration file, run the program, and, hey presto, the files are updated. More work needs to be done; the documentation doesn't quite match with the program and the regression tests only cover the release flows, but it's important to get this stuff out before the next release is published so people can start using it.