Re: Contribute to Django - Python 3 or Python 2

[premdjango]

Thanks Michael, That was the confusion. 
I will go ahead with Python 3.

On Tuesday, June 28, 2016 at 7:45:02 PM UTC-4, premdjango wrote:
>
> Hello,
> Im trying to contribute to Django project and started with this document.
>
> https://docs.djangoproject.com/en/dev/intro/contributing/
>
> Here in couple of places I see Python3 is being used but in most places 
> python2 is used.
>
> Should I use Python 3 or Python 2?
>
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-users+unsubscr...@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at https://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/e772e9e9-55bc-437c-97a1-57804ea898d4%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Contribute to Django - Python 3 or Python 2

[Michal Petrucha]

On Sat, Jul 02, 2016 at 07:04:31AM -0700, premdjango wrote:
> Tim - 
> The reason I said its used in most of the places is because - 
> 
> for example:
> 
> pip install -e /path/to/your/local/clone/django/
> 
> 
> I would expect pip3 install of pip..

This looks like a bit of a misunderstanding. Using executables called
``pip``, or ``python``, means “use whatever version of Python you have
set as default,” which in some cases will be Python 2, but in other
cases Python 3. If you create your virtualenv or venv using Python
3.5, then running just ``pip`` or ``python`` with that venv activated
will indeed use Python 3.5.

Using ``pip3`` in the docs would be misleading, because it would
indicate that only Python 3 is supported, while you're free to choose
either Python 2 or Python 3 (at least for now).

Of course, many people (myself included) will recommend going with
Python 3, but 2.7 is still a valid choice.

Cheers,

Michal

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-users+unsubscr...@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at https://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/20160702175209.GY29054%40konk.org.
For more options, visit https://groups.google.com/d/optout.


signature.asc
Description: Digital signature

Re: Contribute to Django - Python 3 or Python 2

[premdjango]

Tim - 
The reason I said its used in most of the places is because - 

for example:

pip install -e /path/to/your/local/clone/django/


I would expect pip3 install of pip..




On Tuesday, June 28, 2016 at 7:45:02 PM UTC-4, premdjango wrote:
>
> Hello,
> Im trying to contribute to Django project and started with this document.
>
> https://docs.djangoproject.com/en/dev/intro/contributing/
>
> Here in couple of places I see Python3 is being used but in most places 
> python2 is used.
>
> Should I use Python 3 or Python 2?
>
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-users+unsubscr...@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at https://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/2c4b16e6-4fb2-4f2d-9f58-cf9253273489%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Contribute to Django - Python 3 or Python 2

[manikos]

+1 to all the above about using python 3. If I was contributing to Django I 
would definetely go with python 3. It's the future.

On Wednesday, June 29, 2016 at 2:45:02 AM UTC+3, premdjango wrote:
>
> Hello,
> Im trying to contribute to Django project and started with this document.
>
> https://docs.djangoproject.com/en/dev/intro/contributing/
>
> Here in couple of places I see Python3 is being used but in most places 
> python2 is used.
>
> Should I use Python 3 or Python 2?
>
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-users+unsubscr...@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at https://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/2affe2b3-5ca5-4f2d-90bd-ce46d0f5e5be%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Contribute to Django - Python 3 or Python 2

[ludovic coues]

https://docs.djangoproject.com/en/dev/releases/1.11/

"The Django 1.11.x series is the last to support Python 2. The next
major release, Django 2.0, will only support Python 3.5+."

But your point remains valid.
It make more sense to use python 3 as it will be the only option
available soon and some feature are already python 3 only, like
unicode support in username.

