Skip to content
This repository has been archived by the owner on Jun 7, 2018. It is now read-only.
/ vend Public archive

Vendored dependencies for Python. No more Virtualenv bullshit! (Work in progress)

License

Notifications You must be signed in to change notification settings

notpushkin/vend

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

1 Commit
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

vend

Work in progress

Vendored dependencies for Python. No more Virtualenv bullshit!

Usage:

$ vend init
Creating Pipfile...
Creating vendor dir (my_package/vendor)...
Done! Please add the following lines to your __init__.py:

  v_path = os.path.sep.join([
      os.path.dirname(os.path.realpath(__file__)), 'vendor'])
  if os.path.isdir(v_path):
      sys.path.append(v_path)

$ vend install some dependencies
$ python3.5 -m my_package  # no venv!

FAQ

Why would you do that?

I just got tired of all these incompatibilities between venvs (conda, pew/pipenv, vanilla virtualenv etc) and stuff.

Also, this allows you to rename and move and copy project and sync it over $YOUR_FAVOURITE_STORAGE_PROVIDER without breaking anything (i. e. virtualenvs).

Should I check my vendored dependencies into the VCS?

This is actually up to you. Kenneth Reitz does this (pipenv, requests), I personally just don't like it.

About

Vendored dependencies for Python. No more Virtualenv bullshit! (Work in progress)

Topics

Resources

License

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published

Languages