Skip to content

Conversation

xavierfigueroav
Copy link
Collaborator

Make use of the license-expression library to parse complex license expressions in SPDX documents.
Signed-off-by: Xavier Figueroa xavierfigueroav@gmail.com

Fixed typo: 'redundent' -> 'redundant'
@pombredanne
Copy link
Member

@xavierfigueroav ping.... do you thing this could be rebased?

Signed-off-by: Xavier Figueroa <xavierfigueroav@gmail.com>
Signed-off-by: Xavier Figueroa <xavierfigueroav@gmail.com>
@xavierfigueroav
Copy link
Collaborator Author

@xavierfigueroav ping.... do you thing this could be rebased?

Hi, PhiIippe :) I've rebased the code.

SantiagoTorres and others added 23 commits March 30, 2020 18:25
The existing example for write_tv requires a couple of fields in the
Document, Package and File objects that are not defined. This causes the
example to fail, which makes its goal of being a reference for current
implementors
The current version of the example fails with "Document is Invalid"
errors, which makes it rather hard to understand what is invalid about
the document. Further, the  exception caught itself presents is already
floating information about which checks specifically made the document
invalid. Present this information to the user in such a way that they
can identify and fix the errors in their document
Signed-off-by: Shubham Kumar Jha <skjha832@gmail.com>
Signed-off-by: Shubham Kumar Jha <skjha832@gmail.com>
Fixes the install error in Python 2.7 and CircleCI error with Python 3.4.8
Previously, there was an extra '>' in line 42 which was the reason this rdf/xml file was showing error. Now, the file is validated.

Signed-off-by: Yash Varshney <b18038@students.iitmandi.ac.in>
…sh Varshney as a part of CommunityBridgeMentorship Programme. The main feature introduce is the CLI-tool for python parser and convertor. Apart from this, Relationship Class is added in python tool, all the other classes have been updated wrt to v2.2 of spdx specs (some issues have also been raised), attribution text has been added to file,package and snippet class as well. BLACK is used for formatting the whole tool.

Signed-off-by: Yash Varshney <b18038@students.iitmandi.ac.in>
CommunityBridge Project by Yash Varshney
It was deprecated in Python 3.1 and removed in Python 3.9.
Fix typo

Merging after all. A one character change is not material

Signed-off-by: Philippe Ombredanne <pombredanne@nexb.com>
Click dropped support for all 2.x versions and all 3.5 or earlier
versions of Python.  So, in order to support those versions, we
must tie the click version to click 7.x.

Since we're still actively testing these older Python versions
in CI, this should fix a number of issues in CI.

Fixes spdx#161.

Signed-off-by: Jeff Licquia <licquia@linuxfoundation.org>
Fixes spdx#163.

Signed-off-by: Jeff Licquia <licquia@linuxfoundation.org>
Signed-off-by: Jeff Licquia <licquia@linuxfoundation.org>
Signed-off-by: Jeff Licquia <licquia@linuxfoundation.org>
Signed-off-by: Jeff Licquia <licquia@linuxfoundation.org>
Fixes spdx#165.

Signed-off-by: Jeff Licquia <licquia@linuxfoundation.org>
Do not test old Pythons in CI 

Signed-off-by: Philippe Ombredanne <pombredanne@nexb.com>
test_jsonyamlxml_parser: remove deprecated json.load encoding argument

Signed-off-by: Philippe Ombredanne <pombredanne@nexb.com>
pombredanne and others added 20 commits June 5, 2021 12:02
Update CircleCI xcode version to a supported one.

Signed-off-by: Philippe Ombredanne <pombredanne@nexb.com>
Signed-off-by: Philippe Ombredanne <pombredanne@nexb.com>
Drop Python 2.7 and 32-bit testing on Appveyor.
Use instead Python 3.6 to 3.9

Signed-off-by: Philippe Ombredanne <pombredanne@nexb.com>
Signed-off-by: Jeff Licquia <licquia@linuxfoundation.org>
Signed-off-by: Jeff Licquia <licquia@linuxfoundation.org>
Signed-off-by: Jeff Licquia <licquia@linuxfoundation.org>
Support multiple packages per SPDX document.

This set of patches adds support for multiple packages per document, by adding document.packages as an array. The API for managing multiple packages is set up to mimic the other APIs for managing multiple objects (files, external licenses, etc.).

To preserve backwards compatibility, this patch introduces document.package as a property; this property is implemented using document.packages behind the scenes, and triggers a DeprecationWarning.

Support is included for parsing documents with multiple packages, as well as writing such documents.

Fixes spdx#79.

Signed-off-by: Philippe Ombredanne <pombredanne@nexb.com>
Signed-off-by: alpianon <alberto@pianon.eu>
Signed-off-by: alpianon <alberto@pianon.eu>
Signed-off-by: alpianon <alberto@pianon.eu>
Signed-off-by: alpianon <alberto@pianon.eu>
Signed-off-by: Philippe Ombredanne <pombredanne@nexb.com>

Co-authored-by: alpianon <alberto@pianon.eu>
Signed-off-by: alpianon <alberto@pianon.eu>
spdx#133

Signed-off-by: Philippe Ombredanne <pombredanne@nexb.com>
spdx#111

Signed-off-by: Philippe Ombredanne <pombredanne@gmail.com>
spdx#111

Signed-off-by: Philippe Ombredanne <pombredanne@nexb.com>
@pombredanne
Copy link
Member

I am keeping this around as this will eventually be merged.

@armintaenzertng
Copy link
Collaborator

armintaenzertng commented Oct 20, 2022

@pombredanne, is this still valid? Do you know when the "eventually" you mentioned might be?

As this PR is quite massive, it will cause a lot of conflicts in the future.

@pombredanne
Copy link
Member

@armintaenzertng your call. Parsing expression is a must have IMHO.

@armintaenzertng
Copy link
Collaborator

I'd like to see a rebase of this PR to get a better sense of what actually changed as the multiple merge commits make this rather incomprehensible.

@xavierfigueroav, are you willing to do this? Else I'll gladly take over from here :)

@nicoweidner
Copy link
Collaborator

Looking at the size, age and type of changes in this PR, I think the only viable course of action is to start from scratch based on current main and potentially use similar logic as in this PR (I didn't actually see the implementation details at first glance, since they are drowned in a sea of formatting changes...).

I will wait for a few days to see if anyone disagrees, then close this. The corresponding issue is #10

@nicoweidner
Copy link
Collaborator

Closing this as announced earlier.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.