What happened?
The built packages do not contain LICENSE or LICENSE-CODE in them like the existing package does. However, it is at least correctly tagged based on the classifiers
What did you expect to happen?
LICENSE and LICENSE-CODE should be included and License-Expression should be set on the metadata.
Because the packaging requires the license file to be in the source tree I see two options:
- We include these files in the source tree for each package
- We copy the files to the right location prior to building
While 1 introduces more files into the repo and is a bit noisy I think it is the better solution as 2 would break the from VCS install for pip
How can we reproduce it (as minimally and precisely as possible)?
uv build to see packaged files
AutoGen version
staging
Which package was this bug in
Other
Model used
No response
Python version
No response
Operating system
No response
Any additional info you think would be helpful for fixing this bug
No response
What happened?
The built packages do not contain
LICENSEorLICENSE-CODEin them like the existing package does. However, it is at least correctly tagged based on the classifiersWhat did you expect to happen?
LICENSEandLICENSE-CODEshould be included and License-Expression should be set on the metadata.Because the packaging requires the license file to be in the source tree I see two options:
While 1 introduces more files into the repo and is a bit noisy I think it is the better solution as 2 would break the from VCS install for pip
How can we reproduce it (as minimally and precisely as possible)?
uv buildto see packaged filesAutoGen version
staging
Which package was this bug in
Other
Model used
No response
Python version
No response
Operating system
No response
Any additional info you think would be helpful for fixing this bug
No response