-
Notifications
You must be signed in to change notification settings - Fork 106
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
Problem with Font awesome on VsCode #33
Comments
I have the same problem, I had installed but I tried it also with fontawesomefree 6.2.1. For changing the version, I followed the instructions on the website. I executed this in a Jupyter Notebook in VSCode with python 3.10.0. |
Hi @MalikQasimAli and @Langhammer , could you share more info other than versions of matplotlib, fontawesomefree and pywaffle, like VS code version and platform? I am still not able to reproduce this issue with versions same as Langhammer mentioned above. Python 3.10.0, matplotlib 3.6.3, fontawesomefree 6.3.0, and pywaffle 1.1.0 in VS Code notebook. |
I am having exactly the same problem. I asked a question on StackOverflow and another user redirected me here. Below is some information about the modules I am using: Name: pywaffle Version: 1.1.0 Summary: PyWaffle is an open source, MIT-licensed Python package for plotting waffle charts. Home-page: https://github.com/gyli/PyWaffle Author: Guangyang Li Author-email: [email protected] License: MIT Location: C:\Users\harry\AppData\Roaming\Python\Python311\site-packages Requires: fontawesomefree, matplotlib Required-by: --- Name: fontawesomefree Version: 6.1.1 Summary: Font Awesome Free Home-page: https://github.com/FortAwesome/Font-Awesome Author: Font Awesome Author-email: [email protected] License: UNKNOWN Location: C:\Users\harry\AppData\Roaming\Python\Python311\site-packages Requires: Required-by: pywaffle --- Name: matplotlib Version: 3.7.0 Summary: Python plotting package Home-page: https://matplotlib.org Author: John D. Hunter, Michael Droettboom Author-email: [email protected] License: PSF Location: C:\Users\harry\AppData\Roaming\Python\Python311\site-packages Requires: contourpy, cycler, fonttools, kiwisolver, numpy, packaging, pillow, pyparsing, python-dateutil Required-by: ipympl, pywaffle I attempted to uninstall the matplotlib-3.7.0 and reinstall matplotlib-3.5.2 to see if it would work for me as well, but it raised a legacy-install-failure (see the log below for details). So, does this mean that there is a compatibility issue between versions of matplotlib after 3.5.2 and pywaffle-1.1.0? EDIT: For clarification, it does not make a difference whether I run a Python script through PowerShell, run a JupyterNotebook in the browser or a JupyterNotebook through Visual Studio Code; I get the same problem. |
I run a jupyter notebook in vscode 1.75.1. Interestingly, it works on binder with the same requirements.txt. from matplotlib import pyplot as plt
from pywaffle import Waffle
fig = plt.figure(
FigureClass=Waffle,
rows=1,
icons='person',
font_size=3,
values={'a':1, 'b':2, 'c':3}
) |
Based on @jhncls's finding, we can basically narrow root cause down to rendering font awesome in matplotlib. I also guess that it only happens on Windows, since that is all the cases reported above, and I am not able to reproduce it with 2 mac that I own. His testing codes
outputs the correct result on my end. So could you submit this issue on matplotlib repo? |
@gyli Yes, it seems to be a problem with matplotlib on windows. |
Did anyone ever fix this? |
I have a strange problem with the PyWaffle library. I am running the examples and everything is working fine except the examples with fontawesome.
I am running the following code and the result shows distorted picture.
I am also having the the following warning message : IPython\core\pylabtools.py:151: UserWarning: Tight layout not applied. The bottom and top margins cannot be made large enough to accommodate all axes decorations.
fig.canvas.print_figure(bytes_io, **kw)
I also tried to use the command fig.set_tight_layout(False)
but the warning message did not go away.
The text was updated successfully, but these errors were encountered: