dmtucker

Configuring IPv6 on EdgeRouter Lite

Tested with:

• v1.9.7+hotfix.4, Wave G in Seattle
• v1.10.5, Comcast in the South Bay Area

set interfaces ethernet eth0 description LAN
set interfaces ethernet eth1 description WAN
set interfaces ethernet eth2 description WLAN

dmtucker

#!/usr/bin/env bash
update_via_http () {
    if [ -z "${token+undefined}" ] || [ "$#" != 2 ]
    then
        echo 'usage: token=<your-HTTP-token> update_via_http zone ipv6' 1>&2
        exit 1
    fi
    zone="$1"
    ipv6="$2"
    # https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=141323

dmtucker

• astroid < 1.3
  • pylint-dev/astroid#85 (comment)
• coverage < 5
  • https://bitbucket.org/ned/coveragepy/issues/609/drop-python-26-and-33
• cryptography < 2.2
  • https://github.com/pyca/cryptography/blob/master/CHANGELOG.rst#22---2018-03-19
• isort < 4.3.0
  • https://github.com/timothycrosley/isort/blob/develop/CHANGELOG.md#430---january-31-2018
• paramiko < 2.4.0
• paramiko/paramiko#1119

dmtucker

• https://www.bernat.tech/pep-517-and-python-packaging/
• https://caremad.io/posts/2013/07/setup-vs-requirement/
• https://nedbatchelder.com/text/names1.html
• https://nedbatchelder.com/text/unipain.html
• https://blog.ionelmc.ro/2014/05/25/python-packaging/
• https://blog.ionelmc.ro/presentations/packaging/#slide:14
• https://datagrok.org/python/activate/

dmtucker

LTS

Stage	Group	Project	Services
dmtucker

dmtucker

say we claim support for >=1, <3

• 1.0 is the first supported version.
  • if this isn't tested, features from later versions may be depended on that break compatibility with this version.
• 1.x adds to it.
  • test the latest version available to detect new features that collide (e.g. variables named async are fine in python 3.6 but async becomes a keyword in python 3.7).
    • only the latest version needs to be tested because features cannot be removed without a major version bump.
  • if something breaks, either
    • a new feature collided with existing code
    • upstream did not follow semver and broke compatibility
• existing code uses upstream code that is not part of the public API

dmtucker

What's up with Python 1.17 in the PyPI stats database?

dmtucker

$ python3 sep.py 
different: cp037 b'a'
different: cp273 b'a'
different: cp424 b'a'
different: cp500 b'a'
different: cp875 b'a'
different: cp1026 b'a'
different: cp1140 b'a'
untested: cp65001
different: utf_32 b'\xff\xfe\x00\x00/\x00\x00\x00'

dmtucker

import os
import py

def _relpath(path, *, relto):
    # TODO py35+ commonpath = os.path.commonpath([path, relto])
    commonpath = str(py.path.local(path).common(py.path.local(relto)))

    def _commonpath_to(_path):
        return _path[len(commonpath):].strip(os.path.sep)

dmtucker

why doesn't it make sense to mix strings and bytes in path components with posixpath.join? this Q is really only for py2 since 3 does away with implicit conversions, but the unicode could be encoded and the join would succeed. even if that results in a multi-encoding str, I've been told, that's ok in POSIX