You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This repo is currently under @Luxonis-Brandon's GitHub account. It makes sense to move this under the Luxonis GitHub org.
Why now?
The RPi compute additions have this repo checked out so the calibration can be performed prior to shipping. We want to ensure their local git repo points to a valid url and simply type "git pull" to fetch updates vs. having to update their .git/config as well.
Additionally:
Change the name to depthai-python-extras.
Remove the /images folder and top-level README.
Move the contents of the python-api folder to the top-level
Why not call the repo depthai-python-api?
Two primary reasons:
While the repo contains the shared library files (.so extension) that contain the depthai Python module, in the medium-term we plan to release a pip-installable version of depthai. When that happens, the .so files will not be used and no API-specific things, just utilities, examples, and tutorials will be located in this repo.
This repo does not contain the depthai Python module source code, which is what I'd expect for a repo with the name depth-python-api. Instead, it's primarily scripts that load the depthai module.
How will this repo be organized?
Eventually we'll have 3 primary folders:
utils
examples
tutorials (the code used for more in-depth walkthrus on our docs and blog)
I don't believe we can start this structure now because of how resource paths and resources are loaded (they assume the script is being executed in the top-level directory and the above dependencies are in nested folders). This will change w/the pip version of depthai.
For now, it's just the contents of the existing python-api folder.
What if I already have this repo checked out locally?
I'll provide instructions for updating your local repo after the transfer.
How do you transfer?
The repo owner, @Luxonis-Brandon, can do this in the repository settings "Danger Zone" area:
The text was updated successfully, but these errors were encountered:
This repo is currently under @Luxonis-Brandon's GitHub account. It makes sense to move this under the Luxonis GitHub org.
Why now?
The RPi compute additions have this repo checked out so the calibration can be performed prior to shipping. We want to ensure their local git repo points to a valid url and simply type "git pull" to fetch updates vs. having to update their
.git/config
as well.Additionally:
depthai-python-extras
./images
folder and top-levelREADME
.python-api
folder to the top-levelWhy not call the repo
depthai-python-api
?Two primary reasons:
While the repo contains the shared library files (
.so
extension) that contain thedepthai
Python module, in the medium-term we plan to release a pip-installable version ofdepthai
. When that happens, the.so
files will not be used and no API-specific things, just utilities, examples, and tutorials will be located in this repo.This repo does not contain the
depthai
Python module source code, which is what I'd expect for a repo with the namedepth-python-api
. Instead, it's primarily scripts that load thedepthai
module.How will this repo be organized?
Eventually we'll have 3 primary folders:
I don't believe we can start this structure now because of how resource paths and resources are loaded (they assume the script is being executed in the top-level directory and the above dependencies are in nested folders). This will change w/the pip version of
depthai
.For now, it's just the contents of the existing
python-api
folder.What if I already have this repo checked out locally?
I'll provide instructions for updating your local repo after the transfer.
How do you transfer?
The repo owner, @Luxonis-Brandon, can do this in the repository settings "Danger Zone" area:
The text was updated successfully, but these errors were encountered: