2025-08-15 08:32:52 +00:00
|
|
|
-------------------------------------------------------------------
|
|
|
|
Thu Aug 14 14:09:44 UTC 2025 - Felix Stegmeier <felix.stegmeier@suse.com>
|
|
|
|
|
|
|
|
- Add missing runtime requirements
|
|
|
|
- Update to 0.20.0
|
|
|
|
* Expand user defined mapping documentation. by @obscurerichard in #480
|
|
|
|
* Follow-up after removing support for Python v3.8 by @jherland in #475
|
|
|
|
* Work around top-level venv special case by @jherland in #468
|
|
|
|
* Upgrade project declarations in pyproject.toml by @jherland in #481
|
|
|
|
* Suggest package names for undeclared imports, when possible by @jherland in #470
|
|
|
|
* CI: call actionlint to check workflow files by @smelc in #485
|
|
|
|
* Add support for *-wildcards in ignore-undeclared and ignore-unused by @jherland in #479
|
|
|
|
* RFC/Follow-up to actionlint CI action by @jherland in #488
|
|
|
|
* Follow-up to #484: Add a --base-dir option by @jherland in #489
|
|
|
|
* CI: run CodeQL by @smelc in #487
|
|
|
|
* CI: call the CodeQL workflow from the main workflow file by @smelc in #491
|
|
|
|
* Fix infinite recursion when --base-dir is not a parent of a source file by @jherland in #492
|
|
|
|
* Update dependencies and bump version to v0.20.0 by @jherland in #493
|
|
|
|
|
- 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.
OBS-URL: https://build.opensuse.org/package/show/devel:languages:python/python-fawltydeps?expand=0&rev=9
2025-07-13 12:16:48 +00:00
|
|
|
-------------------------------------------------------------------
|
|
|
|
Sun Jul 13 12:15:54 UTC 2025 - Dirk Müller <dmueller@suse.com>
|
|
|
|
|
|
|
|
- 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.
|
|
|
|
|
2025-04-01 21:20:57 +00:00
|
|
|
-------------------------------------------------------------------
|
|
|
|
Tue Apr 1 20:03:48 UTC 2025 - Nico Krapp <nico.krapp@suse.com>
|
|
|
|
|
|
|
|
- Update to 0.19.0
|
|
|
|
* Drop Python v3.7 support, upgrade deps, add Python v3.13 support by @jherland in #459
|
|
|
|
* Documentation page: mkdocs & GitHub pages by @mknorps in #449
|
|
|
|
* Add support for PEP 735 dependency groups by @jherland in #469
|
|
|
|
|
2025-08-15 08:32:52 +00:00
|
|
|
-------------------------------------------------------------------
|
|
|
|
Mon Mar 3 08:53:55 UTC 2025 - Felix Stegmeier <felix.stegmeier@suse.com>
|
|
|
|
|
|
|
|
- update to 0.19.0
|
|
|
|
* Drop Python v3.7 support, upgrade deps, add Python v3.13 support by @jherland in #459
|
|
|
|
* Documentation page: mkdocs & GitHub pages by @mknorps in #449
|
|
|
|
* Add support for PEP 735 dependency groups by @jherland in #469
|
|
|
|
|
|
|
|
|
2025-02-10 14:00:51 +00:00
|
|
|
-------------------------------------------------------------------
|
|
|
|
Mon Feb 10 14:00:42 UTC 2025 - Dirk Müller <dmueller@suse.com>
|
|
|
|
|
|
|
|
- spec-cleaner run
|
2025-02-10 14:43:52 +00:00
|
|
|
- switch to poetry-core
|
2025-02-10 14:00:51 +00:00
|
|
|
|
2025-02-10 13:52:30 +00:00
|
|
|
-------------------------------------------------------------------
|
|
|
|
Fri Feb 7 14:19:50 UTC 2025 - Nico Krapp <nico.krapp@suse.com>
|
|
|
|
|
|
|
|
- initial packaging v0.18.0
|