Skip to content

Commit b6afd86

Browse files
BorjaEstalvarolopez
authored andcommitted
docs: update entry point configuration from setup.cfg to pyproject.toml
1 parent b6c97cc commit b6afd86

File tree

1 file changed

+7
-11
lines changed

1 file changed

+7
-11
lines changed

doc/source/user/v2-api.rst

Lines changed: 7 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -25,14 +25,12 @@ one will be served.
2525

2626
In order to define your entry points, your module should leverage setuptools and be
2727
ready to be installed in the system. Then, in order to define your entry points, you
28-
should add the following to your ``setup.cfg`` configuration file:
28+
should add the following to your ``pyproject.toml`` configuration file:
2929

30-
.. code-block:: ini
30+
.. code-block:: toml
3131
32-
[entry_points]
33-
34-
deepaas.v2.model =
35-
my_model = package_name.module
32+
[project.entry-points."deepaas.v2.model"]
33+
my_model = package_name.module
3634
3735
This will define an entry point in the ``deepaas.v2.model`` namespace, called
3836
``my_model``. All the required functionality will be fetched from the
@@ -42,12 +40,10 @@ This will define an entry point in the ``deepaas.v2.model`` namespace, called
4240
If you provide a class with the required functionality, the entry point will be
4341
defined as follows:
4442

45-
.. code-block:: ini
46-
47-
[entry_points]
43+
.. code-block:: toml
4844
49-
deepaas.v2.model =
50-
my_model = package_name.module:Class
45+
[project.entry-points."deepaas.v2.model"]
46+
my_model = package_name.module:Class
5147
5248
Again, this will define an entry point in the ``deepaas.v2.model`` namespace,
5349
called ``my_model``. All the required functionality will be fetched

0 commit comments

Comments
 (0)