Lsseq

Latest version: v4.0.0

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

Scan your dependencies

Page 4 of 4

2.3.1

A bug was introduced sometime after v2.0.24 (see dist - tarballs). This fixes it.

The bug manifested itself if you lsseq -R in the testdir, specifically on the contents of e01_sh0001_globalFX because it had a subdirectory called anim which caused havoc because there is a file extention type "anim" that the code used to handle better before a rewrite (versions since 2.0.24) because a simple test got omitted from a new function call.

2.3.0

Added an ability to turn OFF (like --skipMissing for example) ALL per-sequence error-lists in one fell swoop with --noErrorLists. This has been implemented in such a way that if you want to turn one specific list back ON, you can, simply by calling (for example --showBadPadding) AFTER calling --noErrorLists. Also added another flag or two and some flag shortforms to some options.

2.2.2

Some shebangs in my code were referring to python3.6, and discovered that it all works by removing the explicit 3.6, just using 3, then it works on other systems that might be more up-to-date than 3.6. (Eg. my mac which is 3.7)

2.2.1

I combed through all the lsseq code, and simplified and cleaned it up quite a bit.
Added comments and named variable, constants better etc. Moved some logic around to
be much easy to follow the flow. So it's much easier to read and follow the logic now.
Furthermore, I added a feature that will report if a sequence has poorly or malformed padded numbers,
which surprisingly helped in the code simplification overall.
The rule for padding sequences is pretty simple, and rarely is broken by users, but it's very useful to catch in the
cases that it is broken. Also, added some helpful hints in the expandseq and condenseseq commands with
regard to passing negative integers on the command line.
Also added some test cases for the badPadding. More test cases will follow in subsequent updates, but
I'm confident that no new (or very few) new bugs have been introduced.

2.1.0

This code has been regression tested, plus pylint run on it to catch any errors in the
update. This is safe to use to replace any earlier versions of lsseq, expandseq and condenseseq!

Page 4 of 4

© 2025 Safety CLI Cybersecurity Inc. All Rights Reserved.