2016-06-30 18:36 GMT+02:00 Ricardo Daniel Quiroga :
> the next django releases don't suport python 2.x. if you want to use python
> 2.x in django use the 1.8 LTS
>
> http://stackoverflow.com/questions/28908401/does-django-have-any-plans-to-drop-support-for-python-2-in-the-near-future
> https://www.djangoproject.com/weblog/2015/jun/25/roadmap/
>
> 2016-06-28 22:13 GMT-03:00 Tim Graham :
>>
>> You can use either, but use Python 3. You can rely on the continuous
>> integration server to test your pull request on Python 2 and debug any
>> issues
>>
>> Can you given an example of "most places python2 is used"? In fact, the
>> tutorial says, "This tutorial assumes you are using Python 3."
>>
>> On Tuesday, June 28, 2016 at 7:45:02 PM UTC-4, premdjango wrote:
>>>
>>> Hello,
>>> Im trying to contribute to Django project and started with this document.
>>>
>>> https://docs.djangoproject.com/en/dev/intro/contributing/
>>>
>>> Here in couple of places I see Python3 is being used but in most places
>>> python2 is used.
>>>
>>> Should I use Python 3 or Python 2?
>>>
>>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "Django users" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to django-users+unsubscr...@googlegroups.com.
>> To post to this group, send email to django-users@googlegroups.com.
>> Visit this group at https://groups.google.com/group/django-users.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/django-users/a0539448-0019-40a2-b732-e2c44799877b%40googlegroups.com.
>>
>> For more options, visit https://groups.google.com/d/optout.
>
>
>
>
> --
>
> Ricardo Daniel Quiroga
>
> --
> You received this message because you are subscribed to the Google Groups
> "Django users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to django-users+unsubscr...@googlegroups.com.
> To post to this group, send email to django-users@googlegroups.com.
> Visit this group at https://groups.google.com/group/django-users.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/django-users/CAO2-wHa0Onh2Ng03sHUDOJAcz3BkLGASkWAkDcJkkF7U884GoA%40mail.gmail.com.
>
> For more options, visit https://groups.google.com/d/optout.



-- 

Cordialement, Coues Ludovic
+336 148 743 42

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-users+unsubscr...@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at https://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/CAEuG%2BTZRB90sL24dcvVFXpTWGYMXZJqWFUsHLsdJzuNn6ga2pA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Contribute to Django - Python 3 or Python 2

[Ricardo Daniel Quiroga]

the next django releases don't suport python 2.x. if you want to use python
2.x in django use the 1.8 LTS

http://stackoverflow.com/questions/28908401/does-django-have-any-plans-to-drop-support-for-python-2-in-the-near-future
https://www.djangoproject.com/weblog/2015/jun/25/roadmap/

2016-06-28 22:13 GMT-03:00 Tim Graham :

> You can use either, but use Python 3. You can rely on the continuous
> integration server to test your pull request on Python 2 and debug any
> issues
>
> Can you given an example of "most places python2 is used"? In fact, the
> tutorial says, "This tutorial assumes you are using Python 3."
>
> On Tuesday, June 28, 2016 at 7:45:02 PM UTC-4, premdjango wrote:
>>
>> Hello,
>> Im trying to contribute to Django project and started with this document.
>>
>> https://docs.djangoproject.com/en/dev/intro/contributing/
>>
>> Here in couple of places I see Python3 is being used but in most places
>> python2 is used.
>>
>> Should I use Python 3 or Python 2?
>>
>>
>> --
> You received this message because you are subscribed to the Google Groups
> "Django users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to django-users+unsubscr...@googlegroups.com.
> To post to this group, send email to django-users@googlegroups.com.
> Visit this group at https://groups.google.com/group/django-users.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/django-users/a0539448-0019-40a2-b732-e2c44799877b%40googlegroups.com
> 
> .
>
> For more options, visit https://groups.google.com/d/optout.
>



-- 

Ricardo Daniel Quiroga

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-users+unsubscr...@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at https://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/CAO2-wHa0Onh2Ng03sHUDOJAcz3BkLGASkWAkDcJkkF7U884GoA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Contribute to Django - Python 3 or Python 2

[Tim Graham]

You can use either, but use Python 3. You can rely on the continuous 
integration server to test your pull request on Python 2 and debug any 
issues

Can you given an example of "most places python2 is used"? In fact, the 
tutorial says, "This tutorial assumes you are using Python 3."

