> I initially was going to use git. I have recently joined Ubuntu > Accomplishments and they use bazaar which i have no idea on at > the moment so may proceed to use bazaar so I can reduce the > number of new things i need to learn currently and come back to > git later.
Both are worth learning. If you already know Subversion or CVS, then Bazaar and Mercurial are a bit easier to learn, IMHO. I find git a bit more powerful (particularly the ease with which you can make sub-file commits; this was what finally made git's "index" click for me as something valuable rather than something to grouse about). I've not probed the edges of it, but you may want to try the vcsplugin for Vim which facilitates using any of them. > As for frameworks I am still reviewing, I did like the looks of > Pyramid http://www.pylonsproject.org/ but I haven't dismissed > Django. Pyramid being already python 3 compliant and its > modularity and apparent freedom to let the user pick and choose > its components seesms attractive. Both are good frameworks. As you've picked up, Pylons/Pyramid was much more a-la-carte where you pick your various components; while Django is more monolithic (though, just being Python, nothing stops you from using other components). > I know pyramid features an overlay debugging toolbar on the > rendered webpage, how would you handle debuging? Both have debugging toolbars which are helpful. I tend to do the "print" style debugging to dump stuff to my devserver's console, but the debugging toolbars and Python's "logging" module are both helpful too. I used to try "import pdb; pdb.set_trace()" at areas of interest, but older versions of Django's runserver had problems (raw terminal control issues) with it--I don't know if that's improved. -tim -- You received this message from the "vim_use" maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php
