Package: isort-plus
isort your python imports for you so you don’t have to.isort is a Python utility / library to sort imports alphabetically, and automatically separated into sections.
It provides a command line utility, Python library andplugins for various editorsto quickly sort all your imports.
It currently cleanly supports Python 2.7 - 3.6 without any dependencies.Before isort:frommy_libimportObjectprint("Hey")importosfrommy_libimportObject3frommy_libimportObject2importsysfromthird_partyimportlib15,lib1,lib2,lib3,lib4,lib5,lib6,lib7,lib8,lib9,lib10,lib11,lib12,lib13,lib14importsysfrom__future__importabsolute_importfromthird_partyimportlib3print("yo")After isort:from__future__importabsolute_importimportosimportsysfromthird_partyimport(lib1,lib2,lib3,lib4,lib5,lib6,lib7,lib8,lib9,lib10,lib11,lib12,lib13,lib14,lib15)frommy_libimportObject,Object2,Object3print("Hey")print("yo")Installing isortInstalling isort is as simple as:pipinstallisortInstall isort with requirements.txt support:pipinstallisort[requirements]Install isort with Pipfile support:pipinstallisort[pipfile]Install isort with both formats support:pipinstallisort[requirements,pipfile]Using isortFrom the command line:isortmypythonfile.pymypythonfile2.pyor recursively:isort-rc.which is equivalent to:isort**/*.pyor to see the proposed changes without applying them:isortmypythonfile.py--diffFinally, to atomically run isort against a project, only applying changes if they don’t introduce syntax errors do:isort-rc--atomic.(Note: this is disabled by default as it keeps isort from being able to run against code written using a different version of Python)From within Python:fromisortimportSortImportsSortImports("pythonfile.py")or:fromisortimportSortImportsnew_contents=SortImports(file_contents=old_contents).outputFrom within Kate:ctrl+[or:menu>Python>SortImportsInstalling isort’s Kate pluginFor KDE 4.13+ / Pate 2.0+:wgethttps://raw.github.com/timothycrosley/isort/master/kate_plugin/isort_plugin.py--output-document~/.kde/share/apps/kate/pate/isort_plugin.pywgethttps://raw.github.com/timothycrosley/isort/master/kate_plugin/isort_plugin_ui.rc--output-document~/.kde/share/apps/kate/pate/isort_plugin_ui.rcwgethttps://raw.github.com/timothycrosley/isort/master/kate_plugin/katepart_isort.desktop--output-document~/.kde/share/kde4/services/katepart_isort.desktopFor all older versions:wgethttps://raw.github.com/timothycrosley/isort/master/kate_plugin/isort_plugin_old.py--output-document~/.kde/share/apps/kate/pate/isort_plugin.pyYou will then need to restart kate and enable Python Plugins as well as the isort plugin itself.Installing isort’s for your preferred text editorSeveral plugins have been written that enable to use isort from within a variety of text-editors.
You can find a full list of themon the isort wiki.
Additionally, I will enthusiastically accept pull requests that include plugins for other text editors
and add documentation for them as I am notified.How does isort work?isort parses specified files for global level import lines (imports outside of try / except blocks, functions, etc..)
and puts them all at the top of the file grouped together by the type of import:FuturePython Standard LibraryThird PartyCurrent Python ProjectExplicitly Local (. before import, as in:from . import x)Custom Separate Sections (Defined by forced_separate list in configuration file)Custom Sections (Defined by sections list in configuration file)Inside of each section the imports are sorted alphabetically. isort automatically removes duplicate python imports,
and wraps long from imports to the specified line length (defaults to 79).When will isort not work?If you ever have the situation where you need to have a try / except block in the middle of top-level imports or if
your import order is directly linked to precedence.For example: a common practice in Django settings files is importing * from various settings files to form
a new settings file. In this case if any of the imports change order you are changing the settings definition itself.However, you can configure isort to skip over just these files - or even to force certain imports to the top.Configuring isortIf you find the default isort settings do not work well for your project, isort provides several ways to adjust
the behavior.To configure isort for a single user create a~/.isort.cfgfile:[settings]line_length=120force_to_top=file1.py,file2.pyskip=file3.py,file4.pyknown_future_library=future,piesknown_standard_library=std,std2known_third_party=randomthirdpartyknown_first_party=mylib1,mylib2indent='    'multi_line_output=3length_sort=1forced_separate=django.contrib,django.utilsdefault_section=FIRSTPARTYno_lines_before=LOCALFOLDERAdditionally, you can specify project level configuration simply by placing a.isort.cfgfile at the root of your
project. isort will look up to 25 directories up, from the file it is ran against, to find a project specific configuration.Or, if you prefer, you can add an isort section to your project’ssetup.cfgortox.inifile with any desired settings.You can then override any of these settings by using command line arguments, or by passing in override values to the
SortImports class.Finally, as of version 3.0 isort supports editorconfig files using the standard syntax defined here:http://editorconfig.org/Meaning you place any standard isort configuration parameters within a .editorconfig file under the*.pysection
and they will be honored.For a full list of isort settings and their meaningstake a look at the isort wiki.Multi line output modesYou will notice above the “multi_line_output” setting. This setting defines how from imports wrap when they extend
past the line_length limit and has 6 possible settings:0 - Gridfromthird_partyimport(lib1,lib2,lib3,lib4,lib5,...)1 - Verticalfromthird_partyimport(lib1,lib2,lib3lib4,lib5,...)2 - Hanging Indentfromthird_partyimport\lib1,lib2,lib3,\lib4,lib5,lib63 - Vertical Hanging Indentfromthird_partyimport(lib1,lib2,lib3,lib4,)4 - Hanging Gridfromthird_partyimport(lib1,lib2,lib3,lib4,lib5,...)5 - Hanging Grid Groupedfromthird_partyimport(lib1,lib2,lib3,lib4,lib5,...)6 - NOQAfromthird_partyimportlib1,lib2,lib3,...# NOQAAlternatively, you can setforce_single_linetoTrue(-slon the command line) and every import will appear on its
own line:fromthird_partyimportlib1fromthird_partyimportlib2fromthird_partyimportlib3...Note: to change the how constant indents appear - simply change the indent property with the following accepted formats:
*   Number of spaces you would like. For example: 4 would cause standard 4 space indentation.
*   Tab
*   A verbatim string with quotes around it.For example:"    "is equivalent to 4.For the import styles that use parentheses, you can control whether or not to
include a trailing comma after the last import with theinclude_trailing_commaoption (defaults toFalse).Intelligently Balanced Multi-line ImportsAs of isort 3.1.0 support for balanced multi-line imports has been added.
With this enabled isort will dynamically change the import length to the one that produces the most balanced grid,
while staying below the maximum import length defined.Example:from__future__import(absolute_import,division,print_function,unicode_literals)Will be produced instead of:from__future__import(absolute_import,division,print_function,unicode_literals)To enable this setbalanced_wrappingtoTruein your config or pass the-eoption into the command line utility.Custom Sections and OrderingYou can change the section order withsectionsoption from the default of:FUTURE,STDLIB,THIRDPARTY,FIRSTPARTY,LOCALFOLDERto your preference:sections=FUTURE,STDLIB,FIRSTPARTY,THIRDPARTY,LOCALFOLDERYou also can define your own sections and their order.Example:known_django=djangoknown_pandas=pandas,numpysections=FUTURE,STDLIB,DJANGO,THIRDPARTY,PANDAS,FIRSTPARTY,LOCALFOLDERwould create two new sections with the specified known modules.Theno_lines_beforeoption will prevent the listed sections from being split from the previous section by an empty line.Example:sections=FUTURE,STDLIB,THIRDPARTY,FIRSTPARTY,LOCALFOLDERno_lines_before=LOCALFOLDERwould produce a section with both FIRSTPARTY and LOCALFOLDER modules combined.Auto-comment import sectionsSome projects prefer to have import sections uniquely titled to aid in identifying the sections quickly
when visually scanning. isort can automate this as well. To do this simply set theimport_heading_{section_name}setting for each section you wish to have auto commented - to the desired comment.For Example:import_heading_stdlib=Standard Libraryimport_heading_firstparty=My StuffWould lead to output looking like the following:# Standard Libraryimportosimportsysimportdjango.settings# My Stuffimportmyproject.testOrdering by import lengthisort also makes it easy to sort your imports by length, simply by setting thelength_sortoption toTrue.
This will result in the following output style:fromevn.utilimport(Pool,Dict,Options,Constant,DecayDict,UnexpectedCodePath,)Skip processing of imports (outside of configuration)To make isort ignore a single import simply add a comment at the end of the import line containing the textisort:skip:importmodule# isort:skipor:fromxyzimport(abc,# isort:skipyo,hey)To make isort skip an entire file simply addisort:skip_fileto the module’s doc string:""" my_module.py
    Best module ever

   isort:skip_file
"""importbimportaAdding an import to multiple filesisort makes it easy to add an import statement across multiple files, while being assured it’s correctly placed.From the command line:isort-a"from __future__ import print_function"*.pyfrom within Kate:ctrl+]or:menu > Python > Add ImportRemoving an import from multiple filesisort also makes it easy to remove an import from multiple files, without having to be concerned with how it was originally
formatted.From the command line:isort-r"os.system"*.pyfrom within Kate:ctrl+shift+]or:menu > Python > Remove ImportUsing isort to verify codeThe--check-onlyoptionisort can also be used to used to verify that code is correctly formatted by running it with-c.
Any files that contain incorrectly sorted and/or formatted imports will be outputted tostderr.isort**/*.py-c-vbSUCCESS:/home/timothy/Projects/Open_Source/isort/isort_kate_plugin.pyEverythingLooksGood!ERROR:/home/timothy/Projects/Open_Source/isort/isort/isort.pyImportsareincorrectlysorted.One great place this can be used is with a pre-commit git hook, such as this one by @acdha:https://gist.github.com/acdha/8717683This can help to ensure a certain level of code quality throughout a project.Git hookisort provides a hook function that can be integrated into your Git pre-commit script to check
Python code before committing.To cause the commit to fail if there are isort errors (strict mode), include the following in.git/hooks/pre-commit:#!/usr/bin/env pythonimportsysfromisort.hooksimportgit_hooksys.exit(git_hook(strict=True))If you just want to display warnings, but allow the commit to happen anyway, callgit_hookwithout
thestrictparameter.Setuptools integrationUpon installation, isort enables asetuptoolscommand that checks Python files
declared by your project.Runningpython setup.py isorton the command line will check the files
listed in yourpy_modulesandpackages.  If any warning is found,
the command will exit with an error code:$pythonsetup.pyisortAlso, to allow users to be able to use the command without having to install
isort themselves, add isort to the setup_requires of yoursetup()like so:setup(name="project",packages=["project"],setup_requires=["isort"])Why isort?isort simply stands for import sort. It was originally called “sortImports” however I got tired of typing the extra
characters and came to the realization camelCase is not pythonic.I wrote isort because in an organization I used to work in the manager came in one day and decided all code must
have alphabetically sorted imports. The code base was huge - and he meant for us to do it by hand. However, being a
programmer - I’m too lazy to spend 8 hours mindlessly performing a function, but not too lazy to spend 16
hours automating it. I was given permission to open source sortImports and here we are :)Thanks and I hope you find isort useful!~Timothy Crosley