nicktimko

#!/usr/bin/env python3
"""
Covert a Pipfile/[.lock] to a pip-tools requirements.(in|txt) file. While it's
only slightly annoying to convert the Pipfile to a requirements.in (which we
do) the primary goal is to convert the *locked* file with all the versions and
hashes, without *updating* any of them. This will allow bisection of problems
to the conversion from Pipenv to Pip-tools without confounding from myriad
updates to all the libraries used within.

To validate/clean up the new file, you can run the build command which will

nicktimko

nicktimko

nicktimko

nicktimko

nicktimko

nicktimko

nicktimko

#!/usr/bin/env python3
"""
Why bother with a service that hits the watchdog? The watchdog package seems
kinda daft if you're worried about your service locking up and/or not doing
something it should be doing.

Maybe could use something like this in conjuction with the watchdog daemon,
but don't want both to reset the WDT or that would be near pointless. Ideally
on my service start I'd like to permanently put the WDT into a state where
it's active, which seems to be done by opening the `/dev` file. Python

nicktimko

import functools

class Operator:
    def __init__(self, func):
        self.func = func

    def __rlshift__(self, other):
        return self.__class__(functools.partial(self.func, other))

    def __rshift__(self, other):

nicktimko