Skip to content

Commit 279e798

Browse files
dhellmanndhellmann
committed
status update
1 parent af54241 commit 279e798

File tree

1 file changed

+133
-62
lines changed

1 file changed

+133
-62
lines changed

‎venv.org

Lines changed: 133 additions & 62 deletions
Original file line numberDiff line numberDiff line change
@@ -1,66 +1,137 @@
11
# Org-mode notes and task list
22

3-
* TODO convert to distribute for packaging [1/2]
4-
- get rid of newvenvw and virtualenvwrapper virtualenvs and re-create
5-
- [X] pavement.py to setup.py
6-
- [ ] sphinx conf.py needs to get version from setup.py somehow
7-
- [ ] separate rules for making website
8-
- [ ] installwebsite
9-
- [ ] register
10-
- [ ] test for installation
11-
12-
* plugin system for hooks
13-
- http://bitbucket.org/dhellmann/virtualenvwrapper/issue/28/
14-
- use Distribute/setuptools entry points
15-
- namespace package `virtualenvwrapper` to hold plugins I write, but
16-
not required for other authors
17-
- bump version to 2, since the user script implementation is moving
18-
and this is a major update
3+
* 2.0
4+
** DONE convert to distribute for packaging [7/7]
5+
CLOSED: [2010-04-01 Thu 08:24]
6+
- get rid of newvenvw and virtualenvwrapper virtualenvs and re-create
7+
- [X] pavement.py to setup.py
8+
- [X] sphinx conf.py needs to get version from setup.py somehow
9+
- [X] separate rules for making website
10+
- [X] installwebsite
11+
- [X] register
12+
- [X] test for installation
13+
- [X] rename virtualenvwrapper_bashrc to virtualenvwrapperrc
14+
15+
16+
** DONE review virtualenv template feature
17+
SCHEDULED: <2010-04-02 Fri> CLOSED: [2010-04-04 Sun 10:20]
18+
- http://bitbucket.org/dhellmann/virtualenvwrapper/issue/28/environment-templates
19+
20+
** plugin system for hooks
21+
- http://bitbucket.org/dhellmann/virtualenvwrapper/issue/28/
22+
- use Distribute/setuptools entry points
23+
- [X] namespace package `virtualenvwrapper` to hold plugins I write, but
24+
not required for other authors
25+
- [X] bump version to 2, since the user script implementation is moving
26+
and this is a major update
27+
28+
*** DONE cli app to run the hooks
29+
CLOSED: [2010-04-03 Sat 07:31]
30+
31+
32+
*** DONE "user script" plugin implementation
33+
CLOSED: [2010-04-03 Sat 07:29]
34+
- uses pkg_resources to get contents of hook scripts out of
35+
python package and run them
36+
- [X] move all/most existing hook execution here
37+
- [X] handle both global & local hooks
38+
39+
*** DONE how does cli app handle the "sourced" hook scripts
40+
CLOSED: [2010-04-03 Sat 07:33]
41+
- ability to `cd` into a specific directory, for example
42+
- separate plugin points for "foo_run_hook" and
43+
"foo_source_hook", handled differently by the calling script
44+
- run hooks are executed first (implement in any language)
45+
- source hooks are dumped to text files and then sourced
46+
(implement in shell language)
47+
48+
49+
*** DONE expose each hook point as an entry point function [6/6]
50+
CLOSED: [2010-04-03 Sat 07:34]
51+
- [X] initialize
52+
- during load of virtualenvwrapper.sh
53+
- [X] mkvirtualenv [2/2]
54+
- [X] pre
55+
- [X] post
56+
- [X] requirements
57+
- automatically install packages based on requirements file
58+
given to pip
59+
- separate hook, or let a package just use postmkvirtualenv?
60+
- if provide as a separate hook, run /before/ postmkvirtualenv
61+
- let the postmkvirtualenv hook handle this as needed
62+
- [X] activate [2/2]
63+
- [X] pre
64+
- [X] post
65+
- [X] deactivate [2/2]
66+
- [X] pre
67+
- [X] post
68+
- [X] rmvirtualenv [2/2]
69+
- [X] pre
70+
- [X] post
71+
72+
73+
*** DONE documentation for how to publish your own hooks [6/6]
74+
CLOSED: [2010-04-04 Sun 10:19]
75+
- user script implementation as example, since it will implement
76+
every hook point
77+
- [X] change setuptools to distribute
78+
- [X] initialize
79+
- [X] mkvirtualenv [2/2]
80+
- [X] pre
81+
- [X] post
82+
- [X] activate [2/2]
83+
- [X] pre
84+
- [X] post
85+
- [X] deactivate [2/2]
86+
- [X] pre
87+
- [X] post
88+
- [X] rmvirtualenv [2/2]
89+
- [X] pre
90+
- [X] post
91+
92+
93+
*** DONE update documentation for user scripts
94+
CLOSED: [2010-04-04 Sun 07:36]
95+
- [X] make sure they are all included
96+
- [X] table for each
97+
- [X] global hook?
98+
- [X] local hook?
99+
- [X] argument(s)
100+
- [X] sourced or run?
101+
102+
103+
*** DONE documentation of existing extensions
104+
CLOSED: [2010-04-04 Sun 10:19]
105+
106+
107+
* TODO emacs desktop mode hooks
108+
- release as separate project
109+
110+
* 2.1
111+
112+
** TODO check if plugin enabled per-environment
113+
- convenience function to check $VIRTUAL_ENV/.wrapperrc to see if a
114+
plugin is enabled
115+
- each plugin must do this itself
116+
- convenience function for plugin to enable itself during
117+
postmkvirtualenv hook (probably based on user interaction)
118+
119+
120+
** TODO load plugin settings
121+
- convenience function to load plugin settings from
122+
$VIRTUAL_ENV/.wrapperrc
123+
19124

