piker/requirements.txt

# we require a pinned dev branch to get some edge features that
# are often untested in tractor's CI and/or being tested by us
# first before committing as core features in tractor's base.
-e git+git://github.com/goodboy/tractor.git@piker_pin#egg=tractor

# `pyqtgraph` peeps keep breaking, fixing, improving so might as well
# pin this to a dev branch that we have more control over especially
# as more graphics stuff gets hashed out.
-e git+git://github.com/pikers/pyqtgraph.git@piker_pin#egg=pyqtgraph
Pin to specific branch made for us 2021-10-23 16:25:16 +00:00			`# we require a pinned dev branch to get some edge features that`
			`# are often untested in tractor's CI and/or being tested by us`
			`# first before committing as core features in tractor's base.`
			`-e git+git://github.com/goodboy/tractor.git@piker_pin#egg=tractor`
Use a `pyqtgraph` dev branch pin (again) There's lotsa movement on the project these days with stuff getting improved, borked, fixed, rinse repeat. Might as well use a pin on our fork so we can more easily hack on it and pull in latest features piece-wise for testing. 2021-12-07 20:11:00 +00:00
			# `pyqtgraph` peeps keep breaking, fixing, improving so might as well
			`# pin this to a dev branch that we have more control over especially`
			`# as more graphics stuff gets hashed out.`
			`-e git+git://github.com/pikers/pyqtgraph.git@piker_pin#egg=pyqtgraph`