1. Doug Hellmann
  2. virtualenvwrapper

Commits

Doug Hellmann  committed 279e798

status update

  • Participants
  • Parent commits af54241
  • Branches master

Comments (0)

Files changed (1)

File venv.org

View file
 # Org-mode notes and task list
 
-* TODO convert to distribute for packaging [1/2]
-  - get rid of newvenvw and virtualenvwrapper virtualenvs and re-create
-  - [X] pavement.py to setup.py
-  - [ ] sphinx conf.py needs to get version from setup.py somehow
-  - [ ] separate rules for making website
-  - [ ] installwebsite
-  - [ ] register
-  - [ ] test for installation
-
-* plugin system for hooks
-  - http://bitbucket.org/dhellmann/virtualenvwrapper/issue/28/
-  - use Distribute/setuptools entry points
-  - namespace package `virtualenvwrapper` to hold plugins I write, but
-    not required for other authors
-  - bump version to 2, since the user script implementation is moving
-    and this is a major update
+* 2.0
+** DONE convert to distribute for packaging [7/7]
+   CLOSED: [2010-04-01 Thu 08:24]
+   - get rid of newvenvw and virtualenvwrapper virtualenvs and re-create
+   - [X] pavement.py to setup.py
+   - [X] sphinx conf.py needs to get version from setup.py somehow
+   - [X] separate rules for making website
+   - [X] installwebsite
+   - [X] register
+   - [X] test for installation
+   - [X] rename virtualenvwrapper_bashrc to virtualenvwrapperrc
+
+
+** DONE review virtualenv template feature
+   SCHEDULED: <2010-04-02 Fri> CLOSED: [2010-04-04 Sun 10:20]
+   - http://bitbucket.org/dhellmann/virtualenvwrapper/issue/28/environment-templates
+
+** plugin system for hooks
+   - http://bitbucket.org/dhellmann/virtualenvwrapper/issue/28/
+   - use Distribute/setuptools entry points
+   - [X] namespace package `virtualenvwrapper` to hold plugins I write, but
+     not required for other authors
+   - [X] bump version to 2, since the user script implementation is moving
+     and this is a major update
+
+*** DONE cli app to run the hooks
+    CLOSED: [2010-04-03 Sat 07:31]
+
+
+*** DONE "user script" plugin implementation
+    CLOSED: [2010-04-03 Sat 07:29]
+     - uses pkg_resources to get contents of hook scripts out of
+       python package and run them
+     - [X] move all/most existing hook execution here
+     - [X] handle both global & local hooks
+
+*** DONE how does cli app handle the "sourced" hook scripts
+    CLOSED: [2010-04-03 Sat 07:33]
+     - ability to `cd` into a specific directory, for example
+     - separate plugin points for "foo_run_hook" and
+       "foo_source_hook", handled differently by the calling script
+       - run hooks are executed first (implement in any language)
+       - source hooks are dumped to text files and then sourced
+         (implement in shell language)
+
+
+*** DONE expose each hook point as an entry point function [6/6]
+    CLOSED: [2010-04-03 Sat 07:34]
+   - [X] initialize
+     - during load of virtualenvwrapper.sh
+   - [X] mkvirtualenv [2/2]
+     - [X] pre
+     - [X] post
+   - [X] requirements
+     - automatically install packages based on requirements file
+       given to pip
+     - separate hook, or let a package just use postmkvirtualenv?
+     - if provide as a separate hook, run /before/ postmkvirtualenv
+     - let the postmkvirtualenv hook handle this as needed
+   - [X] activate [2/2]
+     - [X] pre
+     - [X] post
+   - [X] deactivate [2/2]
+     - [X] pre
+     - [X] post
+   - [X] rmvirtualenv [2/2]
+     - [X] pre
+     - [X] post
+
+
+*** DONE documentation for how to publish your own hooks [6/6]
+    CLOSED: [2010-04-04 Sun 10:19]
+    - user script implementation as example, since it will implement
+      every hook point
+   - [X] change setuptools to distribute
+   - [X] initialize
+   - [X] mkvirtualenv [2/2]
+     - [X] pre
+     - [X] post
+   - [X] activate [2/2]
+     - [X] pre
+     - [X] post
+   - [X] deactivate [2/2]
+     - [X] pre
+     - [X] post
+   - [X] rmvirtualenv [2/2]
+     - [X] pre
+     - [X] post
+
+
+*** DONE update documentation for user scripts
+    CLOSED: [2010-04-04 Sun 07:36]
+    - [X] make sure they are all included
+    - [X] table for each
+      - [X] global hook?
+      - [X] local hook?
+      - [X] argument(s)
+      - [X] sourced or run?
+
+
+*** DONE documentation of existing extensions
+    CLOSED: [2010-04-04 Sun 10:19]
+
+
+* TODO emacs desktop mode hooks
+   - release as separate project
+
+* 2.1
+
+** TODO check if plugin enabled per-environment
+   - convenience function to check $VIRTUAL_ENV/.wrapperrc to see if a
+     plugin is enabled
+   - each plugin must do this itself
+   - convenience function for plugin to enable itself during
+     postmkvirtualenv hook (probably based on user interaction)
+
+
+** TODO load plugin settings
+   - convenience function to load plugin settings from
+     $VIRTUAL_ENV/.wrapperrc
+
 
 ** TODO how to specify execution order between plugin providers?
-    - plugins could provide a "phase" function for sorting
-      - return an integer, let the plugin author community sort out the
-        ranges
-    - alphabetical by plugin name
-    - undefined
-
-** TODO "user script" plugin implementation
-    - uses pkg_resources to get contents of hook scripts out of
-      python package and run them
-    - move all/most existing hook execution here
-    - handles both global & local hooks
-
-** TODO cli app to run the hooks
-
-** TODO how does cli app handle the "sourced" hook scripts
-    - ability to `cd` into a specific directory, for example
-    - separate plugin points for "foo_run_hook" and
-      "foo_source_hook", handled differently by the calling script
-      - run hooks are executed first (implement in any language)
-      - source hooks are dumped to text files and then sourced
-        (implement in shell language)
-
-** TODO expose each hook point as an entry point function [0/5]
-  - [ ] requirements
-    - automatically install packages based on requirements file
-      given to pip
-    - separate hook, or let a package just use postmkvirtualenv?
-    - if provide as a separate hook, run /before/ postmkvirtualenv
-  - [ ] mkvirtualenv [0/2]
-    - [ ] pre
-    - [ ] post
-  - [ ] activate [0/2]
-    - [ ] pre
-    - [ ] post
-  - [ ] deactivate [0/2]
-    - [ ] pre
-    - [ ] post
-  - [ ] rmvirtualenv [0/2]
-    - [ ] pre
-    - [ ] post
-
-** TODO documentation for how to publish your own hooks
-
-
-* TODO add pre/post hooks for cpvirtualenv
-  - add new ones or just invoke existing hooks?
+   - options
+     - plugins could provide a "phase" function for sorting
+       - return an integer, let the plugin author community sort out the
+         ranges
+     - alphabetical by plugin name
+     - undefined
+   - left as undefined for now
+
+
+
+** TODO add pre/post hooks for cpvirtualenv
+   - add new ones or just invoke existing hooks?