Fontparts setup.py won't run.
george_thompson
Posts: 32
Mac 10.13.5: I have tried running the setup.py script for Fontparts several times and in different ways (sudo, build, python + build, etc.) and it always fails saying there is no README.rst file even though there is. Any suggestions as to what I am doing wrong?
George
Traceback (most recent call last):
File "/Applications/FontTools/fontParts-master/setup.py", line 138, in <module>
with open('README.rst', 'r') as f:
IOError: [Errno 2] No such file or directory: 'README.rst'
George
Tagged:
0
Comments
-
What is the command that you are running exactly?0
-
George: sounds like you may be running setup.py for release, not install. To install font parts, it's much easier to use pip:
pip install fontparts
This has the advantage of also installing the dependencies for fontParts.
0 -
Thanks, Ben, pip did it except it said defcon[pens] was lacking so I tried pip install --upgrade defcon[pens] but pip said no match so I installed fontPens separately. Hope that works.
George0 -
George, it should. Not sure why it would say defcon[pens] was lacking, but as long as you have fontPens installed, you should be good (pip install fontpens)0
-
I am getting the following message:
Could not fetch URL https://pypi.python.org/simple/fontparts/: There was a problem confirming the ssl certificate: [SSL: TLSV1_ALERT_PROTOCOL_VERSION] tlsv1 alert protocol version (_ssl.c:590) - skipping<br> Could not find a version that satisfies the requirement fontparts (from versions: )<br>No matching distribution found for fontparts<br><br>
0 -
Ramiro — this is an issue with pip, you need to upgrade pip. See https://pip.pypa.io/en/stable/installing/1
-
Everything is now in site-packages under Frameworks/Python, but not in the Python site-packages and FLVI says there is no such module. What's going on?
0 -
George — Ah, I should have asked what you are trying to do. Two issues here:
1. A application needs to write a wrapper for fontParts (unless you are using it on the command line, then the included fontshell works there). FontLab VI —to my knowlege— does not yet have a wrapper for fontParts, however, it includes the older (and now archived) roboFab. You don't need to install anything, it's just there. See the FontLab documentation on this.
2. FLVI, it seems, is pulling from a different python than the one where you installed fontparts. I do not know if it uses the system or if it has it's own python bundled. I also don't know if your system has more than one version of python installed — if so, you may have installed fontParts in one version, and FontLab is pulling from a different. This issue is likely not a problem if you are just wanting to script things in FontLab — until fontParts is added, use roboFab.
Hope that helps.1 -
Ben Kiel said:...however, it includes the older (and now archived) roboFab. You don't need to install anything, it's just there. See the FontLab documentation on this.
roboFab is not included and will not work with FL6, as the current API features only some legacy FL5 commands or tries to "emulate" them, rather unsatisfactory (actually who needs that compatibility anyhow ).2. FLVI, it seems, is pulling from a different python than the one where you installed fontparts. I do not know if it uses the system or if it has it's own python bundled. I also don't know if your system has more than one version of python installed — if so, you may have installed fontParts in one version, and FontLab is pulling from a different. This issue is likely not a problem if you are just wanting to script things in FontLab — until fontParts is added, use roboFab.0 -
For this week's 6.0.7 dot release, we have updated the FontLab VI Python install for so that (1) the user can specify location the first time they install, or just use the existing Windows Python, and (2) on Windows the 32-bit and 64-bit are treated separately, so the user can have both (for FLS 5 and 64-bit FLS VI at the same time).
0 -
FLVI says no module named robofab.world and none of the robofab based scripts will work. Tried importing FL module first, but same result. Will try re-installing robofab, but the scripts quit working earlier this year with FL5.
As for different Python versions I can't find another one. There were some with the old AdobeFDK stuff, but I deleted them a while ago. Python is dated 3-18 while FLVI is 5-18 so I don't think it installed another version unless it hid it under the floorboards.
So how do I go about using Fontparts or should I even bother at this point in time?
Right now I am rewriting some scripts in plain Python, but I would rather be designing type than writing code.
Sorry if I sound obtuse, but I'm a designer and other than learning some Basic in the 2E era and enough Python to cobble some scripts together I'm not a coder.
George0 -
I forgot to say: FL VI only installs its own Python on Windows. Mac OS has its own Python 2.7 which is fine, and FontLab just uses that. On Windows, there is no system Python, and there is the issue of 32-bit vs 64-bit Python.0
-
Boy, so many different ways to not run our Robofab, FontParts or FontLab 5 scripts0
-
George:
Sorry for the slow reply — was on vacation. My mistake on thinking that FLVI had Robofab built in, I misremembered the line “Python (APIs compatible with FontLab Studio and RoboFab)” from the FontLab site. RoboFab works for me in FLVI (simple tests), but that's because I have it installed on my system.
If you type:import sys<br>print(sys.path)<br>
In the scripting pane of FLVI, it'll tell you which python it is pulling from, you can then see if roboFab is installed there. If not, be sure to install it into one of the site-packages folders listed in the output of the above.
To answer your question: for FLVI (currently) you need to use roboFab or the FontLab specific scripting (http://help.fontlab.com/fontlab-vi/Scripting-with-Python/) not FontParts. At some point, hopefully, fontParts will work with FLVI, but this needs FontLab to do the work of incorporating it.
I know that getting roboFab to work is really really frustrating, which is why we've written fontParts — it's easier for applications to incorporate and has mostly the same API as roboFab. It's a rough transition period, but hopefully in the near term, things will be easier for all.
I hope the above helps.
1
Categories
- All Categories
- 43 Introductions
- 3.7K Typeface Design
- 803 Font Technology
- 1K Technique and Theory
- 622 Type Business
- 444 Type Design Critiques
- 542 Type Design Software
- 30 Punchcutting
- 136 Lettering and Calligraphy
- 83 Technique and Theory
- 53 Lettering Critiques
- 485 Typography
- 303 History of Typography
- 114 Education
- 68 Resources
- 499 Announcements
- 80 Events
- 105 Job Postings
- 148 Type Releases
- 165 Miscellaneous News
- 270 About TypeDrawers
- 53 TypeDrawers Announcements
- 116 Suggestions and Bug Reports