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?

[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.

[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:

[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/ 

--
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...@googlegroups.com.
To post to this group, send email to django...@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

[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.

> 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

[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.

[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:

[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

[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: