ansys / ansys/actions

License checker is not doing the right thing

Closed
#1,066 0 comments 0 reactions 0 assignees View on GitHub
bug
Dominant language
Python
Stars
19
Forks
7
Avg merge
2d 9h
Merged PRs (30d)
70

Description

### 🔍 Before submitting the issue

- [x] I have searched among the existing issues
- [x] I am using a Python virtual environment

### 🐞 Description of the bug

License checker should be checking the packages installed on a customer's machine, not pinned development only dependencies, unless the license terms of those packages specifically prohibit commercial use etc.

In the case of PyMaterials Manager the action is complaining about several dependencies being LGPL and friends, for example astroid which is a transitive dependency of sphinx-automodapi. This is used only to generate the documentation, and is not installed on a customer's environment.

Simply checking the lock file, or the environment when poetry install has been used is not the way to determine license compliance, realistically for locked environments we ought to install only the project, excluding any extras or other groups before running the reporting tool.

### 📝 Steps to reproduce

https://github.com/ansys/pymaterials-manager/actions/runs/19696138640/job/56421521678

### 💻 Which operating system are you using?

Linux

### 📀 Which ANSYS version are you using?

_No response_

### 🐍 Which Python version are you using?

3.12

### 📦 Installed packages

```shell
n/a
```

Contributor guide

Open the contributing guide

Research direction

Start with the linked GitHub Actions run and trace how the license checker determines which packages to report when Poetry is used. Compare its package selection with the project's runtime dependencies, excluding development-only, extras, and other groups where appropriate. Done means the report reflects packages installed for the project rather than documentation-only dependencies such as astroid.

Written by the indexing model from the issue text.

Assessment

Tech stack
github-actions, python
Domain
ci-cd, devops
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.