eprints2archives - Release 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.

- Python
Published by mhucka almost 3 years ago

eprints2archives - Release 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.

- Python
Published by mhucka over 3 years ago

eprints2archives - Release 1.3.3

Changes in this release (relative to previous release)

Define console_scripts for setuptools to produce a better wrapper script.
Update all requirement versions to latest versions of packages. This was not done for over a year and it showed...
Add requirement for a certain 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.

New: self-contained binary distributions

This release includes standalone, runnable binaries for macOS and Linux. These experimental binaries were built using shiv. They only need a copy of Python 3.6, 3.7, 3.8 or 3.9 on your system to run – they don't require installation of additional Python packages using (e.g.) pip. They should work on macOS 10.13–11.1, Ubuntu 18+, CentOS 7.5, and probably others. To use them:

Download the zip file for either the Python 3.6, 3.7, 3.8 or the 3.9 version, depending on the version of Python you have installed on your computer. (Use python3 --version to find out the version you have.)
Unzip the resulting file (if your web browser did not automatically unzip it).
Move the file eprints2archives to a location where your terminal shell looks for programs. A popular location is /usr/local/bin.

Thereafter, you should be able to type eprints2archives in your shell and it should run. (If it does not, please report the problem using the issue tracker.) Note that the first time you run it, eprints2archives will take longer than usual to start because it does a one-time configuration step, but on subsequent runs, startup times should be shorter.

- Python
Published by mhucka over 4 years ago

eprints2archives - Release 1.3.2

Changes in this release

Fix a mixhandled exception when a server returns a code 500.
Improve catching interrupts on Windows.
Use CommonPy network utilities, file utilities, and data utilities instead of internal copies.
Use 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.

New: self-contained binary distributions

This release includes standalone, runnable binaries for macOS. These experimental binaries were built using shiv. They only need a copy of Python 3.7, 3.8 or 3.9 on your system to run – they don't require installation of additional Python packages using (e.g.) pip. They should work on macOS 10.13–11.1. To use them:

Download the zip file for either the Python 3.7, 3.8 or the 3.9 version, depending on the version of Python you have installed on your computer
Unzip the resulting file (if your web browser did not automatically unzip it)
Move the file eprints2archives to a location where your terminal shell looks for programs. A popular location is /usr/local/bin.

Thereafter, you should be able to type eprints2archives in your shell and it should run. (If it does not, please report the problem using the issue tracker.) Note that the first time you run it, eprints2archives will take longer than usual to start because it does a one-time configuration step, but on subsequent runs, startup times should be shorter.

- Python
Published by mhucka over 4 years ago

eprints2archives - Release 1.3.1

This version has no functional or user-interface changes. It brings only some minor documentation updates to README.md and the following internal changes:

Use 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.

The file CHANGES contains a more complete change log that includes information about previous releases.