e3c843042aAccepting request 1299433 from home:fstegmeier:branches:devel:languages:pythonNico Krapp2025-08-15 08:32:52 +00:00
d2baa3d674Accepting request 1294585 from devel:languages:pythonAna Guerrero2025-07-21 18:00:22 +00:00
0148444d6b- update to 0.20.0: * When FawltyDeps finds a 3rd-party import that is not declared, it will output that import name as an undeclared dependency. But as we've talked about before, _import_ names in Python are not necessarily synonymous with the _package_ names that you would have to declare in order to make those import names available. * For example, if you import sklearn in your code, it might not be obvious that the corresponding dependency declaration should be scikit-learn, and not sklearn. * Starting with this version, if you run FawltyDeps with the --detailed option, _and_ if there happens to be one or more (undeclared) packages in your Python environment that provide the relevant import name, then FawltyDeps will suggest these packages as potential solutions to your undeclared dependency. * By default (and before this release) FawltyDeps looks at the paths on the command-line to deduce where 1st-party imports (i.e. your project's own modules) can be found. In some corner cases this deduction fails, and the result is typically that a 1st-party import is flagged by FawltyDeps as an undeclared dependency. * The new --base-dir allows you to control where FawltyDeps looks for 1st-party imports, and it can help fix those cases where the default deduction fails, for example in cases where you are passing individual file names (instead of directory names) on the FawltyDeps command line.Dirk Mueller2025-07-13 12:16:48 +00:00
5fe3f02623Accepting request 1266330 from devel:languages:pythonAna Guerrero2025-04-02 15:16:16 +00:00
ef5fe3462cAccepting request 1266317 from home:nkrapp:branches:devel:languages:pythonMatej Cepl2025-04-01 21:20:57 +00:00
e1266a457aAccepting request 1244793 from devel:languages:pythonAna Guerrero2025-02-10 17:19:22 +00:00