-
Notifications
You must be signed in to change notification settings - Fork 105
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Splitting out helper scripts as a separate project #1639
Comments
I like this. We should do it so that #1515 is satisfied as well. @chrissimpkins suggested using PEP 420 - Implicit Namespace Packages which is already a python built in. |
We should probably move (b) into https://github.com/googlefonts/tools :) |
Uh, seems like PEP 420 support for python 2.7 is suboptimal pypa/setuptools#406 (comment) |
👍 |
pkgutil-style namespace packages work well in both python 2 and 3 |
Font Bakery from now on will be focused on a sigle purpose: a Quality-Assurance automated testing framework for font families. (issue googlefonts#3 and fonttools/fontbakery#1639)
Font Bakery from now on will be focused on a sigle purpose: a Quality-Assurance automated testing framework for font families. (issue googlefonts#3 and fonttools/fontbakery#1639)
Font Bakery from now on will be focused on a sigle purpose: a Quality-Assurance automated testing framework for font families. (issue #3 and fonttools/fontbakery#1639)
You decide to transition all QA tools to the tools repo? |
yes. It is all there and it is also already available as a pip package since this weekend when I made a first release of gftools. Install it with:
and use it just like you used fontbakery (with the subcommands and so on...) |
Thanks for the link Felipe! |
you're welcome! I'll also add that info to the README and to the CHANGELOG ! |
...auxiliary scripts into a separate python package called gftools (which stands for Google Fonts Tools) and is available at http://pypi.python.org/gftools and https://github.com/googlefonts/tools/ (issue fonttools#1639)
...auxiliary scripts into a separate python package called gftools (which stands for Google Fonts Tools) and is available at http://pypi.python.org/gftools and https://github.com/googlefonts/tools/ (issue #1639)
done! |
Congrats! This is a pretty big change so I suggest to tag and release 0.3.3 soon (like this week) I moved stuff from 0.3.3 to 0.3.4 - does https://github.com/googlefonts/fontbakery/milestone/61 look doable this week? |
I would like to consider and discuss here the idea of eventually splitting fontbakery into 2 separate python packages:
bin/
directory. A whole bunch of tiny tools for inspecting and hotfixing font files.The rationale to that proposal relates to a common complain about the difficulty to install fontbakery on a system due to its large number of dependencies. The testsuite portion of the code still requires a lot of dependencies, but there are things that are really only needed on the scripts.
It seems to me that a fontbakery-scripts package could pretty easily list fontbakery as a dependency in its setup.py so that it would be doable to install everything by simply performing a pip install fontbakery-scripts, but users who only need to run the testsuite can skip installing the scripts and their extra dependencies.
A second reason is simply the fact that right now the project tries to accomplish 2 fairly separate purposes: (a) QA automated reports and (b) code snippets for font inspection & hotfixing.
The text was updated successfully, but these errors were encountered: