-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Should we keep vendoring dependencies? #4
Comments
I'm fine to not vendor dependencies on AspenWeb projects. |
@pjz is -1 on vendoring. |
Okay, then let's drop vendoring entirely, it'll be easier than to use Git LFS. I'll make a PR, and once it's merged we'll rebase 527 on top of master. |
Changaco
added a commit
to AspenWeb/pando.py
that referenced
this issue
Mar 9, 2016
Changaco
added a commit
to AspenWeb/pando.py
that referenced
this issue
Mar 11, 2016
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Picking up from #2 (comment)
Do we want all projects who have dependencies to vendor in
virtualenv
,setuptools
,pip
, etc? Why do we expectpython
to be installed (since we don't vendor it) but notvirtualenv
and the packaging tools?The goal of vendoring is to allow offline hacking, right? Why isn't it enough to have a simple reminder in the README that you need to run
make env
or whatever before going offline?The text was updated successfully, but these errors were encountered: