Latest comments
Here are the latest 20 comments posted to my site.
Back in the Django saddle – Marshall on December 5, 2011:
It's good to see that there may be more Django activity soon. As someone very interested in Django and wanting to learn it's been difficult as most of the information that I come across (blog posts, tutorials, whatever) seems to be from 2007... I may be looking in all the wrong places, but a lot of what I've run into on the web doesn't tell me that the framework has a very active community behind it currently. REALLY looking forward to seeing where things go. Oh, and I hope that doesn't come off as offensive to anyone.
Back in the Django saddle – Markus Gattol on December 3, 2011:
The current progress on Python 3 is great. Another thing that's on the radar for so long and which is actually ready for 1.4 is NoSQL support:
- https://groups.google.com/forum/#!topic/django-developers/o9PF07rOCaY
- https://github.com/django-nonrel (migration currently in progress)
Back in the Django saddle – Joe Tennies on December 2, 2011:
Jeff, if you've been listening to the django-dev mailing list. Python 3.x support is almost assuredly not going to land in 1.4, but there is discussion about potentially a preview release in 1.5. There's a couple tests failing (literally a couple) and most DB backends that are going to need to be tested (all but SQLITE), but it's sounding like it's getting very close.
Back in the Django saddle – Jeff Bauer on November 30, 2011:
One thing I wish I'd seen on your BDFL list ... Migration towards Python 3.x. Any thoughts?
Back in the Django saddle – Joe Tennies on November 30, 2011:
Isn't the pjax stuff basically Dajax (dajaxproject.com)? You may argue the implementation, but I love the part where all the ajax is implemented cross-library so it supports Prototype, jquery, mootools, and dojo. To me the Dajaxice (or something like it) is the missing part from Django.
Back in the Django saddle – Thomas Güttler on November 30, 2011:
Great news! Good luck!
Back in the Django saddle – Michael Trier on November 29, 2011:
Excellent news. I love your priorities. Good luck with it all!
Back in the Django saddle – BrettH on November 29, 2011:
You might want to consider Assembla Public Portfolio's for Django which would give you better than Trac ticketing and choice of svn/git/hg + wiki etc. Critically they have a RESTful api for export/import tickets, trac to assembla import, and static pages. Up until 6 months ago I hated their interface but it's really shaping up nicely now.
Back in the Django saddle – amd on November 29, 2011:
Fix transaction management. Not sure yet whether this only affects PostgreSQL, but I'm tired of the "idle in transaction" problem.
At least in some cases this is just changing the psycopg2 to autocommit which isn't the default.
Back in the Django saddle – Atte on November 29, 2011:
While you are looking at Jinja, you should consider taking Django templating more that way, especially with macros.
Another thing that has bugged me for quite a while is the lack of a good and simple enough default file and directory layout for Django projects. Semantically, do apps belong to the project or what?
Back in the Django saddle – Batisite on November 29, 2011:
Hi, good news,
The template performance is definitively an important issue because it can make the integration of projects using different template engine difficult or impossible.
Back in the Django saddle – Derek on November 29, 2011:
Re: "Please either spend some time tending to the commenting facility on djangobook.com, improve it, or remove it and point new users to the django-users list and official documentation."
I'd like to +1 this ... I learnt Django from djangobook.com, and I'd love to see it upgraded to the latest version (perhaps 1.4?) - but if you are not able/willing to do that, please just remove it and redirect users elsewhere. Its not very pleasant to see something so useful wither away bit-by-bit.
Back in the Django saddle – Paul on November 29, 2011:
Welcome back, was worried! but you are a bad daddy, you abandoned your child :)
Back in the Django saddle – anonymous on November 29, 2011:
Certainly seems like the project has gone stale. Glad to hear someone with motivation will be jumping back in. How about some movement towards compatibility with Python 3? (Now that it's been years and all...)
Back in the Django saddle – David on November 28, 2011:
The move to git is fantastic, without a BDFL simply impossible!
Back in the Django saddle – qoda on November 28, 2011:
Great news indeed, I've been using Django for 5 years and would like to say, Thank you!
Back in the Django saddle – Steven Hepting on November 28, 2011:
Great news Adrian! It seems like a lot of work to fit into one day a week, but even that is still excellent.
Back in the Django saddle – David W on November 28, 2011:
Claiming App Engine launched with Django is sort of like claiming Intel launched with the 80486 - it neatly omits the months of pain and suffering people discovered while using various hacks (painfully slow zip import comes immediately to mind) to get Django running on the original App Engine. AFAIK to this day Django's models aren't out of the box compatible with Datastore in any useful way.
On the other hand, it did launch with Django templates, which was a very useful addition to the original lineup (such a pity, though, that so many hoops must be jumped through to get this useful component running separately from the rest of the framework).
Congratulations nonetheless
Back in the Django saddle – Joe Tennies on December 6, 2011:
Okay. We are looking like we may have all tests passing under both SQLite and psycopg2! There's someone working on MySQL right now, but I think the driver is what is behind. Ditto for Oracle! I must admit that this is hugely exciting.
I believe the new thing being worked on is the stuff that required PIL. I may come back and make a run at the caching layers as I know I haven't tested them.
The big thing I see missing is a good "porting guide" to help people port their apps to Python 3, and the big thing needed for that is brave souls to try it and document their pain!