Parallel tests, curious if folks are seeing a big difference in their existing testing suite?
On_commit sounds nice.
Django 1.9 Released
31–40 of 91 posts
Re: Django 1.9 Released
#32Is the Django team planning anything big for a 2.0 release?
Expanding a bit: the plan is that 2.0 just switches us to a new versioning system. The tl;dr is:
Versions start going 2.0, 2.1, 2.2, then 3.0, 3.1, 3.2, then 4.0, 4.1, etc.
Every X.2 is a long-term support release.
The deprecation cycle gets tweaked so that if you're on, say, 2.2 LTS and your codebase runs with no deprecation warnings, then you'll be able to just run as-is on 3.2 LTS. You can then clean up any deprecation warnings on 3.2, and you'd be good to go for 4.2 LTS, etc.
Re: Django 1.9 Released
#33Before anyone says something about Django not being hip enough for realtime stuff, just know that you can layer Pushpin (http://pushpin.org) in front of it. This may sound like a bandage but it's actually good design, regardless of programming language.
Disclaimer: author.
Re: Django 1.9 Released
#34This might be a good time to mention that Django is always trying to raise funds: https://www.djangoproject.com/fundraising/ The really quick turn around on tickets and pull requests is largely thanks to the Django Fellow, who is paid to manage the community. The last two or three releases have been on time because of the Fellow. The Fellow is funded via Django Software Foundation fundraising activities. If your comp…
Good call, this is very important! It's baffling that such a huge project, used by thousands of companies including at least one billion dollar unicorn, have such a hard time finding money to fund only one single developer. As a solo owner and happy Django user, I've donated what I could and encouraged others to do so but would love to find a solution to entice larger businesses to donate regularly.
What do you envision the solution looking like? A list of projects, with their updated runway, yearly budget, technology category and subcategory? Maybe create a watch list too and send notifications when the combination of their runway, yearly budget, and rate of donations reaches a critical point of becoming unsustainable. You can also have people give a range of what they'd be comfortable donating. When the project comes to a critical point, the first line of defense is to send notifications to larger businesses and as a project becomes more in danger the notifications get sent down the line to the people whom have smaller budgets.
Re: Django 1.9 Released
#35Before anyone says something about Django not being hip enough for realtime stuff, just know that you can layer Pushpin ( http://pushpin.org ) in front of it. This may sound like a bandage but it's actually good design, regardless of programming language. Disclaimer: author.
I'm a big fan of the design of pushpin - it's a really elegant solution for adding real-time features to frameworks like Django. I don't think it feels like a band-aid at all: for most web programming tasks, I'd much rather think in terms of a standard request/response cycle - it makes scaling with a shared-nothing architecture much easier to reason about.
Re: Django 1.9 Released
#36This might be a good time to mention that Django is always trying to raise funds: https://www.djangoproject.com/fundraising/ The really quick turn around on tickets and pull requests is largely thanks to the Django Fellow, who is paid to manage the community. The last two or three releases have been on time because of the Fellow. The Fellow is funded via Django Software Foundation fundraising activities. If your comp…
Good call, this is very important! It's baffling that such a huge project, used by thousands of companies including at least one billion dollar unicorn, have such a hard time finding money to fund only one single developer. As a solo owner and happy Django user, I've donated what I could and encouraged others to do so but would love to find a solution to entice larger businesses to donate regularly.
The Django Software Foundation has just hired a part time person to organise fundraising [0]. There is also discussion happening around the community about trying to find a sustainable way of funding open source projects and Django in particular.
Part of the problem is that it's hard to get companies to "donate" money. If they can purchase something like "support" or something else tangible, or "sponsorship" out of their advertising budgets, there may be more opportunities of gaining funding.
Thank you for donating though! Django gets a lot of their money from regular developers' pockets. I, personally, feel that bigger companies using Django to generate lots of revenue should be contributing a greater portion to support the stack that supports them.
[0] https://www.djangoproject.com/weblog/2015/nov/23/introducing...
Re: Django 1.9 Released
#37Before anyone says something about Django not being hip enough for realtime stuff, just know that you can layer Pushpin ( http://pushpin.org ) in front of it. This may sound like a bandage but it's actually good design, regardless of programming language. Disclaimer: author.
I didn't hear about Pushpin before, looks like a solid product, will definitely look into it. I'm not sure if that's a valid question, but how does the Pushpin compare to something like SwampDragon (http://swampdragon.net/), besides not being tied to Django?
Re: Django 1.9 Released
#38Earlier quoted context omitted.
Good call, this is very important! It's baffling that such a huge project, used by thousands of companies including at least one billion dollar unicorn, have such a hard time finding money to fund only one single developer. As a solo owner and happy Django user, I've donated what I could and encouraged others to do so but would love to find a solution to entice larger businesses to donate regularly.
The Django Software Foundation has just hired a part time person to organise fundraising [0]. There is also discussion happening around the community about trying to find a sustainable way of funding open source projects and Django in particular. Part of the problem is that it's hard to get companies to "donate" money. If they can purchase something like "support" or something else tangible, or "sponsorship" out of t…
Shame tbh. If they invest they could see their businesses doing even better.
Re: Django 1.9 Released
#39Earlier quoted context omitted.
Care to elaborate?
I've dabbled with both, and they suffer from the same kind of problem that all frameworks on top of dynamic languages suffer from. You essentially have to do all the checks that the compiler /should/ do for you, by using unit tests. Also, on large code bases, I now prefer having real refactoring support. I'd rather pick something on top of a compiler that is not brain dead. If I had to do python again, I'd use pyrami…
This is, of course, why nobody has ever bothered developing a unit-testing framework for a statically-typed language, and why it would have been impossible for the idea of automated refactorings to have originated in a dynamically-typed language.
Re: Django 1.9 Released
#40Not looking to start a fanboy-war here; but i would like to hear some opinions. If you were to start a new small to medium sized web app today, would choose Ruby on Rails or Django?
I'm shocked, frankly, at how lousy both are out-of-the-box. I just don't get why a simple CRUD app (which many/most apps are) has to be so difficult. I had trouble figuring out how to do email login on Django and just gave up. At first, Rails seems like it's going to be a lot better. I don't care for generating files. Don't like TDD. And found the migrations very confusing (if I make a typo in a field name, I delete the whole project and start over).
I can't believe this is the current state of web app development. I know everyone's moved on to Node and Angular, but, c'mon!