Hi everyone
I just started learning django. Question arises in my mind to write a
script, by using that script i wanted to jump django version 1.5.1 without
effecting my previous settings or effecting my application which is
currently running on django 1.4.3. Is it possible to do that? If yes tha
On Thu, Jun 20, 2013 at 3:17 AM, Deepak Sharma wrote:
> Hi everyone
>
> I just started learning django. Question arises in my mind to write a
> script, by using that script i wanted to jump django version 1.5.1 without
> effecting my previous settings or effecting my application which is
> curren
Okay but my situation is bit different. I am updating my university software.
That software is wrote in django version 1.3.1. My challenge was to run that
software on 1.5.1 and i completed that. As many things changed in django 1.5.1
like < direct_to_template > changed to < TemplateView> and fe
On Thursday, June 20, 2013 8:55:07 AM UTC+5:30, Deepak Sharma wrote:
>
> Okay but my situation is bit different. I am updating my university
> software. That software is wrote in django version 1.3.1. My challenge was
> to run that software on 1.5.1 and i completed that. As many things changed
Error analysis + reading documentation = solution. Well, most of the time
anyway. For help with errors, please share the errors?
On Tue, Aug 27, 2013 at 7:37 PM, Harjot Mann wrote:
>
>
> On Thursday, June 20, 2013 8:55:07 AM UTC+5:30, Deepak Sharma wrote:
>>
>> Okay but my situation is bit diff
On Tue, Aug 27, 2013 at 6:37 PM, Harjot Mann wrote:
> I also want to shift my app from django version 1.4.5 to 1.5.1. You are
> right there should be some script which automatically upgrades the version
> without affecting the application.
No, there shouldn't. You would spend more time writing
I've been using Django since v1.0, and when each major version is released,
I run through the release notes to see what I need to change. Russell is
correct that most things will work from one version to the next, but I like
to keep as up to date as possible to minimize my risk of hitting a
de
On 31/08/2013 02:14, Dan Gentry wrote:
I've been using Django since v1.0, and when each major version is
released, I run through the release notes to see what I need to change.
Russell is correct that most things will work from one version to the
next, but I like to keep as up to date as possib
The worst change i've had to make was a long time ago when we had to send
CSRF Token with Ajax calls because of a security exploit.
Had to write an entire regular expression and apply it to multiple template
files. Took perhaps 40 minutes.
However i can see some of the really old django snippets o
9 matches
Mail list logo
