Zach Moody

@MarkehMe I'm on OSX and got around that by downgrading NPM to 4.6.1. No idea why that works or if it's good practice.

Hey, sorry, MacOS 10.12.2

@andersryanc think that behavior is related to #89.

Yeah, the approach I went with for pynetbox in the beginning was to have `Record` cover as many use-cases as was reasonable without adding a ton of conditionals for outliers...

I don't think I mind the global, but I have a feeling tinkering with `__setstate__` is going mess with pickling. Are the tests ok after that change?

Seems ok for me. This is on NetBox 2.7.12 though. ```>>> import pynetbox >>> nb = pynetbox.api("https://netbox", token="hunter2") >>> x = nb.dcim.devices.get(123) >>> x test-device >>> x.tags [] >>> x.tags.append("test")...

> Would be kinda cool if .save() would not return True unless it was a HTTP/1.1 200 OK, but I am nitpicking. That's probably fair, iirc, we look at `response.ok`...

:wave: I hadn't really planned on including it. Mostly because there's plenty of well-support GQL libraries out there already, and I'm not that interested in making another one. I don't...

Yeah, I think in practice, that meant we stopped testing against py2. Keeping it around doesn't bother me too much, but we can drop it in the next major release.

I feel like a more comprehensive look at plugin support might be needed. There's a handful of places we assume certain behavior from NetBox, and the folks developing it have...