On Mar 17, 5:09 pm, "rubdabadub" <[EMAIL PROTECTED]> wrote > Now I also need to learn Python from scratch! Man! Python is a rather easy language to pick up. I suggest you start here: http://www.python.org/moin/BeginnersGuide
Learning python through Django is kind of like learning C++ via MFC. Well that over stating things a bit. Django uses some advanced features of the language to get some of its work done. The end result is some of it appears to work by magic. This is not that big a deal, but I have seen it trip a few people up. Don't get too bogged down in trying to do things the 'python' or 'Django' way. > 1. How about deployment? Capistrano works with django i mean you can > make so called recipe but is there anything like that in python > world.. NOTE: don't get overwhelmed reading these sites, they are best used as reference or for when you are interested in solving a specific problem. Python has the cheezeshop for python modules, and packages called eggs (think RedHat RPM). http://cheeseshop.python.org/ There is also the ActiveState python cookbook repository: http://aspn.activestate.com/ASPN/Cookbook/Python/ As you noted Capistrano works with django, and the djangosnippet people are working on getting something integrated: http://www.djangosnippets.org/snippets/ The main django wiki site also has many many many pages and links to different django apps ready to plug in. > 2. How about "consuming XML" i didn't find much docs about it. I would > like to edit OPML files via the django-admin. My apps has some > database stuff but mostly I am playing 90% of the time with XML files > and 10% with a db. The best XML processing library in python is ElementTree. It comes with Python2.5 and can be downloaded seperatly for older python releases. You wont find much about consuming XML, generating PDF's, working with images, etc. in the Django docs, because there are standard python modules for dealing with those problems. The python standard library is extensive and so is the cheeseshop. There is a firefox sidebar for the python docs which I use regularly: http://www.edgewall.org/python-sidebar/html/toc-tutorial.html Unfortunately Ruby is becoming synonymous with RoR which is a huge injustice to the language. It means that there is allot of language documentation in the RoR docs (what there are of them). That isn't the case with Django so sometimes it can be confusing to people who have never seen Python before. It can be hard to discern which things are part of the language, the standard libraries, and what is part of Django. Luckily the documentation for all of these is fantastic and the community help is incredible. > 3. There are plenty of python programs out there that is off my > interest is there any "blog post" or anything that could guide me how > to djangofiy these scripts/apps. * Probably a dumb question due to > lack of python knowledge * James posts cover the links you need here. If there are pages dedicated to answering a question, it's defiantly not dumb. > 4. What about migrations i.e Schema Evolution is it in the trunk? Schema migration is a hot topic in general. There is work being done to make it easier to migrate your existing django code to a new schema. Currently you need to do this by hand. There is a wiki page for the progress of this feature: http://code.djangoproject.com/wiki/SchemaEvolution Django has schema introspection to create django code from an existing DB. http://www.djangoproject.com/documentation/legacy_databases/ > 5. Can I hook on to django SVN for production servers? is it a good > idea or should I go with released version? I prefer to use the svn trunk via svn:externals in my own svn project. This way I revision control the version of django I am using with the version of my code. It can also make it easier to upgrade a large number of production machines at once. I use buildbot for this, but there are a number of tools for doing an svn update on N networked machines. I have found the SVN trunk to be exceptionally stable. Django has a good set of standard tests which get run regularly, and I have my own tests for my sites. I recommend going this route. If you want to stick with a specific release of django you can. just set the svn:externals property to that release revision. The new features in django are too good to stick with the older releases. This will may change once 1.0 is released. > More ideas, pointers that will help me forget my loss (last 4 months) > are also welcome :-) Django has a very gradual learning curve over all. It is best to take it one step at a time and try not to do everything all at once. Start with something small and then build, adding features as you need. Start off with a basic model and get used to the django admin and the power of that interface. Then create some simple views of your data. Then add some custom forms. Then move on to login accounts, etc. Building, one step at a time will keep you from being overwhelmed by Django and Python. Spend some time in the django irc channel: #django on freenode.net There are alot of great people from all different skill levels. We all help each other out because no one can know everything. Hope this helps! -Doug --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
