[soton] [activity-2014-11-26] Final push for Python 3 port of SR tools
11 views
Skip to first unread message
Tom Leese
Nov 24, 2014, 10:14:56 AM11/24/14
to Student Robotics
Hi all,
On Wednesday 26th November I intend to run an activity where we shall finish
the last remaining to-do items which are required to complete the Python 3
(and Setuptools) port of the Student Robotics tools.
I will be in SR1 from 5pm and I imagine this activity will take most of the
doing. A large majority of the time will be put to testing all the individual
commands to check they are still working in Python 3 (and preferably in Python
2). We will also look at producing some proper API documentation (generated
with sphinx and docstrings) and a user guide for installation.
We will go to the pub at around 8pm (with anyone else who is at the doing).
Tom
On Wednesday 26th November I intend to run an activity where we shall finish
the last remaining to-do items which are required to complete the Python 3
(and Setuptools) port of the Student Robotics tools.
I will be in SR1 from 5pm and I imagine this activity will take most of the
doing. A large majority of the time will be put to testing all the individual
commands to check they are still working in Python 3 (and preferably in Python
2). We will also look at producing some proper API documentation (generated
with sphinx and docstrings) and a user guide for installation.
We will go to the pub at around 8pm (with anyone else who is at the doing).
Tom
Tom Leese
Nov 27, 2014, 3:53:31 AM11/27/14
to Student Robotics
Hi all,
On 24/11/14 15:14, Tom Leese wrote:
> On Wednesday 26th November I intend to run an activity where we shall finish
> the last remaining to-do items which are required to complete the Python 3
> (and Setuptools) port of the Student Robotics tools.
This happened and was fairly successful (although we didn't finish all
the remaining to-do items!).
Having tested the Setuptools based installation procedure on numerous
machines, we're quite happy that it's a definite improvement over
scripts and symlinks in '~/.sr'. We're also now pretty confident that
the budget and inventory tools work on both Python 2 and Python 3—Harry
was even able to port some of the old shell script inventory tools to
Python. The remaining tools *should* still work under Python 2, however
there is a fine chance that something else broke in the move to Setuptools.
We came across an inventory tool called 'inv-newflag' which we decided
to rename to 'inv-setattr' for clarity, please let us know if we've
broken someone's work flow here; it would be trivial to restore the
previous name.
We were also able to start writing some documentation to go with the
tools, with the ultimate goal of being about to run 'man sr-<tool>' and
getting something useful back.
It's now getting to the point where we would really appreciate it if
people who use specific tools are able to test and help in the Python
porting process. There is documentation on Trac[0] or in the 'python3'
branch of 'tools.git' on how to get the new tools set up.
Tom
[0]:
https://www.studentrobotics.org/trac/wiki/DevScripts#BetaInstallationMethod
On 24/11/14 15:14, Tom Leese wrote:
> On Wednesday 26th November I intend to run an activity where we shall finish
> the last remaining to-do items which are required to complete the Python 3
> (and Setuptools) port of the Student Robotics tools.
the remaining to-do items!).
Having tested the Setuptools based installation procedure on numerous
machines, we're quite happy that it's a definite improvement over
scripts and symlinks in '~/.sr'. We're also now pretty confident that
the budget and inventory tools work on both Python 2 and Python 3—Harry
was even able to port some of the old shell script inventory tools to
Python. The remaining tools *should* still work under Python 2, however
there is a fine chance that something else broke in the move to Setuptools.
We came across an inventory tool called 'inv-newflag' which we decided
to rename to 'inv-setattr' for clarity, please let us know if we've
broken someone's work flow here; it would be trivial to restore the
previous name.
We were also able to start writing some documentation to go with the
tools, with the ultimate goal of being about to run 'man sr-<tool>' and
getting something useful back.
It's now getting to the point where we would really appreciate it if
people who use specific tools are able to test and help in the Python
porting process. There is documentation on Trac[0] or in the 'python3'
branch of 'tools.git' on how to get the new tools set up.
Tom
[0]:
https://www.studentrobotics.org/trac/wiki/DevScripts#BetaInstallationMethod
Harry Cutts
Nov 28, 2014, 5:53:38 AM11/28/14
to sr...@googlegroups.com
Hi,
On Thursday, 27 November 2014 08:53:31 UTC, Tom Leese wrote:
We came across an inventory tool called 'inv-newflag' which we decided
to rename to 'inv-setattr' for clarity, please let us know if we've
broken someone's work flow here; it would be trivial to restore the
previous name.
It's worth mentioning that it wasn't only the name that changed; the argument which lists part codes to change has been moved to the end, to avoid having to quote lists (e.g. `$ sr inv-setattr foo bar SR000 SR0XE6` instead of `$ sr inv-setattr "SR000 SR0XE6" foo bar`).
Harry Cutts
Reply all
Reply to author
Forward
0 new messages