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.

Sign up for GitHub

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

Jump to bottom

[BREAKING] Adopt PEP-3102 #143

Closed
madpah opened this issue Jan 24, 2022 · 1 comment · Fixed by #148
Closed

[BREAKING] Adopt PEP-3102 #143

madpah opened this issue Jan 24, 2022 · 1 comment · Fixed by #148
Assignees
@jkowalleck @madpah
Labels
breaking change enhancement New feature or request
Milestone
2.0.0

Comments

@madpah
Copy link
Collaborator

madpah commented Jan 24, 2022

Created from:
@madpah madpah mentioned this issue Jan 24, 2022
Merged
@madpah
Copy link
Collaborator Author

madpah commented Feb 3, 2022 •
edited
Loading

The answer is Yes.

Adopting PEP-3102 will allow us to reduce the number of breaking changes as we build out the library's models and other functions.

@madpah madpah added this to the 1.4.0 milestone Feb 3, 2022
@madpah madpah added breaking change enhancement New feature or request labels Feb 3, 2022
@madpah madpah changed the title [QUESTION] Should PEP-3102 be utilised? [BREAKING] Should PEP-3102 be utilised? Feb 3, 2022
@madpah madpah changed the title [BREAKING] Should PEP-3102 be utilised? [BREAKING] Adopt PEP-3102 Feb 3, 2022
This was referenced Feb 3, 2022
Merged
Merged
@madpah madpah linked a pull request Feb 3, 2022 that will close this issue
RELEASE 2.0.0 #148
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@jkowalleck jkowalleck

@madpah madpah

Labels
breaking change enhancement New feature or request
Projects
None yet
Milestone
2.0.0
Development

Successfully merging a pull request may close this issue.

RELEASE 2.0.0 CycloneDX/cyclonedx-python-lib
2 participants
@jkowalleck @madpah