-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
pydrake: Migrate pydrake.examples
to example directories
#9645
Comments
pydrake.examples
pydrake.examples
to example directories
The other ideas/concerns that we discussed:
|
Neither #9646 nor this issue formulates the way that makes the more sense to me. I will try to write up longer thoughts later, but to me the only important thing is whether the API to the artifact being shipped is via library calls (linking / loading) or via a binary program (new process). I am more than happy to ship any and all sealed binary demos -- where the stable interface to the user is the README.md and command-line arguments -- no matter where they live in the source tree. When the API is via a library (be it C++ headers or python module), I think it should not live in examples. In short, the only public targets of |
Per #4224, yes, the current intent is that all of the example applications are (or at least could be) installed. |
Relates #8911.
At present, some components from
//examples
are bound and exposed viapydrake.examples
. They should be removed.If there is functionality that should be accessible via
pydrake
(or@drake//
in general), it should live outside of//examples
.Process:
//examples
folder.pydrake.examples
modules. (May involve code duplication to preserve backwards compatibility.)pydrake.examples
\cc @RussTedrake @jwnimmer-tri
The text was updated successfully, but these errors were encountered: