You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi,
just noticed that a test I had failed when upgrading from 4.3.2 to 4.3.3.
When passing use_index=False to mgf.read() with a str filepath the aux._check_use_index() overwrites this back to True. So one always ends up with an IndexedMGF when passing a str filepath and it's no longer possible to create an MGF object. Was wondering if this is an intended change.
Thank you!
The text was updated successfully, but these errors were encountered:
Hi,
just noticed that a test I had failed when upgrading from 4.3.2 to 4.3.3.
When passing
use_index=False
tomgf.read()
with a str filepath theaux._check_use_index()
overwrites this back toTrue
. So one always ends up with anIndexedMGF
when passing a str filepath and it's no longer possible to create anMGF
object. Was wondering if this is an intended change.Thank you!
The text was updated successfully, but these errors were encountered: