Search found 3 matches
- Tue Apr 28, 2015 1:50 pm
- Forum: Developer Discussions
- Topic: Rationale for importing os.path as _path in cfclient?
- Replies: 0
- Views: 8458
Rationale for importing os.path as _path in cfclient?
From what I've read, importing a module as some name is useful to deconflict different modules with matching names. In the cfclient file (located in /bin of the GitHub release), os.path is imported as _path (line 7). Is there a reason that this method is used as opposed to "from os import path&...
- Sat Apr 18, 2015 6:34 am
- Forum: Support
- Topic: [SOLVED] How to run cfclient from source?
- Replies: 1
- Views: 2550
Re: How to run cfclient from source?
Solved: the cfclient file in crazyflie-clients-python/bin is not a binary file; it is a Python script. Viewing with the nano text editor: crazyflie-clients-python/bin username$ nano cfclient The file defines a couple functions and concludes with the following: if __name__ == '__main__': init_paths()...
- Fri Apr 17, 2015 2:33 am
- Forum: Support
- Topic: [SOLVED] How to run cfclient from source?
- Replies: 1
- Views: 2550
[SOLVED] How to run cfclient from source?
My Crazyflie 2.0 has been flying great with the cfclient in the crazyflie-clients-python/bin folder. I have also been able to run basiclog.py and ramp.py from the crazyflie-clients-python/examples folder. I'm going to be doing some control and navigation development, so I'm delving into the Python c...