crates: Fixes and improvements
- Aug 27, 2024
-
-
Antoine Lambert authored
Those extrinsic metadata can be directly fetched by the loader through the crates Web API, plus it contains more metadata fields.
-
Antoine Lambert authored
Instead of having a single crate and its versions info per page, prefer to have up to 1000 crates per page to significantly speedup the listing process.
-
Antoine Lambert authored
Previously, the lister state was recorded regardless if errors occurred when listing crates as the finalize method is called regardless of raised exception during listing. As a consequence some crates could be missed as the incremental listing restarts from the dump date of the last processed crate database. So ensure all crates have been processed by the lister before recording its state.
-
Antoine Lambert authored
packaging.version.parse is dedicated to parse Python package version numbers but crate versions do not necessarily respect Python version number conventions and thus some crate versions cannot be parsed. Prefer to use looseversion.LooseVersion2 instead which in a drop-in replacement for deprecated distutils.version.LooseVersion and enables to parse all kind of version numbers.
-
Antoine Lambert authored
A size limit of 1000000 was not enough to properly process all CSV crates data so bump to a higher value.
-