On Tuesday, June 28, 2016 at 7:45:02 PM UTC-4, premdjango wrote:
>
> Hello,
> Im trying to contribute to Django project and started with this document.
>
> https://docs.djangoproject.com/en/dev/intro/contributing/
>
> Here in couple of places I see Python3 is being used but in most places 
> python2 is used.
>
> Should I use Python 3 or Python 2?
>
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-users+unsubscr...@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at https://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/a0539448-0019-40a2-b732-e2c44799877b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Contribute to Django - Python 3 or Python 2

[Farhan Khan]

I switched from Python2 to Python3 because I needed my Django code to fire 
off some TLSv1.2 code, that python2 could not do. I barely notice the 
difference between the two except in very small syntax differences. When I 
switched from python2 to python3, I literally did this:

find ./ -name "*.py" -exec 2to3 -w {} \;

And everything worked :)

I found it to have a more profound impact in other frameworks, such as 
Twisted or any type of socket programming, where you need to worry about 
encoding/decoding between unicode and binary strings.

On Tuesday, June 28, 2016 at 7:45:02 PM UTC-4, premdjango wrote:
>
> Hello,
> Im trying to contribute to Django project and started with this document.
>
> https://docs.djangoproject.com/en/dev/intro/contributing/
>
> Here in couple of places I see Python3 is being used but in most places 
> python2 is used.
>
> Should I use Python 3 or Python 2?
>
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-users+unsubscr...@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at https://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/9ca05994-67cc-4ee4-bddd-1bd912dbe406%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Contribute to Django - Python 3 or Python 2

[premdjango]

Hello,
Im trying to contribute to Django project and started with this document.

https://docs.djangoproject.com/en/dev/intro/contributing/

Here in couple of places I see Python3 is being used but in most places 
python2 is used.

Should I use Python 3 or Python 2?


-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-users+unsubscr...@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at https://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/55a3a553-72d9-4ad9-a3fa-f8ae11b30f40%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: GUI with web-browser using Django, Python 3

[Gergely Polonkai]

Hello,

you should walk through the Django tutorial[1] to get as idea on how to use
it. However, if this is the sole problem, I think Django is overkill, a
pure WSGI page would suffice.

Best,
Gergely

[1] https://docs.djangoproject.com/en/1.8/intro/tutorial01/
On 4 May 2015 17:28, "Aura"  wrote:

> I want to make a py-file by GUI. The GUI I want is based on web-browser
> (chrome, safari). So I use Django.
>
> The step-by-step idea is:
>
>1.
>
>I open the web-browser (as GUI, not to access internet). On the
>web-browser, there are two blanks and a "Generate" button, like
>
>a = ??
>
>filename = ??
>
>"Generate"
>
>(Here ?? is blank waiting for filling.)
>2.
>
>I fill like: a = [1,2,3,4], and filename = MyFile
>3.
>
>Click the "Generate" button
>
>Then A py-file "MyFile.py" is generated in an aimed folder. In the
>file, there is a python code
>
>a = [1,2,3,4]
>
>4.
>
>I plot a figure by
>
>import matplotlib.pyplot as plt
>plt.plot(a,a)
>
>It will generate a figure. I want this figure to be shown on the
>web-browser.
>
> I am using Python 3.
>
> Can you please show me how to do the 4 steps with Django? Thanks!
>
> --
> You received this message because you are subscribed to the Google Groups
> "Django users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to django-users+unsubscr...@googlegroups.com.
> To post to this group, send email to django-users@googlegroups.com.
> Visit this group at http://groups.google.com/group/django-users.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/django-users/d4a8bc37-a838-40a1-ac21-48ebd335d8d8%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-users+unsubscr...@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at http://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/CACczBUKG73S-DPWpMibwas3hSyPn4i%2Buj1p_o64bQfzmzZ8yFA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

GUI with web-browser using Django, Python 3

[Aura]

I want to make a py-file by GUI. The GUI I want is based on web-browser 
(chrome, safari). So I use Django.

