Releases: justinfx/fileseq
Release v1.13.0
New in v1.13.0
- [#104] Added
to_dict()
method andfrom_dict()
classmethod toFileSequence
to expand support for custom serialization beyond just pickle format (just as json)
Patch release v1.12.3
New in patch release v1.12.3
- Further updates to
FileSequence
py2 str/unicode support, and py3 bytes/str support (#100)
Patch release v1.12.2
New in release v1.12.2
- Fix python2 handling of unicode strings in
FileSequence
__str__()
,__repr__()
, and__format__()
methods (adds__unicode__()
method) (#99)
v1.12.1 Release
New in release v1.12.1
Duplicate release of v1.12.0 for pypi deployment
v1.12.0 Release
New in release v1.12.0
Patch release v1.11.3
New in patch release v1.11.3
- Update
FrameSet
constructor to raiseParseException
on non-numeric args (#92)
Patch release v1.11.2
New in patch release v1.11.2
- Fix regression of undocumented matching of file sequence from absolute
file path infindSequenceOnDisk
(#89) - Add allow_subframes argument, defaulting to False, to preserve previous
behaviour where patterns not including padding characters worked even though
not documented - this prevents accidentally matching subframe filenames if no
padding is provided (#89) - Ensure yield_sequences_in_list correctly yields subframe sequences for
findSequenceOnDisk (do not overwrite frame variable) (#89)
Patch release v1.11.1
Release v1.11.0
This release introduces support for subframe sequences.
Subframes: 1001-1066x0.25, 1001.5-1066.0x0.5
At the FileSequence
level, subframe support is opt-in via the constructor allow_subframes=True
and also in related findSequence*
functions. The expectation is that existing sequence and frameset behaviour should not change.
Release v1.10.0
In this release there is a change to what is perceived to be a bug in the padding width of negative frames (#80) being padded one character wider than they should, making them unbalanced with the positive frame widths, and also does not align with other systems like Nuke. One possible impact to be aware of is if a sequence with negative frames were written out with a previous version of fileseq (with the wider negative frame padding) and then that same sequence pattern were used to iterate the files in this new release, the file paths may not match the negative frames.