Not pushed to pypi yet, but soon! Here’s the PR: Initial Apriltag wrapper by virtuald · Pull Request #1 · robotpy/robotpy-apriltag · GitHub
One thing I’d love help with – I chose the name
rpy_apriltag for the import path. I don’t like it, but I also don’t want to conflict with the apriltag library which already uses
apriltag. Open to other ideas.
Just go with robotpy_apriltag
But it’s tradition our import names don’t match our package names! /s
In all honesty this is probably the least confusing option.
rpy_apriltag seems to be descriptive enough to be clear and not be confusing. Go with your first thoughts on naming.
wpilib_apriltag or robotpy_apriltag
future proof the package name assuming robot py will be part of wpilib in 2024. wpitag makes it sound like WPILib made its own unique tag. wpi_apriltag works but isn’t specific enough. Apriltagz just sounds kind of silly.
This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.