20125
** TODO how to specify execution order between plugin providers?
21-
- plugins could provide a "phase" function for sorting
22-
- return an integer, let the plugin author community sort out the
23-
ranges
24-
- alphabetical by plugin name
25-
- undefined
26-
27-
** TODO "user script" plugin implementation
28-
- uses pkg_resources to get contents of hook scripts out of
29-
python package and run them
30-
- move all/most existing hook execution here
31-
- handles both global & local hooks
32-
33-
** TODO cli app to run the hooks
34-
35-
** TODO how does cli app handle the "sourced" hook scripts
36-
- ability to `cd` into a specific directory, for example
37-
- separate plugin points for "foo_run_hook" and
38-
"foo_source_hook", handled differently by the calling script
39-
- run hooks are executed first (implement in any language)
40-
- source hooks are dumped to text files and then sourced
41-
(implement in shell language)
42-
43-
** TODO expose each hook point as an entry point function [0/5]
44-
- [ ] requirements
45-
- automatically install packages based on requirements file
46-
given to pip
47-
- separate hook, or let a package just use postmkvirtualenv?
48-
- if provide as a separate hook, run /before/ postmkvirtualenv
49-
- [ ] mkvirtualenv [0/2]
50-
- [ ] pre
51-
- [ ] post
52-
- [ ] activate [0/2]
53-
- [ ] pre
54-
- [ ] post
55-
- [ ] deactivate [0/2]
56-
- [ ] pre
57-
- [ ] post
58-
- [ ] rmvirtualenv [0/2]
59-
- [ ] pre
60-
- [ ] post
61-
62-
** TODO documentation for how to publish your own hooks
63-
64-
65-
* TODO add pre/post hooks for cpvirtualenv
66-
- add new ones or just invoke existing hooks?
126+
- options
127+
- plugins could provide a "phase" function for sorting
128+
- return an integer, let the plugin author community sort out the
129+
ranges
130+
- alphabetical by plugin name
131+
- undefined
132+
- left as undefined for now
133+
134+
135+
136+
** TODO add pre/post hooks for cpvirtualenv
137+
- add new ones or just invoke existing hooks?

0 commit comments

Comments
 (0)