Yo Fred! On Tue, 29 Jan 2019 19:01:40 -0800 (PST) Fred Wright via devel <devel@ntpsec.org> wrote:
> > Well, the way we use sys.stdout is warned about in the Python doc. > > That is enough for me to want it aligned with the python doc. > > The real question is why the build procedure thinks it needs to > output 'bytes' to the terminal, Easy, to fix make the code work with Python2 and Python 3. See here: https://gitlab.com/esr/practical-python-porting/blob/master/polystr-inclusion.py http://www.catb.org/esr/faqs/practical-python-porting/ Weird, but no one has done better. > It can probably be worked around by prefixing the build command with > "NOSYNC=1", which disables waf's AnsiTerm hackery. That worked. Thanks! Something for Eric to add to the INSTALL procedure and to his 'Practical Python Porting". RGDS GARY --------------------------------------------------------------------------- Gary E. Miller Rellim 109 NW Wilmington Ave., Suite E, Bend, OR 97703 g...@rellim.com Tel:+1 541 382 8588 Veritas liberabit vos. -- Quid est veritas? "If you can’t measure it, you can’t improve it." - Lord Kelvin
pgpZGdLBAZ6O5.pgp
Description: OpenPGP digital signature
_______________________________________________ devel mailing list devel@ntpsec.org http://lists.ntpsec.org/mailman/listinfo/devel
