Skip to main content

How to properly declare optional dependencies both as extras and in dedicated groups in Poetry?

From Poetry documentation about the difference between groups and extras:

Dependency groups, other than the implicit main group, must only contain dependencies you need in your development process. Installing them is only possible by using Poetry. To declare a set of dependencies, which add additional functionality to the project during runtime, use extras instead. Extras can be installed by the end user using pip.

This perfectly makes sense and works fine most of the time. However, during development one usually wants to install all the extras dependencies in order to test all the functionalities of the package. However, extras are not installed by default contrary to groups. Moreover, the Poetry documentation states that:

The dependencies specified for each extra must already be defined as project dependencies.

Dependencies listed in dependency groups cannot be specified as extras.

Thus, because it is not possible to define extras in a Poetry project that are defined in dependency groups and because extras are not installed by default, this left 2 suboptimal options for the developer to get a nice developer experience:

  • Installing the project with poetry install --all-extras. This has the downside that the developer ha to remember to pass this option during development, even when the dev dependency group is installed.
  • Mirroring the extras dependencies in a corresponding dependency group. This has the downside to introduce a lot of boilerplate and possible errors since dependencies are listed multiple times.

For instance, the second case would look like:

[tool.poetry.dependencies]
python = "^3.8,<3.12"
numpy = "^1.22"
scipy = { version = "^1.8", optional = true }

[tool.poetry.group.dev.dependencies]
scipy = "^1.8"

[tool.poetry.extras]
plot = ["scipy"]

In this example there is an extra that requires the SciPy dependency. This dependency is declared as optional in the main dependency group, as recommended by Poetry. However, this dependency should additionally be declared in the dev dependency group in order to organize the development dependencies and have it installed automatically.

Is there a simpler approach to solve this problem that do not requires specifying multiple times the same dependency?



source https://stackoverflow.com/questions/77512072/how-to-properly-declare-optional-dependencies-both-as-extras-and-in-dedicated-gr
Labels:

Comments

Post a Comment

Popular posts from this blog

Where and how is this Laravel kernel constructor called? [closed]

Where and how is this Laravel kernel constructor called? public fucntion __construct(Application $app, $Router $roouter) { } I have read the documentation and some online tutorial but I can find any clear explanation. I am learning Laravel and I am wondering where does this kernel constructor receives its arguments from. "POSTMOTERM" CLARIFICATION: Here is more clarity.I have checked the boostrap/app.php and it is only used for boostrapping the interfaces into the container class. What is not clear to me is where and how the Kernel class is instatiated and the arguments passed to the object calling the constructor.Something similar to; obj = new kernel(arg1,arg2) or, is the framework using some magic functions somewhere? Special gratitude to those who burn their eyeballs and brain cells on this trivia before it goes into a full blown menopause alias "MARKED AS DUPLICATE". To some of the itchy-finger keyboard warriors, a.k.a The mods,because I believe in th...
Post a Comment
Read more

Why is my reports service not connecting?

I am trying to pull some data from a Postgres database using Node.js and node-postures but I can't figure out why my service isn't connecting. my routes/index.js file: const express = require('express'); const router = express.Router(); const ordersCountController = require('../controllers/ordersCountController'); const ordersController = require('../controllers/ordersController'); const weeklyReportsController = require('../controllers/weeklyReportsController'); router.get('/orders_count', ordersCountController); router.get('/orders', ordersController); router.get('/weekly_reports', weeklyReportsController); module.exports = router; My controllers/weeklyReportsController.js file: const weeklyReportsService = require('../services/weeklyReportsService'); const weeklyReportsController = async (req, res) => { try { const data = await weeklyReportsService; res.json({data}) console...
Post a Comment
Read more

How to show number of registered users in Laravel based on usertype?

i'm trying to display data from the database in the admin dashboard i used this: <?php use Illuminate\Support\Facades\DB; $users = DB::table('users')->count(); echo $users; ?> and i have successfully get the correct data from the database but what if i want to display a specific data for example in this user table there is "usertype" that specify if the user is normal user or admin i want to user the same code above but to display a specific usertype i tried this: <?php use Illuminate\Support\Facades\DB; $users = DB::table('users')->count()->WHERE usertype =admin; echo $users; ?> but it didn't work, what am i doing wrong? source https://stackoverflow.com/questions/68199726/how-to-show-number-of-registered-users-in-laravel-based-on-usertype
Post a Comment
Read more