File tree Expand file tree Collapse file tree 2 files changed +5
-4
lines changed Expand file tree Collapse file tree 2 files changed +5
-4
lines changed Original file line number Diff line number Diff line change @@ -142,7 +142,8 @@ And it can be used in plugin importing the module:
142
142
Storage, activation and sharing
143
143
-------------------------------
144
144
145
- Plugins are Python files stored under *~/.conan/plugins * folder and their file name should be the same used for activation.
145
+ Plugins are Python files stored under *~/.conan/plugins * folder and **their file name should be the same used for activation ** (without the
146
+ *.py * extension).
146
147
147
148
The activation of the plugins is done in the *conan.conf * section named ``[plugins] ``. The plugin names listed under this section will be
148
149
considered activated.
Original file line number Diff line number Diff line change @@ -146,7 +146,7 @@ subsequent **pre**/**post** ``download_package()``/``upload_package()`` if that
146
146
using :command: `conan create ` or :command: `conan install `.
147
147
148
148
Function parameters
149
- --------------------
149
+ -------------------
150
150
151
151
Here you can find the description for each parameter:
152
152
@@ -193,14 +193,14 @@ Table legend:
193
193
- **post **: Only available in ``post `` function.
194
194
- **cache **: Only available when the context of the command executed is the local cache. e.g. :command: `conan create `,
195
195
:command: `conan install `...
196
- - **user space **: Only available when the context of the command executed is the local cache . e.g. :command: `conan build `
196
+ - **user space **: Only available when the context of the command executed is the user space . e.g. :command: `conan build `
197
197
198
198
.. note ::
199
199
200
200
Path to the different folders of the Conan execution flow may be accessible as usual through the ``conanfile `` object. See
201
201
:ref: `folders_attributes_reference ` to learn more.
202
202
203
- Some of this parameters does not appear in the signature of the function as they may not be available always (Mostly depending on the recipe
203
+ Some of this parameters does not appear in the signature of the function as they may not be always available (Mostly depending on the recipe
204
204
living in the local cache or in user space). However, they can be checked with the ``kwargs `` parameter.
205
205
206
206
.. important ::
You can’t perform that action at this time.
0 commit comments