Live data from Hacker News

Django 1.6 released

djangoproject.com

51–60 of 107 posts

Re: Django 1.6 released

#51

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?

I would recommend using 1.6 and South for now. 1.7 is at least nine months away, and who knows where the API will go in that time. You're probably better off developing a stable version of your project using 1.6/South, and then refactoring when 1.7 lands.

Re: Django 1.6 released

#52

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?

No: 1.7 is not stable and it's not like the current migration situation with South is a particularly large pain-point.

What I'd do is use South now and essentially rebase when you upgrade to 1.7 – ensure that your servers are current with South, remove it and start over with 1.7's built-in migrations.

Re: Django 1.6 released

#53
post #36

For those who works with designers or html people who don't use the command line, how do you collaborate with them with Django? For me it's a perpetual issue to get them up and running, commit/push with git, etc etc. Is there an easier solution? Basically, I'd like them to get started and be able to tweak the templates and css as effortless as possible. It's kind of very hard to have people working directly in templa…

We put together a vagrant script and a set of instructions specifically for front-end devs on Windows who might lack the bash-fu and Python skills needed to get a local setup.

Happy to share if you ping me.

Re: Django 1.6 released

#54
post #36

For those who works with designers or html people who don't use the command line, how do you collaborate with them with Django? For me it's a perpetual issue to get them up and running, commit/push with git, etc etc. Is there an easier solution? Basically, I'd like them to get started and be able to tweak the templates and css as effortless as possible. It's kind of very hard to have people working directly in templa…

Let them code things up as static HTML then add in your dynamic stuff after.

Re: Django 1.6 released

#55
post #36

For those who works with designers or html people who don't use the command line, how do you collaborate with them with Django? For me it's a perpetual issue to get them up and running, commit/push with git, etc etc. Is there an easier solution? Basically, I'd like them to get started and be able to tweak the templates and css as effortless as possible. It's kind of very hard to have people working directly in templa…

I also have this same problem. It's one of the things which has made me think about switching to web2py - you can edit templates and css, and do commits directly in the admin. There is something a bit crazy about it though. Alternatively I don't think it would be that difficult to put a decent JavaScript-based editor on a page and allow editing of certain files, combined with a way of running the collectstatic management command. Difficult enough for me to not have tried it though.

Re: Django 1.6 released

#56

Earlier quoted context omitted.

Well, apart from Fabric.

You may want to check out Invoke ( https://github.com/pyinvoke/invoke); it's the successor to Fabric, and it's Python 3 compatible.

For what I can see, Invoke is just a revamped version of Fabric’s task running components. Fabric 2.0 will "leverage Invoke for task running, leaving Fabric itself much more library oriented".

Re: Django 1.6 released

#57

It's a small change yet I'm really happy with it. > BooleanField no longer defaults to False It caused quite a few headaches. Boolean can't have default.

> Boolean can't have default.

I don't see the problem.

Re: Django 1.6 released

#59
post #36

For those who works with designers or html people who don't use the command line, how do you collaborate with them with Django? For me it's a perpetual issue to get them up and running, commit/push with git, etc etc. Is there an easier solution? Basically, I'd like them to get started and be able to tweak the templates and css as effortless as possible. It's kind of very hard to have people working directly in templa…

Let them code things up as static HTML then add in your dynamic stuff after.

It's good for the first time, but as you move forward it becomes really annoying to check the diffs and merge them back..

Re: Django 1.6 released

#60
post #42

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…

am a fan of strongly-typed languages

Nit-pick: suspect you are actually a fan of statically-typed languages. Python is a strongly-typed language, but not statically-typed.

(general easy way to tell them apart: in a statically-typed language, both the name and the value bound to it have a type, and those types must match; in a dynamically-typed language only the value has a type; in a weakly-typed language, operations on incompatible types are permitted, and they may be coerced for compatibility; in a strongly-typed language, operations on incompatible types are an error -- usually at compile-time or equivalent for statically-typed, usually run-time for dynamically-typed)

Post reply on HN