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
Extractor does not import defcon directly, so strictly speaking defcon is not an install_requires.
However, you can't do anything with it if you don't provide a defcon Font instance, or something that "quacks" like one ;)
Once we get to write some unit tests, we will at least need to add defcon among the test requirements.
Now, I have a few questions:
Does anyone know if the current extractor still works with Robofab RFont instances? If so, is this still a requirement for future versions (I hope not)?
Does extractor work with fontParts, and/or is it supposed to? If so, we need to test against that one too.
Does the current extractor depends on any specific version/revision/branch/commit/whatever of defcon? I'd assume or ensure it works at least with the only defcon version which we can reliably specify as a pip requirement (ie. version 0.2.0)
Extractor does not import
defcon
directly, so strictly speakingdefcon
is not aninstall_requires
.However, you can't do anything with it if you don't provide a defcon
Font
instance, or something that "quacks" like one ;)Once we get to write some unit tests, we will at least need to add
defcon
among the test requirements.Now, I have a few questions:
RFont
instances? If so, is this still a requirement for future versions (I hope not)?fontParts
, and/or is it supposed to? If so, we need to test against that one too./cc @moyogo, @adrientetar, @typesupply, etc. and anybody who has used this more me.
The text was updated successfully, but these errors were encountered: