Lsseq

Latest version: v3.0.2

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

Scan your dependencies

Page 3 of 4

2.4.3

Release v2.4.3 is only made to properly sync the label with the files in github. v2.4.2 was created but unfortunately all the file changes had not been pushed up. This release fixes that. Check the description of v2.4.2 to see what this release REALLY contains. Apologies.

2.4.2

lsseq didn't gracefully handle the case when a sequence has duplicate frame numbers, eg. two frame 5's, but only different in terms of the padding of the frame number.

This is clearly a problem that the user created by having an extra file (likely unintentional), however when lsseq was attempting to list frames with bad-padding (i.e files that had numbers that didn't match the padding of the sequence), the code wasn't properly accounting for the possibility of two entries with the same frame number in an internal database, and it was causing unintended consequences when trying to come up with the list of badly padded frames. This has been fixed,

NOTE: that this bug ONLY affected the listing of badly padded frames, all other output of lsseq was correct.

Also "warnings" are now issued if/when such duplicate files are found.

Therefore --showBadPadding correctly lists all badly padded frames.

Also added --silent and --quiet also, to suppress printing of warning messages. Previously the only warning printed was if a broken soft link was present.

Furthermore, changed names of three env vars, that the user can use to adjust the list of image-extensions, or cache-extensions etc, from OIC_* to LSSEQ_* - however the code is quiet about it, but still supports the use of the old names for backward compatibility.

2.4.1

The way I used to distribute lsseq, along with seqLister, and some other command-line utils, was out-of-date and began to cause problems for users trying to install on their systems. Errors with seqLister not being accessible, and issues with permissions of user vs root. were being experienced by several people (including me!)

I decided to redo my approach. seqLister is now a separate python-library package, as are the other command-line utils, expandseq and condenseseq.

Furthermore installation should be very easy now, with the packages checked into pypi.org. Follow the installation instructions in the README.md on the home page. Please report problems to me.

2.3.2

Cleaner fix for the bug-fix earlier today in v2.3.1
ALso fixed a bug that would have occurred (but never discovered so far)
in the case that a directory would have been named like a sequence or cache.
Added test cases to the regression test to verify.

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.

Page 3 of 4

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.