Eprints2archives

Latest version: v1.3.5

Safety actively analyzes 681812 Python packages for vulnerabilities to keep your Python projects secure.

Scan your dependencies

Page 1 of 2

1.3.5

Changes in this version:
* Fix bug in definition of `Service` class in `services/base.py`.
* Update some package versions in `requirements.txt`.
* Pin more versions of packages in `requirements.txt`.
* Change name of runnable program to have dash between the name `eprints2archives` and the version number.
* Updated copyright year in file headers and other places.

1.3.4

Changes in this version:
* Fix handling of occasionally unexpected timemap result from InternetArchive.
* Update versions of some dependencies in `requirements.txt`.
* Add of `CITATION.cff` file.

1.3.3

* Add requirement for a package imported by another requirement but that does not, for some reason, get imported properly when a clean virtual environment is created in the process of making pyz apps.
* Update all requirement versions to latest versions of packages. This was not done for over a year and it showed...
* Define `console_scripts` for setuptools to produce a better wrapper script.

1.3.2

* Fix a mixhandled exception when a server returns a code 500.
* Improve catching interrupts on Windows.
* Use [CommonPy](https://github.com/caltechlibrary/commonpy) network utilities, file utilities, and data utilities instead of internal copies.
* Use [Bun](https://github.com/caltechlibrary/bun) user interface code instead of internal copy. Also change some colors of messages printed by `eprints2archives`.
* Update internal imports and some requirements.
* Update copyright year.

1.3.1

* Use [Sidetrack](https://github.com/caltechlibrary/sidetrack) instead of internal `debug.py` version of the same.
* Internally, use different approach to recording version number and other metadata.
* Use updated release procedure codified in `Makefile`.

1.3.0

* Check that URLs obtained from EPrints records appear to be valid URLs, before trying to send them to web archives. (This is mostly to catch bad values in the `official_url` record field.)
* Be more careful about which `/view/X/N.html` pages are sent.
* Do a better job with HTTP code 400 from Internet Archive.
* Do some more internal network code refactoring.
* Add some more debug log statements.

Page 1 of 2

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.