vpype 1.12 is out! 🎉
No ground-breaking features, but an improved “quality-of-life”, especially for Apple-silicon Mac owners, and few other goodies.
Let’s dive in.
Migration to PySide6
- Migrated to PySide6 (from PySide2), which simplifies installation on Apple silicon Macs (#552, #559, #567)
PySide2 is the official Python wrapper for Qt 5, the GUI toolkit I use for the viewer. As Qt 5 doesn’t officially support Apple-silicon Macs, PySide2 – and thus vpype until now – were notoriously difficult to install on these computers. This is resolved with the transition to PySide6, which wraps Qt 6 and officially supports Apple-silicon Macs.
This took me waaaay too long. I actually feel bad for the struggle incurred to vpype users 😅 All things considered, the migration wasn’t that complicated, but there were still a few pitfalls to figure out due to Qt 6 breaking changes around the OpenGL-based widget.
Migrating to PySide6 is also a major step towards supporting Python 3.11, which brings a host of novelties as well as a significant performance bumps. I’m hoping this will happen by the next release, which means vpype 1.12 might well be the last to support Python 3.8.
Other fixes and improvements
layoutcommand now properly handles the
tightspecial case by fitting the page size around the existing geometries, accommodating for a margin if provided (#556)
- Fixed a viewer issue where page width/height of 0 would lead to errors and a blank display (#555)
layout tight would formerly set the page size to 0 by 0, which is useless in itself and caused a blank display. Not only the blanking issue has been resolved, but
layout tight is now actually useful. It sets the page size to fit exactly the current geometries, accounting for a margin if
--fit-to-margin MARGIN is provided.
inchunit as a synonym to
in, useful for expressions (in which
inis a reserved keyword) (#541)
This addresses an oversight introduced with expressions in vpype 1.9. The units available for length CLI options are also available as scaling factor in expressions. For example, this creates a 10x15 cm rectangle:
vpype rect 0 0 10cm '%15*cm%' show
The expression works because the
cm variable is made available by the interpreter, and set to the conversion factor between centimetres and pixels. This would however break for inches, because
in is a reserved keyword in Python. The variable
inch is now available instead. Either form can be used in CLI options, but
inch must be used in expressions:
vpype circle 5in 5inch '%3*inch%' show
- Fixed a viewer issue where fitting the view to the document would not adjust when page size changes (vsketch only) (#564)
This change doesn’t directly benefits vpype as the page size cannot change while the viewer is active. In vsketch, however, the sketch code is free to set/change the page size based on GUI parameters, like in the included
quick_draw example. In this case, when the view is fitted to the page size (i.e. as long as you don’t zoom or scroll), the view will adjust when the page size changes.
- Updated svgelements to 1.8.4, which fixes issue with some SVG constructs used by Matplotlib exports (#549)
Supporting all of the SVG standard subtleties is hard. Not only svgelements does a great job at it, but @tatarize’s reactivity when edge cases appear is unmatched. In this instance, Drawingbots' Discord user apur wanted to plot Matplotlib-generated SVGs of LaTeX equations. They included unusual
<use> elements, which didn’t import properly. This is now fixed and I eagerly await the next niche corner case! 🤗
Plausible is a privacy-focused, GDPR-compliant web statistics service. As I did for this site, I migrated from Google Analytics with my projects' documentation web sites. This is a paid service, so that neither your or I are the product.
- Added new units (
vpype.format_length()to convert pixel length into human-readable string with units (#541)
Yes, vpype supports kilometer-scale plots!1
Seriously though, these changes are part of the WIP improvements of vpype’s terminal output. This will happen in future versions, but for some reason it was easier to integrate those change early.
- Poetry 1.2 or later is not required (developer only) (#541)
justfileis now provided for most common operations (install, build the documentation, etc.) (#541)
plotter not included ↩︎