Support

PyPath is coming soon to the App Store. Once it is available: open the App Store on your iPhone, iPad or Mac, search for PyPath and tap the download button. You need iOS 18 or later on iPhone and iPad, or macOS 15 or later on the Mac.

Yes. Install PyPath on each device with the same Apple ID. What you buy then works on all of those devices, and your progress syncs via iCloud. Short exercises are handy on your iPhone, bigger assignments on your Mac.

Not yet. The lessons and the app are in Dutch for now; English lessons are on the roadmap.

PyPath stores your progress on your device and, if iCloud is enabled, in your own private iCloud storage. On another device with the same Apple ID your progress then appears automatically. You can also keep learning offline: as soon as you are connected again, everything is merged without losing progress.

Check these points:

• You are signed in with the same Apple ID on both devices.
• iCloud is turned on for PyPath. On iPhone and iPad: Settings › your name › iCloud, then under the apps using iCloud. On the Mac: System Settings › your name › iCloud.
• Both devices are online, and your iCloud storage is not full.
• Open PyPath on both devices and give it a moment.

No. Week 1 is free, and everything after that is a one-time purchase: PyPath Basis, individual trade packs, or everything together in PyPath Complete. Nothing renews automatically, so there is nothing to cancel either.

On a new device, or after reinstalling PyPath, choose Aankopen herstellen (Restore purchases) in PyPath. Use the same Apple ID you bought with; your purchases come back without paying again.

Purchases are handled by Apple, so you request a refund from Apple at reportaproblem.apple.com. The developer of PyPath cannot issue refunds directly.

Team licences for businesses will follow later. Until then, everyone buys PyPath with their own Apple ID.

That is part of learning to program. A few things that almost always help:

• Read the explanation below the error message. The message itself is in English, as in real Python and pyRevit; PyPath adds a plain-language explanation.
• Check the indentation: everything inside an if, for or def must be indented by the same amount.
• Do not forget the colon at the end of a line with if, for or def.
• Brackets and quotes always come in pairs.
• Capitals matter: FilteredElementCollector is not the same as filteredelementcollector.
• Ask for a hint. After three attempts you can view the model solution.

Draaien (Run) executes your code and shows the output in the console, as often as you like. Nakijken (Check) has PyPath verify whether your exercise is correct, and gives you feedback and XP.

We would like to know. Report it via GitHub Issues with the name of the lesson and the exercise, your code and what you expected. Do not include personal data; issues are public.

The Revit exercises use the real names from the Revit API and pyRevit, so the way of working is the same. The simulated model is simpler than a real project, though. pyRevit uses IronPython 2.7 by default: write .format() instead of f-strings there, or choose the Python 3 engine. Always test a new script on a copy of your model first.