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

Remove upper version bounds #755

Merged
merged 1 commit into from
May 7, 2022
Merged

Conversation

pombredanne
Copy link
Contributor

Using an upper bound for dependency versions on a library is a source of troubles for users.
Let's not do it as it makes pdfminer wreck havoc downstream.

@pietermarsman you introduced this in this recent commit 1bf3c42#diff-60f61ab7a8d1910d86d9fda2261620314edcae5894d5aaa236b821c7256badd7R20

Because of this change, I cannot upgrade to the latest pdfminer short of downgrading cryptography which is a security risk and not an issue for pdfminer proper.

For a longer and comprehensive exploration of the issue, please read this excellent article https://iscinumpy.dev/post/bound-version-constraints/ by @henryiii

Signed-off-by: Philippe Ombredanne pombredanne@nexb.com

Pull request

Please remove this paragraph and replace it with a description of your PR.
Also include links to the issues that it fixes.

How Has This Been Tested?

Please repalce this paragraph with a description of how this PR has been
tested. Include the necessary instructions and files such that other can
reproduce it.

Checklist

  • I have formatted my code with black.
  • I have added tests that prove my fix is effective or that my feature
    works
  • I have added docstrings to newly created methods and classes
  • I have optimized the code at least one time after creating the initial
    version
  • I have updated the README.md or verified that this
    is not necessary
  • I have updated the readthedocs documentation or
    verified that this is not necessary
  • I have added a concise human-readable description of the change to
    CHANGELOG.md

Using an upper bound for dependency versions on a library
is a source of troubles for users.
Let's not do it as it makes pdfminer wreck havoc downstream.

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

pietermarsman commented May 7, 2022

Thanks for noticing and fixing this issue @pombredanne!

And @henryiii, thanks for writing the excellent article on why version caps in libraries are bad!

@pietermarsman pietermarsman merged commit 7f97e26 into pdfminer:master May 7, 2022
@pombredanne pombredanne deleted the patch-1 branch May 7, 2022 22:03
@eddie-scio
Copy link

Is there a timeline for releasing a version on PyPi (later than 20220506) that includes this change?

pietermarsman added a commit that referenced this pull request May 24, 2022
@pietermarsman
Copy link
Member

Publishing now

Beants added a commit to HiTalentAlgorithms/pdfminer.six that referenced this pull request Aug 5, 2022
* commit '8f52578e85b27831ab8a68a6d86721ea3348a553':
  Run black locally with nox (pdfminer#776)
  Install typing_extensions on Python 3.6 and 3.7 (pdfminer#775)
  Fix `TypeError` by Ignoring null characters in PSBaseParser (pdfminer#768)
  Fix `ValueError` with unencrypted metadata values (Fixes pdfminer#766). (pdfminer#774)
  Fix `TypeError` when getting default width of font (pdfminer#772)
  Deprecate usage of `if __name__ == "__main__"` in scripts that are not documented. Also deprecate usage of scripts that are only there for testing purposes. (pdfminer#756)
  Fix Sphinx warnings and error (pdfminer#760)
  Update CHANGELOG.md for pdfminer#755
  Remove upper version bounds (pdfminer#755)
  Ignore path constructors that do not begin with  m (pdfminer#749)
  Bump version 20220506 & fix small issue with types
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.

3 participants