Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Upgrade spdx-tools to version 0.8 #3455

Closed
1 of 7 tasks
armintaenzertng opened this issue Jul 17, 2023 · 1 comment · Fixed by #3456
Closed
1 of 7 tasks

Upgrade spdx-tools to version 0.8 #3455

armintaenzertng opened this issue Jul 17, 2023 · 1 comment · Fixed by #3456

Comments

@armintaenzertng
Copy link
Contributor

Short Description

Upgrade spdx-tools to v0.8

Possible Labels

  • dependencies

Select Category

  • Enhancement
  • Add License/Copyright
  • Scan Feature
  • Packaging
  • Documentation
  • Expand Support
  • Other

Describe the Update

Update the spdx-tools dependency from 0.7.0rc0 to 0.8.0rc2 or later.

How This Feature will help you/your organization

The new 0.8 version of the spdx-tools lays the groundwork for the upcoming SPDX-3.0 implementation in python. We therefore expect broad adoption of the 0.8 version.
Tools that use the 0.8 version of the spdx-tools currently can't simultaneously use scancode which depends on the 0.7 version (there can't be two different versions of the same library in a single environment).
This issue currently blocks adoption of the spdx-tools in tern, for example.

Example/Links if Any

Pending PR in tern that introduces spdx-tools in version 0.8: tern-tools/tern#1233

Can you help with this Feature

I will open a PR that takes care of the upgrade while preserving the current feature set.

@priv-kweihmann
Copy link
Contributor

FYI: release of 0.80 is out since last week - no need to upgrade to a rc

pombredanne added a commit that referenced this issue Oct 13, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants