of pythons and turtles

I was exposed to Turtle Graphics in the dim dark early 1980s via Texas Instruments TI99/4A home computer and their implementation of Logo. Logo itself goes back even further, to the late 1960s (for the history of Logo, see https://el.media.mit.edu/logo-foundation/what_is_logo/history.html ). I thought Logo interesting, but after a time it faded into the background as I moved on to other computers and languages. Fast forward to now, where I came across a problem requiring Turtle graphics be used to draw from one to four copies of simple graphics on a Tcl/Tk canvas. My example draws “trees” using heptagons as the “tree” crowns on both macOS 11 and a CentOS 8.3 VM hosted on my Mac. Through solving the problem I was reintroduced to Turtle graphics and I learned about a number of side issues running Python on both MacOS and CentOS. But first, a screen capture of my application running on macOS.

And now, a screen capture from CentOS.

The big difference between the two screen captures is a lack of anti-aliasing on the CentOS version. Why does the Linux version look so bad compared to the macOS version?

Before I go farther, let me post my source code here.

#!/usr/bin/env python3

import math
import turtle
import tkinter as tk

# RegularPolygon, a regular polygon drawer.
# Three or more equal sides.
def RegularPolygon(t, color, x, y, sides, side_length, fill):
    if sides < 3:

    # Shift the turtle starting point so that the center
    # of the polygon is actually at x and y.
    inradius = ((side_length/2) / math.tan(math.pi/sides))
    t.setposition(x + side_length/2, y - inradius)

    if fill:

    turn_angle = 360 / sides

    for x in range(0, sides):

    if fill:


# Draw an abstract tree.
def Tree(t, color, x, y, fill):
    # Draw the trunk.
    # I could, I suppose, write and use a Line function.
    # Too lazy.
    t.setposition(x, y)
    # Draw two branches at 45 degrees from the trunk.
    t.setposition(x, y+25)
    branch = (25/math.sin(45 * math.pi/180))
    t.setposition(x, y+25)
    t.setposition(x, y+50)
    # Draw the tree's crown using a RegularPolygon.
    # Make sure to set the polygon's coordinates so
    # that the base is at the top of the trunk, i.e.
    # where drawing stopped.
    # Too many magic numbers.
    # For example, the number of sides and side length.
    number_of_sides = 7
    side_length = 80
    RegularPolygon(t, color,
        x, (t.ycor() + (side_length/2) / math.tan(math.pi/number_of_sides)),
        number_of_sides, side_length, fill)

# Draw a cross right in the center of the canvas.
# Use this for visual checking of other drawn graphics.
def CenterCross(t):
    end_point = 25
    diagonal = (end_point/math.sin(math.radians(45))) * 2
    t.setposition(end_point * -1, end_point * -1)
    t.setposition(end_point * -1, end_point)

def DrawTrees(entries):
    tree_colors = []
    for entry in entries:
        tree_color = entry[1].get()
        if len(tree_color) > 0:

    if len(tree_colors) == 0:

    turtle.TurtleScreen._RUNNING = True
    my_turtle = turtle.Turtle()
    turtle.title('Python Turtle Example')
    # Set up center points for each tree, i.e.
    # where the trunks go.
    startx = (len(tree_colors) - 1) * -100
    object_span = 200
    # Draw all the trees in our selected colors.
    fill = False
    for color in tree_colors:
            Tree(my_turtle, color, startx, 0, fill)
        except turtle.TurtleGraphicsError:
            print("Bad color " + color);
        startx += object_span
        fill = not fill

    # Visually show where position 0,0
    # is on the canvas.
    # Wait for a mouse click anywhere on the
    # window's canvas area, then exit.

def MakeForm(root, fields):
    entries = []
    for field in fields:
        row = tk.Frame(root)
        lab = tk.Label(row, width=15, text=field,
            anchor='w', background='#d0d0d0')
        ent = tk.Entry(row)
        row.pack(side=tk.TOP, fill=tk.X, padx=5, pady=5)
        ent.pack(side=tk.RIGHT, expand=tk.YES, fill=tk.X)
        entries.append((field, ent))
    return entries

def ShowForm():
    root = tk.Tk()
    root['background'] = '#d0d0d0'
    ents = MakeForm(root, ['Tree 1','Tree 2','Tree 3','Tree 4'])
    root.bind('<Return>', (lambda event, e=ents: DrawTrees(e)))   
    b1 = tk.Button(root, text='Show',
        command=(lambda e=ents: DrawTrees(e)))
    b1.pack(side=tk.LEFT, padx=5, pady=5)
    b2 = tk.Button(root, text='Quit', command=root.quit)
    b2.pack(side=tk.LEFT, padx=5, pady=5)

if __name__ == "__main__":

To drive the Turtle graphics, I used Tcl/Tk to create a very simple GUI. Not much there, four fields to fill in a color, a Show button to show the Turtle graphics window, and a Quit button.
And once again the version under Linux.

Unlike Turtle graphics rendering, the Linux version of the Tk form looks a lot better than the macOS version. By the way, for those who want to give this a spin, you can enter from one to four colors, and you will draw as many trees as the number of colors you enter. Clear all the fields and nothing happens.

Working with Python on macOS isn’t smooth sailing. While working with Python3 (3.8.6) I came across two messages sent to the console every time I ran the application:

DEPRECATION WARNING: The system version of Tk is deprecated and may be removed in a future release. Please don't rely on it. Set TK_SILENCE_DEPRECATION=1 to suppress this warning.
2020-12-05 15:35:16.336 Python[67143:3480650] ApplePersistenceIgnoreState: Existing state will not be touched. New state will be written to /var/folders/d9/n152_yx519121c0nlmlds71c0000gn/T/org.python.python.savedState

The first line is easy enough to eliminate by following the advice of the first warning by adding export TK_SILENCE_DEPRECATION=1 to your .zshrc file. The second warning is a bit more obscure, but I found a solution in a StackOverflow forum posting. At the command line execute defaults write org.python.python ApplePersistenceIgnoreState NO in a terminal, and that should take care of that. For more details see https://stackoverflow.com/questions/18733965/annoying-message-when-opening-windows-from-python-on-os-x-10-8 . Needless to say I never saw either of those messages until I stepped up to macOS 11.0.1. Just lovely.

In the end I got tired of having that message pop out of the version of Tcl/Tk that ships with macOS. I downloaded the latest version from ActiveState and installed it, then downloaded the latest version of Python from Python.org and installed it on top of that. I tried the same thing through Brew, but the Brew version of Python wouldn’t bind with the Brew version of Tcl/Tk, only the system version. Out of annoyance I force removed both Brew’s Tcl/Tk and Python, then installed ActiveState’s Tcl/Tk and Python.org’s Python 3.9.1. No more deprecation messages, and the Tcl/Tk widgets look a little better on my Mac, but not by much.

Working with Python on CentOS 8.3 (and RHEL 8.3 for that matter) required building a more up-to-date version of Python on those platforms. I tried stepping up to Python 3.9.1, but building that version of Python on those platforms is something of a hot mess, especially when trying to build the SSL modules required by pip to install third-party Python modules. Those SSL modules failed to build, and without them, pip won’t download anything. This build issue is also found with Ubuntu 20.04 and 20.10. Even though Python 3.9.1 is officially released, for all practical purposes it’s still bleeding edge enough and should be left alone unless you can get it pre-built, such as for macOS. Stick with Python 3.8.x as the latest to build and use.

installing pyqt5 (qt version 5.15) on python 3.8.5 and jetpack 4.4

Back in September 2019 I wrote how I failed to build Qt 5.13 from its C++ source, which was the latest Qt release at that time(see https://arcanesciencelab.wordpress.com/2019/09/02/an-absolute-failure-unable-to-build-qt5-on-a-raspberry-pi-4/ ). My primary reason to build the latest Qt was to step up the Qt version used in PyQt5. There were problems I’d discovered in the installed repo version, and I’d wanted to create a development environment where I could investigate, and if possible, try to fix any of those problems, with an eye towards pushing any fixes back up stream. That obviously didn’t work out, and I left the whole thing alone. Until now.

For whatever reason I decided to try again. Except this time, I used JetPack 4.4 on the Nvidia Xavier NX Developer Kit. While the Xavier is ostensibly for machine learning prototyping and development, the fact it’s based on Ubuntu 18.04.5, ported onto Nvidia’s six core ARM chip, makes it too tempting for me just to use for ML. And thus I decided to try to run with the latest PyQt5 on the latest Python 3 release.


I’m starting from my Python 3.8 installation inside an activated Python virtual environment. I’d documented how to build Python from scratch as well as create a working virtual environment here: https://arcanesciencelab.wordpress.com/2020/05/24/building-python-3-8-3-on-jetpack-4-4-dp-and-the-jetson-xavier-nx/ , so I won’t go through that again.

However, before we really get started, you’ll need to install the basic Qt5 development tools, otherwise PyQt5 won’t install. You do that with sudo apt install qt5-default . That gives all the basic tools and support libraries.

With Qt5 default installed, activate the Python 3.8 virtual environment. I’ve since moved up to Python 3.8.5, and I’m getting ready to install Python 3.9 alongside 3.8.5 when it’s officially released. That’s another reason I like virtual environments; it’s incredibly easy to keep multiple Python versions on hand.

Within the virtual environment, do a simple pip install pyqt5 .

You might as well go off and do house work or watch an episode or two of your favorite streaming shows, because this is going to take a while (as in hours). No, I didn’t time it.

Once it’s done, it should announce it’s successful. From there you can work with PyQt5 within that virtual Python environment. I would strongly recommend you always work within a Python virtual environment. It all works with your regular security permissions (no sudo), and if you want to blow it away, it’s very easy to do so. I just don’t like adulterating the system installation of Python anymore.

So far, except for the long build time, everything is working without any drama.