Rubber 1.4
Milestone information
- Project:
- Rubber
- Series:
- trunk
- Version:
- 1.4
- Released:
- Registrant:
- Sebastian Kapfer
- Release registered:
- Active:
- No. Drivers cannot target bugs and blueprints to this milestone.
Activities
- Assigned to you:
- No blueprints or bugs assigned to you.
- Assignees:
- No users assigned to blueprints and bugs.
- Blueprints:
- No blueprints are targeted to this milestone.
- Bugs:
- No bugs are targeted to this milestone.
Download files for this release
Release notes
Version 1.4 (2015-12-11)
This version of Rubber officially requires Python 2.6 and up.
Note that the code has not been tested with Python 3, so if you
run it under Python 3, you're on your own. Bug reports are welcome!
Starting with 1.4, the primary repository at Launchpad is a
Git tree.
Features:
- New distutils-based build & install scripts by Nicolas.
- Report BibTeX / Biber errors more reliably.
- We have support for embedding R code via knitr.
http://
Closes: https:/
Note that since R can run arbitrary external code, --unsafe
must be given at the command line:
rubber -d --unsafe paper.Rtex
creates beautifully typeset PDF from your R script.
- Support for PythonTeX package. Also requires --unsafe if
you want Rubber to invoke pythontex.
- Rubber will no longer attempt to use jpeg2ps on its own, which has
been superseded by sam2p. (You can add it back by providing your
own rules.ini.)
Bugfixes:
- Refuse to read logfiles which exceed 1 MB.
This avoids out-of-memory situations. The limit may be raised with
% rubber: set logfile_limit 1000000
https:/
- The command-line parsing of rubber and rubber-info has been merged.
Thus, the --inplace and --into options are not only accepted by
Rubber (as they were previously), they also take effect.
Closes: https:/
- Rubber complains properly now for nonexisting directives, and
doesn't just print a stacktrace.
Closes: https:/
- More refactoring, reducing the number of code paths to test and
maintain.
Changelog
This release does not have a changelog.
0 blueprints and 0 bugs targeted
There are no feature specifications or bug tasks targeted to this milestone. The project's maintainer, driver, or bug supervisor can target specifications and bug tasks to this milestone to track the things that are expected to be completed for the release.
