Download Autodata 340 Ita
Anfos Sin
Terms of the transaction were not made public, and the closing is expected to be completed within the coming weeks, subject to customary closing conditions. Following the transaction, the Autodata Solutions management team will remain intact and will continue to operate from its headquarters in London, Ontario, Canada and Troy, Michigan, with offices in Portland, Oregon, Minneapolis, Minnesota, and Calgary, Alberta, Canada.
RBC Capital Markets is serving as the exclusive financial advisor to Internet Brands, and Simpson Thatcher is serving as the legal advisor to Internet Brands. Kirkland & Ellis is serving as the legal advisor to Thoma Bravo. Financing for the transaction is being provided by RBC Capital Markets and KKR Capital Markets LLC.
The Autodata Solutions Group serves the global automotive industry with versatile data, technology, and marketing solutions. Founded in 1990, the company is headquartered in London, Ontario, Canada and has offices in Troy Michigan, Portland, Oregon and Minneapolis, Minnesota. Autodata Solutions, along with its Chrome Data and UnityWorks brands, serves the automotive industry with software and SaaS solutions that increase the effectiveness of the automotive sales chain. For more information, visit www.autodata.net.
Headquartered in El Segundo, Calif., Internet Brands is a fully integrated online media and software services organization focused on four high-value vertical categories: Automotive, Legal, Health, and Home/Travel. The company's award-winning consumer websites lead their categories and serve more than 250 million monthly visitors, while a full range of web presence offerings has established deep, long-term relationships with SMB and enterprise clients. Internet Brands' powerful, proprietary operating platform provides the flexibility and scalability to fuel the company's continued growth. Internet Brands is a portfolio company of KKR and Temasek. For more information, visit www.internetbrands.com.
For this to work, the docstrings must of course be written in correctreStructuredText. You can then use all of the usual Sphinx markup in thedocstrings, and it will end up correctly in the documentation. Together withhand-written documentation, this technique eases the pain of having to maintaintwo locations for documentation, while at the same time avoidingauto-generated-looking pure API documentation.
If you prefer NumPy or Google style docstrings over reStructuredText,you can also enable the napoleon extension.napoleon is a preprocessor that converts yourdocstrings to correct reStructuredText before autodoc processes them.
autodoc analyses the code and docstrings by introspection afterimporting the modules. For importing to work, you have to make sure that yourmodules can be found by Sphinx and that dependencies can be resolved (if yourmodule does import foo, but foo is not available in the python environmentthat Sphinx runs in, your module import will fail).
Use an environment that contains your package and Sphinx. This can e.g. be yourlocal dev environment (with an editable install), or an environment in CI inwhich you install Sphinx and your package. The regular installation processensures that your package can be found by Sphinx and that all dependencies areavailable.
autodoc provides several directives that are versions of the usualpy:module, py:class and so forth. On parsing time, theyimport the corresponding module and extract the docstring of the given objects,inserting them into the page source under a suitable py:module,py:class etc. directive.
Another example; If your class Foo has __str__ special method andautodoc directive has both inherited-members and special-members,__str__ will be documented as in the past, but other special methodthat are not implemented in your class Foo.
The automodule, autoclass andautoexception directives also support a flag option calledshow-inheritance. When given, a list of base classes will be insertedjust below the class signature (when used with automodule, thiswill be inserted for every class that is documented in the module).
All autodoc directives support the no-index flag option that has thesame effect as for standard py:function etc. directives: noindex entries are generated for the documented object (and allautodocumented members).
In an automodule directive with the members option set, onlymodule members whose __module__ attribute is equal to the module nameas given to automodule will be documented. This is to preventdocumentation of imported classes or functions. Set theimported-members option if you want to prevent this behavior anddocument all available members. Note that attributes from imported moduleswill not be documented, because attribute documentation is discovered byparsing the source file of the current module.
autodata and autoattribute support the annotationoption. The option controls how the value of variable is shown. If specifiedwithout arguments, only the name of the variable will be printed, and its valueis not shown:
For module data members and class attributes, documentation can either be putinto a comment with special formatting (using a #: to start the commentinstead of just #), or in a docstring after the definition. Commentsneed to be either on a line of their own before the definition, orimmediately after the assignment on the same line. The latter form isrestricted to one line only.
If you document decorated functions or methods, keep in mind that autodocretrieves its docstrings by importing the module and inspecting the__doc__ attribute of the given function or method. That means that ifa decorator replaces the decorated function with another, it must copy theoriginal __doc__ to the new function.
This value selects if automatically documented members are sortedalphabetical (value 'alphabetical'), by member type (value'groupwise') or by source order (value 'bysource'). The default isalphabetical.
This value is a list of autodoc directive flags that should be automaticallyapplied to all autodoc directives. The supported flags are 'members','undoc-members', 'private-members', 'special-members','inherited-members', 'show-inheritance', 'ignore-module-all'and 'exclude-members'.
If this boolean value is set to True (which is the default), autodoc willlook at the first line of the docstring for functions and methods, and if itlooks like a signature, use the line as the signature and remove it from thedocstring content.
This value contains a list of modules to be mocked up. This is useful whensome external dependencies are not met at build time and break the buildingprocess. You may only specify the root package of the dependenciesthemselves and omit the sub-modules:
Return a listener that either keeps, or if exclude is True excludes,lines between lines that match the marker regular expression. If no linematches, the resulting docstring would be empty, so no change will be madeunless keepempty is true.
If more than one enabled extension handles the autodoc-skip-memberevent, autodoc will use the first non-None value returned by a handler.Handlers should return None to fall back to the skipping behavior ofautodoc and other enabled extensions.
Customers of Autodata include most of the automotive companies in North America including Chrysler, Ford, GM, Nissan, Toyota, Mazda, Honda, Hyundai, Kia, Volvo, and Jaguar. The company, founded in 1990, is headquartered in London, ON and Troy, MI with additional offices in Portland, OR; Minneapolis, MN; and Calgary, AB (www.autodata.net).
KKR (NYSE: KKR) makes private equity, fixed income and other investments in companies in North America, Europe, Asia and the Middle East. KKR was founded in 1976 and in addition to its New York headquarters has offices in 19 cities around the world (www.kkr.com).
b1e95dc632