The step-by-step idea is:

   1. 
   
   I open the web-browser (as GUI, not to access internet). On the 
   web-browser, there are two blanks and a "Generate" button, like
   
   a = ??
   
   filename = ??
   
   "Generate"
   
   (Here ?? is blank waiting for filling.)
   2. 
   
   I fill like: a = [1,2,3,4], and filename = MyFile
   3. 
   
   Click the "Generate" button
   
   Then A py-file "MyFile.py" is generated in an aimed folder. In the file, 
   there is a python code
   
   a = [1,2,3,4]
   
   4. 
   
   I plot a figure by
   
   import matplotlib.pyplot as plt
   plt.plot(a,a)
   
   It will generate a figure. I want this figure to be shown on the 
   web-browser.
   
I am using Python 3.

Can you please show me how to do the 4 steps with Django? Thanks!

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-users+unsubscr...@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at http://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/d4a8bc37-a838-40a1-ac21-48ebd335d8d8%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Near term disadvantages of Django+Python 3 stack?

[Russell Keith-Magee]

On Thu, Jan 10, 2013 at 9:47 PM, John  wrote:

> I understand that Django 1.5 RC supports Python 3, but for the sake of
> this question let's assume the 1.5 GA was already out.  As a developer, I
> want to use latest possible stable versions.  However, are there other
> implications for using a Py3 stack here?  For example, might I in the near
> future discover that 75% of the plugins which I might find useful will not
> yet be ported over for some time?  Are there any other gotchas that might
> make me want to stay with Python2.7 stack for a site I'll be building in a
> 6 month window?
>
> You've pretty much identified the two biggest problems.

1) We've done plenty of testing under Python 3, but there's no testing like
people actually using code in anger, so it's possible we will find small
problems with our Python 3 implementation after 1.5 is finalised. If we
find a particularly bad problem, we might be forced to break backwards
compatibility for Python 3 projects.

2) The wider community of Django apps/plugins/libraries hasn't been updated
for Python 3. You've said 75% - the number is probably closer to 95%. Of
course, this is a great opportunity for you to become a huge community
contributor by submitting pull requests for Python 3 updates.

Ultimately, the decision is yours.

If you're completely new to Django, you have really tight deadlines, or you
don't have a lot of confidence in the idea of diving into the internals of
Django and 3rd party apps, it's probably better to stick with Python 2.7
for the moment. Without knowing you or your circumstance or experience
level, I'd err on the side of caution and say this is the safer option.

However, if you're adventurous, you're not afraid of a few road bumps, and
you're willing to do a bit of extra work to help port 3rd party projects,
it would be a huge help to the Django community to see a live project
working on Python 3; and long term, your code will be ready for the future.

Yours,
Russ Magee %-)

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To post to this group, send email to django-users@googlegroups.com.
To unsubscribe from this group, send email to 
django-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-users?hl=en.

Re: Near term disadvantages of Django+Python 3 stack?

[Nikolas Stevenson-Molnar]

Python 3 support isn't considered ready for production use as of Django
1.5, as it hasn't received much real-world testing. For more info, see
this blog post by the dev team:
https://www.djangoproject.com/weblog/2012/aug/19/experimental-python-3-support/

_Nik

On 1/10/2013 5:47 AM, John wrote:
> I understand that Django 1.5 RC supports Python 3, but for the sake of
> this question let's assume the 1.5 GA was already out.  As a
> developer, I want to use latest possible stable versions.  However,
> are there other implications for using a Py3 stack here?  For example,
> might I in the near future discover that 75% of the plugins which I
> might find useful will not yet be ported over for some time?  Are
> there any other gotchas that might make me want to stay with Python2.7
> stack for a site I'll be building in a 6 month window?
>
> thanks!
> John
> -- 
> You received this message because you are subscribed to the Google
> Groups "Django users" group.
> To view this discussion on the web visit
> https://groups.google.com/d/msg/django-users/-/KCDiLybbFF0J.
> To post to this group, send email to django-users@googlegroups.com.
> To unsubscribe from this group, send email to
> django-users+unsubscr...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/django-users?hl=en.

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To post to this group, send email to django-users@googlegroups.com.
To unsubscribe from this group, send email to 
django-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-users?hl=en.

Near term disadvantages of Django+Python 3 stack?

[John]

I understand that Django 1.5 RC supports Python 3, but for the sake of this 
question let's assume the 1.5 GA was already out.  As a developer, I want 
to use latest possible stable versions.  However, are there other 
implications for using a Py3 stack here?  For example, might I in the near 
future discover that 75% of the plugins which I might find useful will not 
yet be ported over for some time?  Are there any other gotchas that might 
make me want to stay with Python2.7 stack for a site I'll be building in a 
6 month window?

thanks!
John

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/django-users/-/KCDiLybbFF0J.
To post to this group, send email to django-users@googlegroups.com.
To unsubscribe from this group, send email to 
django-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-users?hl=en.

Re: Django/ Python 3 - nervous about starting large project

[Vasil Vangelovski]

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 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 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/
> Python 2.6 code that needs to be ported?
>
> Any tips would be greatly appreciated.  Thanks.
>
> Tony
>
> >
>   


--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To post to this group, send email to django-users@googlegroups.com
To unsubscribe from this group, send email to 
django-users+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-users?hl=en
-~--~~~~--~~--~--~---

Re: Django/ Python 3 - nervous about starting large project

[Wayne Koorts]

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 with anything over 2.5.  I
really wanted to start using 2.6 but for some reason 2.5 seems to be
the most all-round compatible release of them all.  Also it seems that
most shared hosting providers use 2.5 by default.

Regards,
Wayne

--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To post to this group, send email to django-users@googlegroups.com
To unsubscribe from this group, send email to 
django-users+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-users?hl=en
-~--~~~~--~~--~--~---

Re: Django/ Python 3 - nervous about starting large project

[Streamweaver]

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 be around for a long time and transitions
in Python for me have always been much easier than in PHP.   If you're
fairly new to Python I doubt you're really venturing into the areas
that will be of major concern in a transition as well.

Good luck with it and Welcome to the Python end of the pool.

On Aug 5, 4:47 pm, snfctech  wrote:
> 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 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/
> Python 2.6 code that needs to be ported?
>
> Any tips would be greatly appreciated.  Thanks.
>
> Tony
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To post to this group, send email to django-users@googlegroups.com
To unsubscribe from this group, send email to 
django-users+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-users?hl=en
-~--~~~~--~~--~--~---

Re: Django/ Python 3 - nervous about starting large project

[snfctech]

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
> > 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/
> > Python 2.6 code that needs to be ported?
>
> First of all, welcome to the Python world, we'll do our best to make
> you feel comfortable here.
>
> You'll find that the Python crowd is very good at supporting legacy
> versions.  You'll see that you can even still download [1] Python
> 1.5.2 (April 1999!).  That's not to say that your favourite libraries
> will be available for such old versions, but many libraries still make
> releases for at least as far back as Python 2.3.  Also, I don't think
> you'll find that Python 3.x will introduce anything so radically new
> and innovative that it will severely limit what you can accomplish
> with older releases.  I'm working on a team starting a new (large)
> project now which we are basing around Python 2.5.
>
> Remember that Python has been around for a long time, since 1991, and
> releases like 2.5, 2.6 etc. are extremely mature and by now all of the
> common programming problems have already been encountered, solved and
> accomodated in the core and standard libraries.
>
> If you do decide to port your application to 3.x (think very carefully
> about it first - make sure that any of the associated libraries you
> require have mature 3.x releases) there are tools available to make
> the job a lot easier, like the 2to3 [2] script.
>
> [1]http://www.python.org/download/
> [2]http://www.python.org/doc/2.6/library/2to3.html
>
> HTH,
>
> Regards,
> Wayne Koortshttp://www.wkoorts.com
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To post to this group, send email to django-users@googlegroups.com
To unsubscribe from this group, send email to 
django-users+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-users?hl=en
-~--~~~~--~~--~--~---

Re: Django/ Python 3 - nervous about starting large project

