Skip to content
This repository has been archived by the owner on Jan 28, 2025. It is now read-only.

Script resilience to version updates #3

Open
alix-dumoulin opened this issue Jun 12, 2020 · 0 comments
Open

Script resilience to version updates #3

alix-dumoulin opened this issue Jun 12, 2020 · 0 comments

Comments

@alix-dumoulin
Copy link
Contributor

alix-dumoulin commented Jun 12, 2020

TLDR: some scripts found on GitHub / StackOverflow use deprecated methods/functions/libraries

Most common cases so far:

  • Mismatch between script and version installed using pip, can lead to methods not existing, old set of parameters because the function changed, requirements for the package not being installed
  • Script using libraries that are not maintained anymore
  • Scripts importing a module that is not part of the package anymore (or may have a new name?)

Example:
This script which converts pdf to html/XML

  • imports process_pdf() which after some research turns out to have been replaced with PDFPage.get_pages()
  • and has a parameter codec for encoding which is not part of the set of parameters in the new version
  • imports a module plywhich is not in the requirements.txt (therefore not installed via pip)

Why it's a problem

  • Now: makes it a bit painful to get scripts running
  • Later: if we integrate scripts into a product, we need to make sure they are resilient to updates of the packages they use (which is very high-maintenance)
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant