Django makes it easy to have a real, functional website while isolating what we'd actually be doing with the newbies into a view. They could see their work in the ultimate form that they might want to learn to execute in the future but only have to learn a little bit about it at first.
Does that make sense? Django would be the scaffolding within which we could see the actual result of using one of these APIs (Rdio, EchoNest, Spotify, etc), as opposed to just making a script that spit back results in text. A new programmer can't get as much context of what that's actually useful for, whereas seeing a website with functionality makes it obvious. On Wed, Aug 29, 2012 at 3:45 PM, Kevin Turner <[email protected]> wrote: > but why Django? In my mind, Django seems as far removed from Music Hack > as anything. > (Although I did catch Adrian Holovaty's talk on "Extracting Musical > Information from Sound" at pycon this year: > http://pyvideo.org/video/878/extracting-musical-information-from-sound > and I hear he has something to do with Django.) > > If you have project ideas already though, you must have made them > connect somehow. > _______________________________________________ > Portland mailing list > [email protected] > http://mail.python.org/mailman/listinfo/portland > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.python.org/pipermail/portland/attachments/20120829/8b94deac/attachment.html> _______________________________________________ Portland mailing list [email protected] http://mail.python.org/mailman/listinfo/portland
