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

Bump pyasn1 from 0.4.2 to 0.4.8 #98

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

dependabot-preview[bot]
Copy link

Bumps pyasn1 from 0.4.2 to 0.4.8.

Release notes

Sourced from pyasn1's releases.

Release 0.4.8

This is a minor feature release:

  • Added ability to combine SingleValueConstraint and PermittedAlphabetConstraint objects into one for proper modeling FROM ... EXCEPT ... ASN.1 clause.

Release 0.4.7

The major feature of this release is SET ... WITH COMPONENTS constraint support.

  • Added WithComponentsConstraint along with related
    ComponentPresentConstraint and ComponentAbsentConstraint classes
    to be used with Sequence/Set types representing
    SET ... WITH COMPONENTS ... like ASN.1 constructs.

The other important change is that sizeSpec attribute of ASN.1 objects is now deprecated
in favor of uniform subtypeSpec, which is now used for all constraints.

  • Deprecate subtypeSpec attributes and keyword argument. It is now
    recommended to pass ValueSizeConstraint, as well as all other constraints,
    to subtypeSpec.
  • Added isInconsistent property to all constructed types. This property
    conceptually replaces verifySizeSpec method to serve a more general
    purpose e.g. ensuring all required fields are in a good shape. By default
    this check invokes subtype constraints verification and is run by codecs
    on value de/serialisation.

In the bug fixes department we have just one fix:

  • Fixed a design bug in a way of how the items assigned to constructed
    types are verified. Now if Asn1Type-based object is assigned, its
    compatibility is verified based on having all tags and constraint
    objects as the type in field definition. When a bare Python value is
    assigned, then field type object is cloned and initialized with the
    bare value (constraints verificaton would run at this moment).

Complete list of changes can be found in CHANGELOG.

Release 0.4.6

This release brings support for one overlooked ASN.1 feature:

  • Added previously missing SET OF ANY construct encoding/decoding support.

As a consequence, SequenceOf/SetOf objects behavior has been made closer to Python list and more consistent with the rest of pyasn1 types (at the expense of potential backward compatibility issues):

  • New elements to SequenceOf/SetOf objects can now be added at any
    position - the requirement for the new elements to reside at the end
    of the existing ones (i.e. s[len(s)] = 123) is removed.
  • List-like slicing support added to SequenceOf/SetOf objects.
  • Removed default initializer from SequenceOf/SetOf types to ensure
... (truncated)
Changelog

Sourced from pyasn1's changelog.

Revision 0.4.8, released 16-11-2019

  • Added ability of combining SingleValueConstraint and PermittedAlphabetConstraint objects into one for proper modeling FROM ... EXCEPT ... ASN.1 clause.

Revision 0.4.7, released 01-09-2019

  • Added isInconsistent property to all constructed types. This property conceptually replaces verifySizeSpec method to serve a more general purpose e.g. ensuring all required fields are in a good shape. By default this check invokes subtype constraints verification and is run by codecs on value de/serialisation.
  • Deprecate subtypeSpec attributes and keyword argument. It is now recommended to pass ValueSizeConstraint, as well as all other constraints, to subtypeSpec.
  • Fixed a design bug in a way of how the items assigned to constructed types are verified. Now if Asn1Type-based object is assigned, its compatibility is verified based on having all tags and constraint objects as the type in field definition. When a bare Python value is assigned, then field type object is cloned and initialized with the bare value (constraints verificaton would run at this moment).
  • Added WithComponentsConstraint along with related ComponentPresentConstraint and ComponentAbsentConstraint classes to be used with Sequence/Set types representing SET ... WITH COMPONENTS ... like ASN.1 constructs.

Revision 0.4.6, released 31-07-2019

  • Added previously missing SET OF ANY construct encoding/decoding support.
  • Added omitEmptyOptionals option which is respected by Sequence and Set encoders. When omitEmptyOptionals is set to True, empty initialized optional components are not encoded. Default is False.
  • New elements to SequenceOf/SetOf objects can now be added at any position - the requirement for the new elements to reside at the end of the existing ones (i.e. s[len(s)] = 123) is removed.
  • List-like slicing support added to SequenceOf/SetOf objects.
  • Removed default initializer from SequenceOf/SetOf types to ensure consistent behaviour with the rest of ASN.1 types. Before this change, SequenceOf/SetOf instances immediately become value objects behaving like an empty list. With this change, SequenceOf/SetOf objects remain schema objects unless a component is added or .clear() is called. This change can potentially cause incompatibilities with existing pyasn1 objects which assume SequenceOf/SetOf instances are value objects right upon instantiation. The behaviour of Sequence/Set types depends on the componentType initializer: if on componentType is given, the behaviour is the same as SequenceOf/SetOf have. IF componentType is given, but neither optional nor defaulted components are present, the created instance remains schema object, If, however, either optional or defaulted component isi present, the created instance immediately becomes a value object.
  • Added .reset() method to all constructed types to turn value object into a schema object.
  • Added PyAsn1UnicodeDecodeError/PyAsn1UnicodeDecodeError exceptions to help the caller treating unicode errors happening internally to pyasn1 at the upper layers.
  • Added support for subseconds CER/DER encoding edge cases in GeneralizedTime codec.
  • Fixed 3-digit fractional seconds value CER/DER encoding of GeneralizedTime.
  • Fixed AnyDecoder to accept possible TagMap as asn1Spec to make dumping raw value operational

Revision 0.4.5, released 29-12-2018

  • Debug logging refactored for more efficiency when disabled and for more functionality when in use. Specifically, the global LOG object can easily be used from any function/method, not just from codec main loop as it used to be.
  • More debug logging added to BER family of codecs to ease encoding problems troubleshooting.
  • Copyright notice extended to the year 2019
  • Fixed defaulted constructed SEQUENCE component initialization.

Revision 0.4.4, released 26-07-2018

  • Fixed native encoder type map to include all ASN.1 types rather than just ambiguous ones
  • Fixed crash in .prettyPrint of Sequence and Set occurring at OPTIONAL components

Revision 0.4.3, released 23-05-2018

  • Copyright notice extended to the year 2018
  • Fixed GeneralizedTime.asDateTime to perform milliseconds conversion correctly
Commits
  • 70c1bbd Release 0.4.8
  • c42c23e Allow combining constraints operating on sets (#181)
  • 40d5a7f Fix failing OctetString to unicode conversion tests on Py2
  • bac135a Improve open maps debugging in decoder
  • aa5eb55 Prepare for 0.4.8
  • 771aa24 Release 0.4.7
  • 3cae125 Add an afterthought on WITH COMPONENTS constraint
  • d0b7f2e Add SET ... WITH COMPONENTS ... ASN.1 construct support (#171)
  • 7214dca Fix for Python 4 (#173)
  • 41ce2e5 Deprecate sizeSpec in favor of subtypeSpec (#172)
  • Additional commits viewable in compare view

Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
  • @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
  • @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
  • @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
  • @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language
  • @dependabot badge me will comment on this PR with code to add a "Dependabot enabled" badge to your readme

Additionally, you can set the following in your Dependabot dashboard:

  • Update frequency (including time of day and day of week)
  • Pull request limits (per update run and/or open at any time)
  • Automerge options (never/patch/minor, and dev/runtime dependencies)
  • Out-of-range updates (receive only lockfile updates, if desired)
  • Security updates (receive only security updates, if desired)

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

Successfully merging this pull request may close these issues.

0 participants