| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
| |
Signed-off-by: Sanjeev Gupta <ghane0@gmail.com>
Signed-off-by: Gary E. Miller <gem@rellim.com>
|
| |
|
|
|
|
| |
Note the program pep8 is now called pycodestyle
|
| |
|
| |
|
|
|
|
|
| |
pylint does not like changing the type of a variable. In this
case tupples to ints. So add an intermediate variable.
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This makes the "future import" statements consistently specify
absolute_import, print_function, and division, for maximum consistency
between Python 2 and Python 3. Although absolute_import is probably a
don't care for top-level programs, if unit tests were ever implemented
for the programs they would be imported as modules, making the module
import behavior relevant.
Note that previous Python 3 fixes are a prerequisite for this change.
Also makes the "polyglot comment" consistent across sources.
TESTED:
Using a version of SConstruct patched to use the target Python for
build helpers, ran "scons build-all check valgrind-audit
www/hardware.html" with all six supported Python versions. Also ran
gegps, gpscat, gpsprof, xgps, and xgpsspeed with both Python 2 and
Python 3.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This fixes two Python 3 issues with leapsecond.py:
1) The urllib module is subdivided in Python 3. Only the 'request'
submodule is needed here. Either that or the Python 2 urllib is now
imported as 'urlrequest'.
2) The data returned by urlopen() is 'bytes' in Python 3, requiring
the polystr transformation to be usable as a string.
Also, the (duplicate) isotime() definition here has been updated to
match the version in gps/misc.py. It is still duplicated to avoid a
dependency on the latter, as is the needed portion of the polystr
code.
TESTED:
Ran "scons build-all check". Also ran "leapsecond.py -f" with all six
supported Python versions, and verified that the result matches the
existing leapseconds.cache. Did *not* test the updated retrieve()
function, but it's not used anywhere.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This changes a few integer division cases to use the '//'
floored-division operator, matching the normal Python 2 (C-like) '/'
behavior, for compatibility with the switch to the "mathematical"
divison operator in Python 3 (and in Python 2 with the "future
division" import). This was more about keeping the behavior the same
than determining whether floored division is actually the proper
choice.
One place where floored division is definitely wanted is in the GPS
week calculations in leapsecond.py, which are now OK for Python 3,
though currently that module is only used by SConstruct, and hence not
with Python 3.
Two other minor fixes:
1) The GPS base date is corrected in the comment in leapsecond.py.
2) The fit_to_grid() function in xgps now consistently returns floats,
rather than returning either ints or floats depending on the line
width.
TESTED:
Ran "scons build-all check" with all 6 supported Python versions.
Also ran xgps and xgpsspeed with all but 2.6.
|
| |
|
| |
|
|
|
|
|
|
|
| |
Verified by testing gpsprof under both versions. leapecond.py is also OK.
Not yet polyglot: gegps, gpscap.py, gpscat, gpsfake, jsongen.py, maskaudit.py,
test_maidenhead.py, valgrind_audit.py, xgps, xgpsspeed.
|
|
|
|
|
|
| |
For the moment most shebang lines still say 'python2' rather than just 'python'.
This is because the client code in gps/ hasn't been touched yet; the internal
imports break under Python 3 and that needs to be fixed.
|
|
|
|
|
|
| |
We've learned that Ubuntu 15.10 will have python3 as default. The ugly
transition gas befun; our only recourse is to hape that all our deployment
targets have 'pyton2' do the right thing. Works on 14.10.
|
|
|
|
| |
Signed-off-by: Gary E. Miller <gem@rellim.com>
|
|
|
|
|
|
| |
Else they lie on the border.
Signed-off-by: Gary E. Miller <gem@rellim.com>
|
|
|
|
|
|
| |
Else they lie on the border.
Signed-off-by: Gary E. Miller <gem@rellim.com>
|
|
|
|
|
|
|
| |
There is no uniformity, hence a line linking points is misleading.
Also clarify Title, this is not TAI-UTC, but GPS-UTC.
Signed-off-by: Gary E. Miller <gem@rellim.com>
|
|
|
|
| |
Signed-off-by: Gary E. Miller <gem@rellim.com>
|
|
|
|
|
|
|
| |
2 lines between functions
2 spaces before inline comments
cleanup indentation in a couple of places
whitespace around operators and = and after commas
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
I am not sure where this should be, but I do not
think this documentation is of direct use to users. Hence
I am adding it to timebase.c , for developers.
Signed-off-by: Eric S. Raymond <esr@thyrsus.com>
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
| |
1. Minor typo in example
2. Added second example for thos with an X11-aware gnuplot
|
| |
|
|
|
|
|
|
| |
I will go through all files that call gnuplot and check syntax
Signed-off-by: Eric S. Raymond <esr@thyrsus.com>
|
| |
|
| |
|
|
|
|
|
| |
Fail more gracefully in this case, and add a leapfetch=no option to
work around it.
|
|
|
|
|
|
|
|
| |
Because of connection problems, add the IERS to the list of places that
are checked for the UTC-TAI history. Adjust the parsing for the
differences in the format of the IERS file.
Signed-off-by: Eric S. Raymond <esr@thyrsus.com>
|
|
|
|
|
|
|
| |
I have problems connecting to maia.usno.navy.mil, and setting a socket
timeout at least doesn't block the build process.
Signed-off-by: Eric S. Raymond <esr@thyrsus.com>
|
| |
|
|
|
|
| |
Signed-off-by: Eric S. Raymond <esr@thyrsus.com>
|
|
|
|
| |
...as well as past ones. All regression tests pass.
|
| |
|
|
|
|
| |
One could have been a fatal error.
|
| |
|
| |
|
| |
|