Skip to content
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

Any 1.0 breaking changes? #58

Open
jdlangs opened this issue Oct 7, 2018 · 2 comments
Open

Any 1.0 breaking changes? #58

jdlangs opened this issue Oct 7, 2018 · 2 comments

Comments

@jdlangs
Copy link
Owner

jdlangs commented Oct 7, 2018

The package API has been stable for a while now and it would be nice to commit to a version 1.0 now that Julia itself has done the same. There's no real rush to do it though and now would be the time to bring in any final breaking changes.

So any proposals for changing stuff up? An easier type generation process? Changes to ease a future ROS2 migration? I'd love to hear any ideas, regardless of feasibility.

@togo59
Copy link

togo59 commented Dec 12, 2018

I have ENV["PYTHON"]="/usr/bin/python" in my startup.jl for Julia version 1.0.2 and exactly the same in my .juliarc.jl file for v0.6.4.

For v0.6.4 everything is fine. Everything works.
For v1.0.2, when I do using RobotOS I get
ERROR: InitError: rospy not found! Has an environment setup script been run?

Using ROS Kinetic on Ubuntu 16.04 Unfortunately I'm pretty much wedded

Which script?

@togo59
Copy link

togo59 commented Dec 13, 2018

Sorry! -- Not a RobotOS issue but something Atom does with path names. See: https://github.com/JunoLab/atom-julia-client/issues/538

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants