Releases: jason-kane/PyYapf
Improved ST 2.x compatibility
Because why not. ST2 should be good again but ... upgrade, ST3 is nice.
Format on save with wildcard exclusion
There are formats (like pyx) that are recognized as python by sublime but are not compatible with yapf. This lets you set wildcard filename ignore patterns to avoid triggering automatic formatting.
With the code changes...
Merge the PR, then cut a release. One of these days I will the sequence right.
Find Yapf in path and better yapf_command
This release adds a where yapf
style search to hunt for the executable in your path. This should reduce the most common difficulty users have getting pyyapf working. We've also improved the yapf_command override to accept commands with arguments. The yapf arguments are appended to whatever you put in the yapf_command field.
Keybindings Menu
Settings menu option to easily access the keybindings appropriate to your platform. Also makes the Readme more easily accessible. Thanks to @ricelid for the feature request and @catch22 for putting it together.
use_stdin by default
Changed default input method to use_stdin
. This should be faster and more reliable. Users with (very) old versions of sublime that can't/don't want to upgrade may have to change use_stdin
to false
in the settings file to avoid a unicode error.
This version is entirely by @catch22. It is a bigger change than the diff suggests. Sorry I took so long pushing the release out to get picked up by Sublime Package Control.
Per-project settings
This release adds per-project settings files following the general approach used by prettifier js. The code contribution came from @mikelambert with code review by @catch22.
Rollup of patches from the last 6 months
Multiple changes from @catch22 and a tweak from @gwelymernans. Most of these are (long overdue) internal cleanups.
Unicode fixup, should work in both
My apologies for the flurry of releases; this should take care of osx/st3 and unicode. Some upstream contributions will be needed for a clean fix.
Fixed viewing/editing global settings file
kind of a nasty oops, not sure when that happened.