Torf

Latest version: v4.2.6

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

Scan your dependencies

Page 2 of 10

4.2.3

- Torrent.calculate_piece_size() now returns 16 MiB for content sizes bigger
than 16 GiB. (Thanks cannibalChipper)

4.2.2

- Fix a bug that was introduced in 4.2.0. Instead of forcibly decoding all
encodings as UTF-8, go back to defaulting to undecoded bytes (like before)
and only perform a decode-and-replace-invalid-characters routine on known
strings like ["info"]["name"].

4.2.1

- Setting Torrent.piece_size_min/max now also sets Torrent.piece_size if it is
too small/big.

4.2.0

- When reading torrent files, strings are now always decoded as UTF-8 (except
for ["info"]["pieces"]). This makes it harder to store binary data in
non-standard fields, but it also means ["info"]["name"] is always a unicode
string.
- Allow any "piece length" that is divisible by 16 KiB.
Previously, power of 2 was required.

4.1.4

- Fix "Too many open files" error when creating a torrent with loads of small
files.

4.1.3

- Try to reduce memory usage before being out of memory.
- Terminate piece hashing threads if they are idle for more than
500 milliseconds.

Page 2 of 10

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.