mirror of https://github.com/ansible/ansible.git
Add a Singleton metaclass, use it with Display (#48935)
* Add a Singleton class, use it with Display * update six import * Move remaining failes to display singleton * Fix rebase issues * Singleton improvements * Add code-smell for 'from __main__ import display'. ci_complete * s/self/cls/g * Add docs for no-main-display * Address linting issues * Add changelog fragment. ci_complete * Implement reentrant lock for class instantiation in Singleton * Add Display singleton porting guidepull/48778/head
parent
54a2f21f93
commit
9773a1f289
@ -0,0 +1,2 @@
|
||||
minor_changes:
|
||||
- Display - Add a ``Singleton`` metaclass and apply it to ``Display`` to remove the need of using ``__main__.Display`` as a pseudo singleton
|
@ -0,0 +1,12 @@
|
||||
Sanity Tests » no-main-display
|
||||
==============================
|
||||
|
||||
As of Ansible 2.8, ``Display`` should no longer be imported from ``__main__``.
|
||||
|
||||
``Display`` is now a singleton and should be utilized like the following::
|
||||
|
||||
from ansible.utils.display import Display
|
||||
display = Display()
|
||||
|
||||
There is no longer a need to attempt ``from __main__ import display`` inside
|
||||
a ``try/except`` block.
|
Some files were not shown because too many files have changed in this diff Show More
Loading…
Reference in New Issue