-
Notifications
You must be signed in to change notification settings - Fork 64
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ansible 1.6.10 expects python in /usr/bin instead of /opt/local/bin #268
Comments
I have never used Ansible, is there a concept of "this OS has X at Y" at all? Or does it simply assume that all the OS of the world will have /usr/bin/python? |
There is (or well was) a discussion on ansible/ansible#6345 also some documentation on http://docs.ansible.com/faq.html#how-do-i-handle-python-pathing-not-having-a-python-2-x-in-usr-bin-python-on-a-remote-machine |
Having thought about this for a while and having started using ansible recently on SmartOS, I'm going to close this as WontFix. Whilst changing it to There is no concept of per-OS defaults at present in the ansible code itself, so this would have to be a global change, forcing you to instead set The ansible inventory format makes this a single line change for all SmartOS hosts if you correctly group them, so it's pretty simple to handle this, i.e.: [smartos_hosts]
192.168.3.216
192.168.3.217
192.168.3.218
192.168.3.219
[smartos_hosts:vars]
ansible_python_interpreter=/opt/local/bin/python Thanks. |
From David Gutteridge in PR pkg/50541 ============ gedit 3.16.4 ============ Fixes ===== - Fix crash in the open document selector - Various bug fixes New and updated translations ============================ - nl (Hannie Dumoleyn) ============ gedit 3.16.3 ============ Fixes ====================== - Various bug fixes New and updated translations ============================ - cs (Marek Černocký) - de (Bernd Homuth) - es (Daniel Mustieles) - gl (Fran Dieguez) - hu (Balázs Úr) - id (Andika Triwidada) - is (Sveinn í Felli) - it (Milo Casagrande) - lt (Aurimas Černius) - oc (Cédric Valmary (totenoc.eu)) - pl (Piotr Drąg) - pt_BR (Felipe Braga) - pt (Pedro Albuquerque) - ru (Paulo Fino) - sk (Du\232an Kazik) - sl (Matej Urbančič) - sv (Anders Jonsson)
Release 0.8.4 - January 16 2016 ------------------------------- * Fix for :func:`write_url` exception when the URL contains two ``#`` location/anchors. Note, URLs like this aren't strictly valid and cannot be entered manually in Excel. Issue `#330 <https://github.com/jmcnamara/XlsxWriter/issues/330>`_. Release 0.8.3 - January 14 2016 ------------------------------- * Added options to configure chart axis tick placement. See :func:`set_x_axis()`. Release 0.8.2 - January 13 2016 ------------------------------- * Added transparency option to solid fill colors in chart areas (:ref:`chart_formatting_fill`). Feature request `#298 <https://github.com/jmcnamara/XlsxWriter/issues/298>`_. Release 0.8.1 - January 12 2016 ------------------------------- * Added option to set chart tick interval. Feature request `#251 <https://github.com/jmcnamara/XlsxWriter/issues/251>`_. Release 0.8.0 - January 10 2016 ------------------------------- * Added additional documentation on :ref:`working_with_formulas`. Release 0.7.9 - January 9 2016 ------------------------------ * Added chart pattern fills, see :ref:`chart_formatting_pattern` and :ref:`ex_chart_pattern`. Feature request `#268 <https://github.com/jmcnamara/XlsxWriter/issues/268>`_.
Upstream changes: 0.9995 2016-07-27T09:23:55Z - Taught the `add` command not to ignore the `--change` option. - The `add` command now emits a usage statement when no change name is passed to it. - The `add` command now helpfully suggests using the --change option when attempting to add a change with the same name as a target. Thanks to Ivan Nunes for the report! - The `tag` command now helpfully suggests using the --tag option when attempting to add a tag with the same name as a target. - Added `--global` as an alias for `--user` to the `config` command. This alias benefits the muscle memory of Git users. - Added a note for Git users to the `sqitch-revert` documentation, to head off potential confusion with `git revert`. Thanks to Eric Br矇chemier for the "time travel" analogy and wording. - Fixed an "uninitialized value" error when creating a registry database on Windows. Thanks to Steven C. Buttgereit for the report (Issue #289). - Fixed editor selection to prioritize the `core.editor` configuration variable over the `$EDITOR` environment variable. The `$SQITCH_EDITOR` environment variable still trumps all. Thanks to Jim Nasby for the pull request (#296). - Added detection of the `$VISUAL` environment variable to Editor selection, prioritzed after the `core.editor` configuration variable and before the `$EDITOR` environment variable. Thanks to Jim Nasby for the pull request (#296). - Updated the DateTime code to set the locale via `set_locale()` instead of `set()`, as the latter may actually change the local time unintentionally, and has been deprecated since DateTime v1.04. Thanks to Dave Rolsky for the pull request (#304). 0.9994 2016-01-08T19:46:43Z - Reduced minimum required MySQL engine from 5.1.0 to 5.0.0. Thanks to @dgc-wh for testing it (Issue #251). - Fixed floating-point rounding issue with SQLite registry versions on Perls with 16-byte doubles. Thanks to H. Merijn Brand for the report and testing. - Fixed an error when adding an engine with the `engine` command. Thanks to Victor Mours for the report and fix! - Updated the Oracle engine to support Oracle Wallet connection strings, where no username or host is in the connection URI. Thanks to Timothy Procter for the patch! - Improved the installer's selection of the prefix in which to install `etc` files to better match the `--installdirs` option, which defaults to the "site" directories. Thanks to @carragom for the pull request (#265). - Added missing dash to `-engine` in sample calls to `sqitch init` in the tutorials. Thanks to Andrew Dunstan for the spot (Issue #268). - Fixed broken Vertica documentation links. - Attempting to revert a database with no associated registry no longer reports the registry as version 0, but correctly reports that no registry can be found. Thanks to Arnaldo Piccinelli for the spot (Issue #271). - Fixed the search for change IDs in engines to match the search for changes. Specifically, change ID seaerch now properly handles the offset characters `~` and `^`. This bug mainly affected the `verify` command, but it's good to address the inconsistency, done mainly by adding the `find_change_id` and `change_id_offset_from_id` methods to complement the `find_change` and `change_offset_from_id` methods. Thanks to Andrew Dunstan for the spot (Issue #272). - Fixed the `flips` table example in the MySQL tutorial. It was inappropriately copied from the PostgreSQL tutorial at some point. Thanks to Jeff Carpenter for the spot (Issue #254)! 0.9993 2015-08-17T17:55:26Z [Bug Fixes] - Eliminated test failures due to warnings from DateTime::Locale when `LC_TIME` is set to C.UTF-8. Thanks to Shantanu Bhadoria for the report and Dave Rolsky for the workaround. - Fixed an error checking the registry version when the local uses a comma for decimal values. Thanks to Steffen M羹ller for the report (Issue #234). - Worked around an error setting the MySQL storage engine using versions of DBI prior to 1.631. Thanks to melon-babak for the report! - Fixed an error from the Oracle engine when deploying more than 1000 changes. Thanks to Timothy Procter and Minh Hoang for the report and testing the fix. - Fixed a bunch of typos in error messages, comments, and documentation. Thanks to Dmitriy for the pull request! - Fixed test failures due to new warnings from File::Path on Perl 5.23.1. - On Firebird, Looking up a change and tag in the database (via the `--onto` option to `rebase` or the `--to` option to `revert`, among others) would sometimes return the incorrect change if the change has been reworked two or more times. Was fixed for the other engines in v0.9991. - Fixed the `--all` option used to apply a command to all known targets so that it loads only targets specified by the local configuration. Otherwise, user and system configuration can get in the way when they specify engines and targets not used by the current project. [Improvements] - Added support for the `--set` option when deploying to MySQL. Thanks to Chris Bandy for figuring out how to do it! - Added support for a "reworked directory". By default, reworked change scripts live in the deploy, revert, and verify directories along with all the other change scripts. But if that starts to get too messy, or you simply don't want to see them, add a `reworked_dir` setting to the core, engine, or target config and reworked scripts will be stored there, instead. Also supported are `reworked_deploy_dir`, `reworked_revert_dir`, and `reworked_verify_dir`. - Added the `--dir` option to the `init`, `engine`, and `target` commands. - Copied the core configuration options (`--engine`, `--target`, `--plan-file`, `--registry`, etc.) to the `init`, `engine`, and `target` commands. This means that they can be specified after the command, which is a bit more natural. It also means that the `--registry` and `--client` options of the `target` are no longer deprecated. - The `init` command on longer writes out commented values for the `deploy_dir`, `revert_dir`, or `verify_dir` settings. I think these settings are not commonly used, and it would start to get crowded if we also added their "reworked" variants, which will be used still less. - Added the `alter` action to the `engine` and `target` commands to set engine and target properties. - Added support for setting reworked directories to the `engine` and `target` commands. - Reformatted the output of the `engine` and `target` command `show` actions to include reworked directories, and to bit a bit less flat. - Attempting to add or alter an engine with a target URI that connects to a different engine now triggers an error. For example, you can't set the target for engine `pg` to `db:sqlite:`. - The `add` and `alter` actions of the `engine` and `target` commands now create script directories if they don't already exist. - The `add` action of the `engine` and `target` commands now creates a plan file if one does not exist in the specified location for the engine or target. - Added the `deploy_dir`, `revert_dir`, and `verify_dir` methods to App::Sqitch::Plan::Change. Each points to the proper directory for the target depending on whether or not the change has been reworked. - In the MySQL engine, the following URI query params will be converted to options passed to the command-line client, if they're present: * mysql_compression=1 => --compress * mysql_ssl=1 => --ssl * mysql_connect_timeout => --connect_timeout * mysql_init_command => --init-command * mysql_socket => --socket * mysql_ssl_client_key => --ssl-key * mysql_ssl_client_cert => --ssl-cert * mysql_ssl_ca_file => --ssl-ca * mysql_ssl_ca_path => --ssl-capath * mysql_ssl_cipher => --ssl-cipher [Documentation] - Added the "Overworked" section to sqitch-configuration guide with an example of how to move reworked change scripts into a `reworked_dir`. [Deprecations] - Deprecated the `set-*` actions in the `engine` and `target` commands in favor of the new `alter` action. - The core `--deployed-dir`, `--revert-dir`, and `--verify-dir` options are deprecated in favor of the `--dir` option on the `init`, `engine`, and `target` command. 0.9992 2015-05-20T23:51:41Z - On PostgreSQL, Sqitch now sets the `client_encoding` parameter to `UTF8` for its own connection to the database. This ensures that data sent to and from the databse should always be properly encoded and decoded. Users should still set the proper encodings for change scripts as appropriate. - Fixed test failures due to path differences on Windows. - DateTime::TimeZone is now explicitly required in an attempt to head off "Cannot determine local time zone" errors. - Corrected some typos and thinkos in `sqitchtutorial-oracle`, thanks to George Hartzell. - Improved the script to upgrade an Oracle registry to v1.0 to support versions prior to Oracle 12, thanks to Timothy Procter. - Added missing closing parenthesis to the "Nothing to deploy" message. Thanks to George Hartzell for the pull request (Issue #226). - Replaced the unique constraint on the `script_hash` column in the `changes` registry table with a unique constraint on `project` and `script_hash`. This is to allow a deploy script to be used in more than one project in a single database. This change increments the registry version to v1.1. Thanks to Timothy Procter for the report. - Updated the registry check constraints to have consistent names on the engines that support them. This will make it easier to modify the constraints in the future. - Fixed precision issues with the registry version on MySQL and Firebird. - Added comment to sqitch-passwords guide that MySQL::Config is required to read passwords from the MySQL configuration files. Thanks to Sterling Hanenkamp for the patch! 0.9991 2015-04-03T23:14:39Z [Improvements] - Reduced minimum required MySQL engine from 5.6.4 to 5.1.0. Versions prior to 5.6.4 lose the following features: * Versions earlier than 5.6.4 is fractional second precision on registry `DATETIME` columns. Since the ordering of those timestamps is so important to the functioning of Sqitch, it will sleep in 100 ms increments between logging changes to the registry until the time has ticked over to the next second. Naturally, reverts and deploys will be a little slower on versions of MySQL before 5.6.4, but accurate. * Versions earlier than 5.5.0 lose the `checkit()` functions, which would otherwise be used to emulate CHECK constraints in the registry, as well as in user-created verify scripts, as recommended in the MySQL tutorial, `sqitchtutorial-mysql`. - Added a script to update the `DATETIME` columns in a MySQL Sqitch registry that was upgraded to MySQL 5.6.4 or higher. It will be installed as `tools/upgrade-registry-to-mysql-5.6.4.sql` in the directory returned by `sqitch --etc`. - Added a script to add the `checkit()` function and registry triggers to emulate CHECK constraints to a MySQL Sqitch registry that was upgraded to MySQL 5.5.0 or higher. It will be installed as `tools/upgrade-registry-to-mysql-5.5.0.sql` in the directory returned by `sqitch --etc`. - The `init` command now throws an error when the plan file already exists and is invalid or defined for a different project. Thanks to Gabriel Potk獺ny for the suggestion (Issue #214). - All commands that take target arguments can now specify them as engine names or plan file paths as well as target names and URIs. - Added the `--all` option and the `$command.all` configuration variable to the `add`, `rework`, `tag`, and `bundle` commands. This option tells the commands to do their thing for all plans known from the configuration, not just the default plan. - Pass engine, target, or plan file names to the `add`, `rework`, `tag`, and `bundle` commands` commands to specify specify one or more targets, engines, and plans to act on. - Added the `--change` option to the `add`, `rework`, and `tag` commands to distinguish the change to be added, reworked, or tagged from plan-specifying arguments, if necessary. - Added the `--tag` option to the `tag` command to distinguish the tag to be added from plan-specifying arguments, if necessary. - Changed the short variant of the `--conflicts` option to the `add` and `rework` commands from `-c` to `-x`. The `-c` option is now used as the short variant for `--change` (and `--conflicts` has almost certainly never been used, anyway). - Added the `engine` and `project` variables to the execution of script templates by the `add` command. The default templates now use it to make their first lines one of: * -- Deploy [% project %]:[% change %] to [% engine] * -- Revert [% project %]:[% change %] from [% engine] * -- Verify [% project %]:[% change %] on [% engine] [Bug Fixes] - DateTime::TimeZone::Local::Win32 is now required on Windows. - The MySQL engine no longer passes `--skip-pager` on Windows, since it is not supported there. Thanks to Gabriel Potk獺ny for the report (Issue #213). - Fixed "no such table: changes" error when upgrading the SQLite registry. - Fixed upgrade failure on PostgreSQL 8.4. Thanks to Phillip Smith for the report! - Fixed an error when the `status` command `show_changes` and `show_tags` configuration variables were set. Thanks to Adrian Klaver for the report (Issue #219). - Fixed `log` and `plan` usage statements to properly spell `--abbrev`. Thanks to Adrian Klaver for the report (Issue #220). - Fixed the formatting of change notes so that a space precedes the `#` character whether the note was added by the `--note` option or via an editor. - Fixed a bug when parsing plan files with DOS/Windows line endings. Thanks to Timothy Procter for the report (Issue #212). - Looking up a change and tag in the database (via the `--onto` option to `rebase` or the `--to` option to `revert`, among others) would sometimes return the incorrect change if the change has been reworked two or more times. Thanks to BryLo for the report! [Documentation] - Updated docs to be consistent in referring to the location of the system configuration and template location as `$(prefix)/etc/sqitch`. Also added notes pointing to the `--etc-dir` to find out exactly what that resolves to. Suggested by Joseph Anthony Pasquale Holsten (Issue #167). [Deprecations] - Reverted deprecation of the database connection options. Target URIs are still generally preferred, but sometimes you want to use a target but just change the user name or database name. Retaining the options is the easiest way to do this. Plus, a fair number of people have scripts that use these options, and it seems petty to break them. Sorry for the double-take here! The list of un-deprecated options is: * `--db-client` * `--db-host` * `--db-port` * `--db-username` * `--db-password` * `--db-name` 0.999 2015-02-12T19:43:45Z - Improved MySQL missing table error detection by relying on error codes instead of matching a (possibly localized) error string. - Made the registry upgrade more transparent when deploying. Sqitch is now is a little more vigilent in checking for things being out-of-date and updating them. - Fixed an issue where the `status` command would return an error when run against a an older version of the registry. - Fixed a Postgres test failure when DBD::Pg is installed but psql is not in the path. - Now require Config::GitLike 1.15 to build on Windows in order to avoid test failures when Cwd::abs_path dies on non-existant paths. - Clarified the behavior of each `deploy` reversion mode with regard to deploy script vs. verify script failures, and with the expectation that deploy scripts are atomic. - Target passwords can now be set via a single environment variable, `$SQITCH_PASSWORD`. Its value will override URI-specified password. - Added the sqitch-passwords and sqitch-environment guides. 0.998 2015-01-15T22:17:44Z - Fixed a bug in `sqitch engine update-config` where it would add data to config files that did not previously have them, or report that data was present in nonexistent config files. - Added the `releases` table to the databases. This table will keep track of releases of the Sqitch registry schema. - The Oracle `registry` variable is now always `DEFINE`d when Oracle scripts run. - Added the `upgrade` command, which upgrades the schema for the Sqitch registry for a target database. - Added the `script_hash` column to the `changes` registry table. This column contains a SHA-1 hash of the deploy script for the change at the time it was deployed. For existing registries, the upgrade script sets its value to be the same as the change ID. This value is update the next time a project is deployed to the database. - The error message when `deploy` cannot find the currently-deployed change ID in the plan now includes more contextual information, including the change name, associated tags, and the plan file name. Suggested by Curtis Poe (Issue #205). - Comments on Firebird registry objects are now created with the `COMMENT` command, rather than INSERTs into catalog tables. - Added support for "merge" events, though none are logged, yet.
### 3.5.0 / 2016-07-01 [Full Changelog](http://github.com/rspec/rspec-support/compare/v3.5.0.beta4...v3.5.0) **No user facing changes since beat4** ### 3.5.0.beta4 / 2016-06-05 [Full Changelog](http://github.com/rspec/rspec-support/compare/v3.5.0.beta3...v3.5.0.beta4) Enhancements: * Improve `MethodSignature` to better support keyword arguments. (#250, Rob Smith). ### 3.5.0.beta3 / 2016-04-02 [Full Changelog](http://github.com/rspec/rspec-support/compare/v3.5.0.beta2...v3.5.0.beta3) Bug Fixes: * Fix `EncodedString` to properly handle the behavior of `String#split` on JRuby when the string contains invalid bytes. (Jon Rowe, #268) * Fix `ObjectFormatter` so that formatting objects that don't respond to `#inspect` (such as `BasicObject`) does not cause `NoMethodError`. (Yuji Nakayama, #269) * Fix `ObjectFormatter` so that formatting recursive array or hash does not cause `SystemStackError`. (Yuji Nakayama, #270, #272) ### 3.5.0.beta2 / 2016-03-10 [Full Changelog](http://github.com/rspec/rspec-support/compare/v3.5.0.beta1...v3.5.0.beta2) No user-facing changes. ### 3.5.0.beta1 / 2016-02-06 [Full Changelog](http://github.com/rspec/rspec-support/compare/v3.4.1...v3.5.0.beta1) Enhancements: * Improve formatting of objects by allowing truncation to a pre-configured length. (Liam M, #256)
* Release 0.12.5 (07-Dec-2016) ** Connection Status Reporting This release adds an object named `ConnectionInfo`, which encapsulates information about a connection (both progress while being established, and the outcome once connected). This includes which connection hint was successful, what happened with the other hints, which handlers were used for each, and when the connection was made or lost. To get one of these, use `tub.getConnectionInfoForFURL(furl)` any time after `getReference()` is called, or `rref.getConnectionInfo()` after it resolves. #267 It also adds `ReconnectionInfo`, a similar object for Reconnectors. These capture the state of reconnection process (trying, established, waiting), and will provide a `ConnectionInfo` for the most recent (possibly successful) connection attempt. The API is `reconnector.getReconnectionInfo()`. #268 For details, see "Connection Progress/Status" and "Reconnector Status" in `doc/using-foolscap.rst`. ** Connection Handler API Changes To support `ConnectionInfo`, the Connection Handler API was changed. The one backwards-incompatible change was that the `hint_to_endpoint()` method now takes a third argument, to update the status as the handler makes progress. External handler functions will need to be modified to accept this new argument, and applications which use them should declare a dependency upon the latest Foolscap version, to avoid runtime breakage. Several backwards-compatible changes were made too: handlers can provide a `describe()` method (which feeds `ConnectionInfo.connectionHandlers`), and they can now set a special attribute on any exception they raise, to further influence the status string. In addition, the `tor.control_endpoint_maker()` handler now accepts an optional second argument, which causes the maker function to be called with a additional `update_status` argument. This backwards-compatible change allows the maker function to influence the `ConnectionInfo` status too. The Tor connection handler was enhanced to report distinct statuses for the different phases of connection: launching a new copy of Tor, connecting to an existing Tor daemon, etc. ** Minor Fixes Foolscap-0.12.0 broke `flappserver create`, causing the command to hang rather than exiting cleanly (although the flappserver directory itself was probably created properly). This release finally fixes it. #271
This upgrade fixes compatibility with new lxml. Upstream changelog ================== 2.3.1 _This is a micro release and I have very little time on my hands right now sorry_ Fix crash with no values when the print_values_position param is set (thanks @cristen) 2.3.0 New call API: chart = Line(fill=True); chart.add('title', [1, 3, 12]); chart.render() can now be replaced with Line(fill=True)(1, 3, 12, title='title').render() Drop python 2.6 support 2.2.3 Fix bar static value positioning (#315) Add stroke_opacity style (#321) Remove useless js in sparklines. (#312) 2.2.2 Add classes option. Handle ellipsis in list type configs to auto-extend parent. (Viva python3) 2.2.0 Support interruptions in line charts (thanks @piotrmaslanka #300) Fix confidence interval reactiveness (thanks @chartique #296) Add horizontal line charts (thanks @chartique #301) There is now a formatter config option to format values as specified. The formatter callable may or may not take chart, serie and index as argument. The default value formatting is now chart dependent and is value_formatter for most graph but could be a combination of value_formatter and x_value_formatter for dual charts. The human_readable option has been removed. Now you have to use the pygal.formatters.human_readable formatter (value_formatter=human_readable instead of human_readable=True) New chart type: SolidGauge (thanks @chartique #295) Fix range option for some Charts (#297 #298) Fix timezones for DateTimeLine for python 2 (#306, #302) Set default uri protocol to https (should fix a lot of "no tooltips" bugs). 2.1.1 Import scipy as a last resort in stats.py (should workaround bugs like #294 if scipy is installed but not used) 2.1.0 Bar print value positioning with print_values_position. Can be top, center or bottom (thanks @chartique #291) ci doc Confidence intervals (thanks @chartique #292) data doc 2.0.12 Use custom xml_declaration avoiding conflict with processing instructions 2.0.11 lxml 3.5 compatibility (#282) 2.0.10 Fix transposable_node in case all attributes are not there. (thanks @yobuntu). 2.0.9 Add dynamic_print_values to show print_values on legend hover. (#279) Fix unparse_color for python 3.5+ compatibility (thanks @felixonmars, @sjourdois) Process major labels as labels. (#263) Fix labels rotation > 180 (#257) Fix secondary axis Don't forget secondary series in table rendering (#260) Add defs config option to allow adding gradients and patterns. 2.0.8 Fix value overwrite in map. (#275) 2.0.7 Fixing to checks breaking rendering of DateTimeLine and TimeDeltaLine (#264) (thanks @mmrose) Fix render_in_browser. (#266) (#268) (thanks @waixwong) 2.0.6 Avoid x label formatting when label is a string 2.0.5 Fix x label formatting 2.0.4 Fix map coloration 2.0.3 Fix label adaptation. (#256) Fix wrong radar truncation. (#255) 2.0.2 Fix view box differently to avoid getting a null height on huge numbers. (#254) Fix broken font_family default Fix non namespaced svg (without embed) javascript by adding uuid in config object. (config is in window.pygal now). 2.0.1 Fix the missing title on x_labels with labels. Auto cast to str x labels in non dual charts (#178) Add print_labels option to print label too. (#197) Add value_label_font_family and value_label_font_size style options for print_labels. Default print_zeroes to True (Re)Add xlink in desc to show on tooltip Activate element on tooltip hovering. (#106) Fix radar axis behaviour (#247) Add tooltip support in metadata to add a title (#249). Take config class options in account too. 2.0.0 Rework the ghost mechanism to come back to a more object oriented behavior, storing all state in a state object which is created on every render. (#161) Refactor maps Add world continents Add swiss cantons map (thanks @sergedroz) Add inverse_y_axis options to reverse graph (#24) Fix DateTimeLine time data loss (#193) Fix no data for graphs with only zeroes (#148) Support value formatter for pie graphs (#218) (thanks @never-eat-yellow-snow) Add new Box plot modes and outliers and set extremes as default (#226 #121 #149) (thanks @djezar) Add secondary_range option to set range for secondary values. (#203) Maps are now plugins, they are removed from pygal core and moved to packages (pygal_maps_world, pygal_maps_fr, pygal_maps_ch, ...) (#225) Dot now supports negative values Fix dot with log scale (#201) Fix y_labels behaviour for lines Fix x_labels and y_labels behaviour for xy like Improve gauge a bit Finally allow call chains on add Transform min_scale and max_scale as options mode option has been renamed to a less generic name: box_mode fix stack_from_top for stacked lines Add flake8 test to py.test in tox Remove stroke style in style and set it as a global / serie configuration. Fix None values in tables Fix timezones in DateTimeLine Rename in Style foreground_light as foreground_strong Rename in Style foreground_dark as foreground_subtle Add a render_data_uri method (#237) Move font_size config to style Add font_family for various elements in style Add googlefont:font support for style fonts Add tooltip_fancy_mode to revert to old tooltips Add auto print_value color + a configurable value_colors list in style Add guide_stroke_dasharray and guide_stroke_dasharray in style to customize guides (#242) (thanks @cbergmiller) Refactor label processing in a _compute_x_labels and _compute_y_labels method. Handle both string and numbers for all charts. Create a Dual base chart for dual axis charts. (#236) Better js integration in maps. Use the normal tooltip.
Ansible 1.6.10 from base-64 15.1.1 (0edf00aa-0562-11e5-b92f-879647d45790) with default settings looks for python 2 interpreter in /usr/bin instead of /opt/local/bin.
This is fine if the target host one tries to manage is not SmartOS (like some Linux distros).
But if the intent is to run ansible from within a SmartOS VM (zone) and to manage target zones then it would make more sense for ansible to look for python in /opt/local/bin
Currently this means that one has to append ansible_python_interpreter=/opt/local/bin/python to each target host which is a SmartOS VM (zone).
[root@ansible /opt/local/etc/ansible]# head -1 hosts
192.168.3.216
[root@ansible /opt/local/etc/ansible]# ansible -m ping 192.168.3.216
192.168.3.216 | FAILED >> {
"failed": true,
"msg": "/bin/sh[1]: /usr/bin/python: not found [No such file or directory]\r\n",
"parsed": false
}
[root@ansible /opt/local/etc/ansible]# head -1 hosts
192.168.3.216 ansible_python_interpreter=/opt/local/bin/python
[root@ansible /opt/local/etc/ansible]# ansible -m ping 192.168.3.216
192.168.3.216 | success >> {
"changed": false,
"ping": "pong"
}
The text was updated successfully, but these errors were encountered: