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?
Django 1.6 released
51–60 of 107 posts
Re: Django 1.6 released
#52If you were starting a new project today, would you use development version 1.7 in order to get Django Migrations instead of using South?
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
#53For 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…
Happy to share if you ping me.
Re: Django 1.6 released
#54For 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…
Re: Django 1.6 released
#55For 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…
Re: Django 1.6 released
#56Earlier 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.
Re: Django 1.6 released
#57It'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.
I don't see the problem.
Re: Django 1.6 released
#58Re: Django 1.6 released
#59For 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
#60Django 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…
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)