Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Django 1.6 released

djangoproject.com

Post reply on HN
Print view View original

41–50 of 107 posts

Re: Django 1.6 released

#41

Post by mhurron »

mbell wrote: post #25
masklinn wrote: post #8

Earlier quoted context omitted.

> Improved transaction management¶ > Django’s transaction management was overhauled. Database-level autocommit is now turned on by default. This makes transaction handling more explicit and should improve performance. The existing APIs were deprecated, and new APIs were introduced, as described in the transaction management docs. > Please review carefully the list of known backwards-incompatibilities to determine if…

It's hard to imagine using an ORM for anything high volume that just got around to adding (still very limited) connection pooling. I'd tend to think anyone overly concerned with performance would use SQLAlchemy, if they use any ORM at all.

> I'd tend to think anyone overly concerned with performance would use SQLAlchemy, if they use any ORM at all.

Or they did connection pooling outside the development framework.

Re: Django 1.6 released

#42

Post by EnderMB »

jroseattle wrote: post #38

Django is one of my favorite open-source projects. I owe the project a lot. Years ago, when I was a Microsoft-only shill (yeah, I'll say it), I knew how to build almost anything as long as something from Microsoft was under the covers. I was proud of my abilities, and in spite of the anti-MS crowd, I stood up for my platform and was a good developer. In 2006, I had a short two-week break from my startup job, and my w…

I'm quite interested in your experiences with Django, as I'm somewhat in the same boat. I'm a .NET developer, and while I love C#, am a fan of strongly-typed languages, and am quite fond of the .NET framework I have a soft spot for Python and especially Django.

Similarly, I had a few days and decided to go out of my comfort zone. A few days later I had written a blog script and had modified it to work with Google App Engine.

Do you use Python/Django in a professional setting now? If so, how did you find the full-time conversion?

Re: Django 1.6 released

#43

Post by ingrownpsyche »

mbell wrote: post #25
masklinn wrote: post #8

Earlier quoted context omitted.

> Improved transaction management¶ > Django’s transaction management was overhauled. Database-level autocommit is now turned on by default. This makes transaction handling more explicit and should improve performance. The existing APIs were deprecated, and new APIs were introduced, as described in the transaction management docs. > Please review carefully the list of known backwards-incompatibilities to determine if…

It's hard to imagine using an ORM for anything high volume that just got around to adding (still very limited) connection pooling. I'd tend to think anyone overly concerned with performance would use SQLAlchemy, if they use any ORM at all.

I think a lot of people might've been using an external connection pooler, eg pgpool.

Re: Django 1.6 released

#44

Post by jtchang »

One of the reasons I like Django so much is because of the community. This might seem rather meta but the comments in this thread are generally positive. Most Django users I know are well aware of its limitations and don't try to sugarcoat it if Django is not the right tool for the job. But overall I've found the community (and that of Python) pretty receptive.

Re: Django 1.6 released

#45

Post by commixon »

codonaut wrote: post #34
pydanny wrote: post #17

Earlier quoted context omitted.

Fabric isn't part of Django. There is nothing specific about Django in Fabric. In fact, the vast majority of my deployments do not use Fabric.

Do you use something in place of Fabric?

Paramiko could be a good example i think...

Re: Django 1.6 released

#46

Post by voorloopnul »

euroclydon wrote: post #29

If you were starting a new project today, would you use development version 1.7 in order to get Django Migrations instead of using South?

Hard to answer, django 1.7 will take at least 9 months before become stable. You have(at minimum) to consider the calendar of your project.

Re: Django 1.6 released

#47

Post by jroseattle »

EnderMB wrote: post #42
jroseattle wrote: post #38

Django is one of my favorite open-source projects. I owe the project a lot. Years ago, when I was a Microsoft-only shill (yeah, I'll say it), I knew how to build almost anything as long as something from Microsoft was under the covers. I was proud of my abilities, and in spite of the anti-MS crowd, I stood up for my platform and was a good developer. In 2006, I had a short two-week break from my startup job, and my w…

I'm quite interested in your experiences with Django, as I'm somewhat in the same boat. I'm a .NET developer, and while I love C#, am a fan of strongly-typed languages, and am quite fond of the .NET framework I have a soft spot for Python and especially Django. Similarly, I had a few days and decided to go out of my comfort zone. A few days later I had written a blog script and had modified it to work with Google App…

You're in the exact same spot I was. C# developer, completely enthralled with strongly-typed languages and OO development.

I definitely use Python professionally (and some Django, but that's not the critical stuff.) It's not the only thing I do, but it's another arrow in my quiver. It's really useful for generating applications that need to do a lot of stuff, but benefit from brevity in code. Django is actually more responsible for me learning Python and how to use it responsibly in a production environment. I knew how to write services in C# and Java that wouldn't be an administrative nightmare or cause pagers to go off at odd hours, so I needed to learn that with Python (turns out, it's not hard.)

As always, your mileage may vary. Nonetheless, lean toward finding a use for it in your operation, if only for experience. It's super practical, and to minimize transitional familiarity, go with IronPython. Works with all the VS IDEs.

Re: Django 1.6 released

#48

Post by valtron »

speg wrote: post #6
EliAndrewC wrote: post #2

The release notes can be found at https://docs.djangoproject.com/en/1.6/releases/1.6/ Personally, I'm happy that Python 3 is now officially supported, though in practice I haven't had an issues with using Django 1.5 with Python 3.

How is library support? I didn't have any issues with django 1.5 itself, but many of my favorite libraries weren't ready yet.

Here's a useful site showing Py3 support for packages: https://python3wos.appspot.com

Re: Django 1.6 released

#50

Post by calpaterson »

kot-behemoth wrote: post #16
pydanny wrote: post #12

Earlier quoted context omitted.

Django Packages lists 160 apps that work with Python 3. See https://www.djangopackages.com/python3/ From personal experience, most of the critical ones are compatible.

Well, apart from Fabric.

Fabric is on the way. Paramiko, the ssh library underlying Fabric, now has a Python 3 PR for which all tests pass: https://github.com/paramiko/paramiko/pull/233
Post reply on HN