From b8677040ae06b2b673f2d0f3806b043ca48f24df Mon Sep 17 00:00:00 2001 From: Jeff Irion Date: Wed, 7 Aug 2019 08:07:59 -0700 Subject: [PATCH] Remove message about putting imports inside functions (#299) --- docs/creating_integration_manifest.md | 2 -- 1 file changed, 2 deletions(-) diff --git a/docs/creating_integration_manifest.md b/docs/creating_integration_manifest.md index 404df5b0..4f2b9c70 100644 --- a/docs/creating_integration_manifest.md +++ b/docs/creating_integration_manifest.md @@ -65,8 +65,6 @@ Requirements are Python libraries or modules that you would normally install usi Requirements is an array of strings. Each entry is a `pip` compatible string. For example, the media player Cast platform depends on the Python package PyChromecast v3.2.0: `["pychromecast==3.2.0"]`. -> Because of how Home Assistant installs requirements on demand, actual Python imports of your requirements should be done inside functions instead of at the root level of your Python files. - ### Custom requirements during development & testing During the development of a component, it can be useful to test against different versions of a requirement. This can be done in two steps, using `pychromecast` as an example: