Script 'mail_helper' called by obssrc
Hello community,
here is the log from the commit of package python-fawltydeps for
openSUSE:Factory checked in at 2025-07-21 20:00:22
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Comparing /work/SRC/openSUSE:Factory/python-fawltydeps (Old)
and /work/SRC/openSUSE:Factory/.python-fawltydeps.new.8875 (New)
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Package is "python-fawltydeps"
Mon Jul 21 20:00:22 2025 rev:3 rq:1294585 version:0.20.0
Changes:
--------
--- /work/SRC/openSUSE:Factory/python-fawltydeps/python-fawltydeps.changes
2025-04-02 17:17:44.380365595 +0200
+++
/work/SRC/openSUSE:Factory/.python-fawltydeps.new.8875/python-fawltydeps.changes
2025-07-21 20:01:20.601690136 +0200
@@ -1,0 +2,31 @@
+Sun Jul 13 12:15:54 UTC 2025 - Dirk Müller <[email protected]>
+
+- 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.
+
+-------------------------------------------------------------------
Old:
----
fawltydeps-0.19.0.tar.gz
New:
----
fawltydeps-0.20.0.tar.gz
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Other differences:
------------------
++++++ python-fawltydeps.spec ++++++
--- /var/tmp/diff_new_pack.H5OFPP/_old 2025-07-21 20:01:21.309719600 +0200
+++ /var/tmp/diff_new_pack.H5OFPP/_new 2025-07-21 20:01:21.313719766 +0200
@@ -18,7 +18,7 @@
%{?sle15_python_module_pythons}
Name: python-fawltydeps
-Version: 0.19.0
+Version: 0.20.0
Release: 0
Summary: Find undeclared and unused 3rd-party dependencies in your
Python project
License: MIT
++++++ fawltydeps-0.19.0.tar.gz -> fawltydeps-0.20.0.tar.gz ++++++
/work/SRC/openSUSE:Factory/python-fawltydeps/fawltydeps-0.19.0.tar.gz
/work/SRC/openSUSE:Factory/.python-fawltydeps.new.8875/fawltydeps-0.20.0.tar.gz
differ: char 12, line 1