[Wayne Koorts]

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/
> Python 2.6 code that needs to be ported?

First of all, welcome to the Python world, we'll do our best to make
you feel comfortable here.

You'll find that the Python crowd is very good at supporting legacy
versions.  You'll see that you can even still download [1] Python
1.5.2 (April 1999!).  That's not to say that your favourite libraries
will be available for such old versions, but many libraries still make
releases for at least as far back as Python 2.3.  Also, I don't think
you'll find that Python 3.x will introduce anything so radically new
and innovative that it will severely limit what you can accomplish
with older releases.  I'm working on a team starting a new (large)
project now which we are basing around Python 2.5.

Remember that Python has been around for a long time, since 1991, and
releases like 2.5, 2.6 etc. are extremely mature and by now all of the
common programming problems have already been encountered, solved and
accomodated in the core and standard libraries.

If you do decide to port your application to 3.x (think very carefully
about it first - make sure that any of the associated libraries you
require have mature 3.x releases) there are tools available to make
the job a lot easier, like the 2to3 [2] script.

[1] http://www.python.org/download/
[2] http://www.python.org/doc/2.6/library/2to3.html

HTH,

Regards,
Wayne Koorts
http://www.wkoorts.com

--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To post to this group, send email to django-users@googlegroups.com
To unsubscribe from this group, send email to 
django-users+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-users?hl=en
-~--~~~~--~~--~--~---

Re: Django/ Python 3 - nervous about starting large project

[Berco Beute]

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  wrote:
> 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 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/
> Python 2.6 code that needs to be ported?
>
> Any tips would be greatly appreciated.  Thanks.
>
> Tony
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To post to this group, send email to django-users@googlegroups.com
To unsubscribe from this group, send email to 
django-users+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-users?hl=en
-~--~~~~--~~--~--~---

Django/ Python 3 - nervous about starting large project

[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 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/
Python 2.6 code that needs to be ported?

Any tips would be greatly appreciated.  Thanks.

Tony

--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To post to this group, send email to django-users@googlegroups.com
To unsubscribe from this group, send email to 
django-users+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-users?hl=en
-~--~~~~--~~--~--~---

Re: Django - Python 3

[Malcolm Tredinnick]

On Sun, 2008-11-16 at 19:10 -0700, Leonel Nunez wrote:
> Hello:
> 
> As we know python 3 is comming in December:
> 
> http://www.python.org/download/releases/3.0/
> 
> Will there be many changes  for django with  python 3

Well, Django doesn't run out of the box on the Python 3 alphas, nor does
2to3.py convert it over cleanly to run on Python 3, so the answer is
"yes".

Since Django supports everything from Python 2.3 to 2.6, plus Jython,
PyPy and IronPython (in theory), we've got a few hairy corners. There's
been a few threads on django-developers about a patch that could make
Django run through 2to3.py more or less, as of a few months back. We'll
probably do something about that once Python 3 is released, but I wager
(not too much, though) it's unlikely that on day 1 of Python 3.0 being
released Django will work straight out of subversion. It's going to be a
miniscule portion of the total userbase, after all.

Regards,
Malcolm



--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To post to this group, send email to django-users@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-users?hl=en
-~--~~~~--~~--~--~---

Re: Django - Python 3

[James Bennett]

On Sun, Nov 16, 2008 at 8:10 PM, Leonel Nunez <[EMAIL PROTECTED]> wrote:
> Will there be many changes  for django with  python 3

As this is a fairly common question, *please* consider searching the
list archives for information.


-- 
"Bureaucrat Conrad, you are technically correct -- the best kind of correct."

--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To post to this group, send email to django-users@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-users?hl=en
-~--~~~~--~~--~--~---

Django - Python 3

[Leonel Nunez]

Hello:

As we know python 3 is comming in December:

http://www.python.org/download/releases/3.0/

Will there be many changes  for django with  python 3

Thank You

Leonel



--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To post to this group, send email to django-users@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-users?hl=en
-~--~~~~--~~--~--~---