1 2013-12-08T00:17:49 *** jigar__
2 2013-12-08T02:11:16 *** sudo_dirk_
3 2013-12-08T02:16:36 *** sudo_dirk
4 2013-12-08T09:38:08 *** skathpalia
5 2013-12-08T09:59:31 *** jigar__
6 2013-12-08T10:06:19 *** jigar__
7 2013-12-08T10:24:29 *** jigar__
8 2013-12-08T11:05:14 *** skathpalia
9 2013-12-08T11:15:19 *** jigar__
10 2013-12-08T11:50:11 *** skathpalia
11 2013-12-08T12:00:33 *** skathpalia
12 2013-12-08T12:46:02 *** jigar__
13 2013-12-08T12:46:55 *** jigar54
14 2013-12-08T12:47:02 *** jigar__
15 2013-12-08T13:29:29 *** jigar54
16 2013-12-08T14:27:42 *** RogerHaase
17 2013-12-08T15:16:53 *** eSyr
18 2013-12-08T15:59:51 *** eSyr
19 2013-12-08T16:27:39 <ThomasWaldmann> RogerHaase: looking at the codereviews.
20 2013-12-08T16:33:57 <ThomasWaldmann> RogerHaase: are there some files missing in https://codereview.appspot.com/38680043/ ? it does from m import ... but there is no m there.
21 2013-12-08T16:38:09 <RogerHaase> ThomasWaldmann: m.py did not change after this cs that I pushed to my repo: https://codereview.appspot.com/31680043/
22 2013-12-08T16:40:41 <ThomasWaldmann> guess we need to change some names. currently naming is a bit confusing.
23 2013-12-08T16:41:27 <ThomasWaldmann> as quickinstall.py is rather a "Makefile replacement", call it make.py?
24 2013-12-08T16:41:56 <ThomasWaldmann> if it does not only install, but do all sorts of things...
25 2013-12-08T16:42:42 <ThomasWaldmann> the Menu class you have, does not show a menu, right? It is rather a container for all sorts of commands.
26 2013-12-08T16:44:36 <ThomasWaldmann> (django uses manage.py for similar stuff btw)
27 2013-12-08T16:45:38 <RogerHaase> m.py does all sorts of things and could be make.py, quickinstall.py still just installs. The issue I was trying to address is existing users continuing to do "python quickinstall.py"
28 2013-12-08T16:46:11 <ThomasWaldmann> well, as we need to change docs anyway, that is not an issue
29 2013-12-08T16:47:08 <ThomasWaldmann> confused people can be a severe issue, though
30 2013-12-08T16:47:46 <RogerHaase> ok, let me try to forget existing user problem and try one more time...
31 2013-12-08T16:48:03 <ThomasWaldmann> also think what needs to be where
32 2013-12-08T16:48:31 <ThomasWaldmann> is there a requirement to have 2 files? (currently quickinstall.py and m.py)
33 2013-12-08T16:48:59 <ThomasWaldmann> how do we decide what's going to be in there and what will be a "moin xxx" command?
34 2013-12-08T16:51:17 <ThomasWaldmann> "make.py install" could be the new quickinstall :)
35 2013-12-08T16:51:42 <RogerHaase> I think going back to a starting command of "python(2.7) makemoinmenu.py (maybe rename that to make menu) where that just creates the script "m" or "m.bat" and displays the menu. Then rename m.py to make.py or manage.py.
36 2013-12-08T16:52:07 <ThomasWaldmann> and then some student from india could add a "make.py install-with-broken-internet"
37 2013-12-08T16:52:22 <RogerHaase> :-D
38 2013-12-08T16:52:58 <ThomasWaldmann> also, please avoid cluttering the repo root
39 2013-12-08T16:53:35 <ThomasWaldmann> (if it's temporary, uncomitted files, some are ok, but keep committed files there low)
40 2013-12-08T16:54:44 <ThomasWaldmann> i am also thinking about whether we really want to deal with virtualenv activation and deactivation there
41 2013-12-08T16:55:09 <ThomasWaldmann> i see it might be comfortable for windows, so you can click on something
42 2013-12-08T16:55:33 <ThomasWaldmann> (and the commands needed on windows are quite longer / less comfortable to enter)
43 2013-12-08T16:55:56 <RogerHaase> hmm,putting the env outside of the repo root caused "env/Scripts/activate" to become "../some-really-long-page-to-the-env"
44 2013-12-08T16:56:13 <ThomasWaldmann> but otoh, there might be multiple venvs (I personally use py27 and pypy at least, for some projects additionally py33)
45 2013-12-08T16:56:41 <RogerHaase> ... so just being able to say "activate" without having to remember where the env is is very handy
46 2013-12-08T16:57:22 <RogerHaase> you have multiple env for one repo?
47 2013-12-08T16:57:22 <ThomasWaldmann> hmm, is there a way to tell whether one already is inside an active venv?
48 2013-12-08T16:57:28 <ThomasWaldmann> yes
49 2013-12-08T16:58:09 <ThomasWaldmann> if there was, you could just take the active one and not activate the default one
50 2013-12-08T16:59:16 <ThomasWaldmann> the usual workflow on linux btw is:
51 2013-12-08T16:59:24 <ThomasWaldmann> create virtualenv (once)
52 2013-12-08T16:59:34 <ThomasWaldmann> activate virtualenv
53 2013-12-08T16:59:59 <ThomasWaldmann> keep that shell/window open as long as you work on the stuff
54 2013-12-08T17:00:22 <ThomasWaldmann> deactivate or close window (maybe hours, days, weeks later)
55 2013-12-08T17:01:03 <ThomasWaldmann> it's not like one is activating/deactivating the env before/after each command
56 2013-12-08T17:01:46 <ThomasWaldmann> virtualenvwrapper adds some comfort to that, btw.
57 2013-12-08T17:02:06 <RogerHaase> I am thinking having multiple env for one repo excludes use of a simple menu system -- unless you rerun quickinstall each time you want to change the env
58 2013-12-08T17:02:52 <ThomasWaldmann> no, one only rarely creates venvs (to avoid the download/setup delay)
59 2013-12-08T17:03:35 <ThomasWaldmann> maybe check if there is a way to detect an active venv
60 2013-12-08T17:03:45 <RogerHaase> The download delay has been eliminated by moving the download cache to ~/...
61 2013-12-08T17:03:55 <ThomasWaldmann> if you just suppress all your "activate venv" code then, everybody is happy (hopefully)
62 2013-12-08T17:05:59 * ThomasWaldmann will give a small presentation about SSL/TLS today within a workshop at the local hackerspace
63 2013-12-08T17:09:09 <RogerHaase> even with the env inside the repo root the env\scripts\activate was a rather nerdy, esoteric command. source env/bin/activate was worse. Having to do either before using the menu makes it harder for non-python programmers
64 2013-12-08T17:10:50 <RogerHaase> with moin, activate, deactivate in the repo root, all the old commands will still work for the few people that have multiple env for one repo
65 2013-12-08T17:13:36 <RogerHaase> "m quickinstall" takes about 7 seconds on my pc
66 2013-12-08T17:19:12 <RogerHaase> OK, will think about multiple env and try rearranging/renaming one more time
67 2013-12-08T17:20:38 <RogerHaase> on the bright side, flask-script 0.6.6 fixes the 0.6.5 problem: https://bitbucket.org/thomaswaldmann/moin-2.0/issue/389/unrecognized-arguments-s-i-flask-script
68 2013-12-08T17:29:01 * ThomasWaldmann gtg / bbl (sorry)
69 2013-12-08T18:50:06 *** tah
70 2013-12-08T18:54:25 *** ThomasAH
71 2013-12-08T19:40:50 *** RogerHaase1
72 2013-12-08T19:41:41 *** RogerHaase
73 2013-12-08T19:41:56 *** RogerHaase1
74 2013-12-08T20:27:48 *** knowing42
75 2013-12-08T20:28:15 <knowing42> Hi my name is arnav kumar agrawal.
76 2013-12-08T20:28:24 <knowing42> I would like to conribute to moin moin wiki
77 2013-12-08T20:28:32 <knowing42> can anybody guide me how to start.
78 2013-12-08T20:36:18 *** knowing42
79 2013-12-08T21:36:00 *** RogerHaase1
80 2013-12-08T22:13:51 *** RogerHaase1
81