Bump edtf from 4.0.1 to 5.0.0

[dependabot]

Bumps edtf from 4.0.1 to 5.0.0.

Changelog

Sourced from edtf's changelog.

5.0.0 (2023-10-04)

• Breaking Changes: Implementation of the newer specifications from https://www.loc.gov/standards/datetime/::

  Differences This specification differs from the earlier draft as follows:

  • the unspecified date character (formerly lower case ‘u’) is superseded by the character (upper case) 'X';
  • Masked precision is eliminated;
  • the uncertain and approximate qualifiers, '?' and '~', when applied together, are combined into a single qualifier character '%';
  • “qualification from the left” is introduced and replaces the grouping mechanism using parentheses;
  • the extended interval syntax keywords 'unknown' and 'open' have been replaced with null and the double-dot notation ['..'] respectively;
  • the year prefix 'y' and the exponential indicator 'e', both previously lowercase, are now 'Y' and 'E' (uppercase); and
  • the significant digit indicator 'p' is now 'S' (uppercase).

• Renaming of the project to edtf2: As this project seems to have no longer support from the creator The Interaction Consortium we decided to fork it and release it under a new name by our own

• Author: https://github.com/muellersSAW

4.0 (2018-05-31)

• Remove 1 AD - 9999 AD restriction on date ranges imposed by Python's datetime module (#26).

  WARNING: This involves a breaking API change where the following methods return a time.struct_time object instead of datetime.date or datetime.datetime objects::

  lower_strict()
  upper_strict()
  lower_fuzzy()
  upper_fuzzy()
  

• Add jdutil library code by Matt Davis at https://gist.github.com/jiffyclub/1294443_ to convert dates to numerical float representations.

• Update EDTFField to store derived upper/lower strict/fuzzy date values as numerical values to Django's FloatField fields, when available, to permit storage of arbitrary date/time values.

  The older approach where DateField fields are used instead is still supported but not recommended, since this usage will break for date/time values outside the range 1 AD to 9999 AD.

3.0 (2018-02-13)

... (truncated)

Commits

• See full diff in compare view

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 show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @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]

Looks like edtf is no longer a dependency, so this is no longer needed.