If you are writing your code in python 2.6 it will be easy to port it to
python 3 later. The backwards incompatible changes introduced in python
3 are not a good reason not to write you web application with django.
snfctech wrote:
> Hello.
>
> We are researching technologies to begin what may
Hi Tony,
> @Wayne: Thanks for the welcome. Why are you using 2.5 for your new/
> large project instead of 2.6?
It just seems to be the "sweet spot" release at the moment. I just
found that a few of the libraries I had been using, even in the last
couple of months, had some kind of problem
I came from the PHP world myself and am even doing some of it still
but I don't think what you're saying is of particular concern.
Even in PHP you have to worry about differences in PHP 4 and 5 and so
on so the concern itself isn't just a Python one. I can say that
support for Python 2.6 will
Thanks for the tips, Berco, Wayne.
@Wayne: Thanks for the welcome. Why are you using 2.5 for your new/
large project instead of 2.6?
Tony
On Aug 5, 2:22 pm, Wayne Koorts wrote:
> Hi Tony,
>
> > However, I'm nervous about the Python 3 situation. What if I start
> >
Hi Tony,
> However, I'm nervous about the Python 3 situation. What if I start
> building a large project based on Django/Python 2.6, and then a year
> or two down the road the project starts limping because of all of the
> cool new Python 3 modules coming out? And I've got a bunch of Django/
>
No worries, Python 2.6 will be actively supported for many, many years
to come and the differences between 2.6 and 3 are not that huge. You
can program for 2.6 while keeping in mind the code will be ported to 3
one day. It'll make a shift a breeze.
2B
On Aug 5, 10:47 pm, snfctech
Hello.
We are researching technologies to begin what may become a pretty
large intranet Dashboard project.
I'm a PHP developer, so the fact that Django uses Python doesn't give
me a head-start - but I've been wanting to consider it, because I am
interested in learning Python.
However, I'm
7 matches
Mail list logo