Ankita, why would a new project be forced to use Python 2 by a (probably
old) package? A well-maintained package must already have its Python 3
version.
Why can't we find an alternative package that uses Python 3? I am curious
about what package that is.
On Sun, Sep 22, 2019 at 12:32 AM Ankita Gu
Agreed - Mike's suggestion is a very sensible one. In the short term,
supporting 2 and 3 could be very useful, until you have the option to drop
support for 2.
https://six.readthedocs.io/
On Wednesday, 25 September 2019 01:00:44 UTC+2, Mike Dewhirst wrote:
>
> I think the original question wa
I think the original question was around backwards conversion of 3.x
code to 2.7.
I don't know of course because all my efforts have been forwards but I
believe the six module would be the easiest way backwards.
And I imagine you would simply run your unit tests in 2.7 and use the
six utilit
On Sat, Sep 21, 2019 at 8:32 PM Ankita Gupta
wrote:
> Not related to Django...
>
Then write to python-l...@python.org
--
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 em
Yes of course - I think RedHat will be continuing to support a python 2
environment because they haven't updated their own internal infrastructure
and also their distributions to python 3.
However - using one of those is still not very smart. The problem is that
all plugins have moved on. So Djang
Ha! How about perl? ;-)
On Tue, Sep 24, 2019 at 8:33 AM Nick Sarbicki wrote:
>
> I'm not convinced anyone could pay me enough to go back to Python 1...
>
>
> On Tue, Sep 24, 2019 at 1:32 PM Larry Martell wrote:
>>
>> You can get anyone to do anything for enough money.
>>
>> On Tue, Sep 24, 2019
I'm not convinced anyone could pay me enough to go back to Python 1...
On Tue, Sep 24, 2019 at 1:32 PM Larry Martell
wrote:
> You can get anyone to do anything for enough money.
>
> On Tue, Sep 24, 2019 at 8:30 AM Deep Sukhwani
> wrote:
> >
> > Thanks for the prompt reply. Did a quick cursory
You can get anyone to do anything for enough money.
On Tue, Sep 24, 2019 at 8:30 AM Deep Sukhwani wrote:
>
> Thanks for the prompt reply. Did a quick cursory check with Anaconda, I don't
> think Anaconda does it. In fact Anaconda has posted a few months ago about
> Python 2's EOL (End of Life)
Thanks for the prompt reply. Did a quick cursory check with Anaconda, I
don't think Anaconda does it. In fact Anaconda has posted a few months ago
about Python 2's EOL (End of Life) -
https://www.anaconda.com/end-of-life-eol-for-python-2-7-is-coming-are-you-ready/
Also, just did a quick look at th
Anaconda, Enthought, ActiveState, Red Hat and maybe others as well.
Also large companies can do their own support.
On Tue, Sep 24, 2019 at 8:11 AM Deep Sukhwani wrote:
>
> Wow, TIL there are companies selling support for Python 2? Never heard of it.
> So basically we are saying these companies w
Wow, TIL there are companies selling support for Python 2? Never heard of
it. So basically we are saying these companies will maintain there own
version of Python programming language which will continue to be maintained
as long as they have paid users for Python 2? I seriously doubt that. Or
may b
On Tue, Sep 24, 2019 at 4:15 AM Andréas Kühne
wrote:
>
> Official access isn't denied - and python 2 will probably be available. The
> problem is that you don't get any security fixes or any updates at all. That
> in itself is a major problem. If someone is saying that you need to use
> python
Official access isn't denied - and python 2 will probably be available. The
problem is that you don't get any security fixes or any updates at all.
That in itself is a major problem. If someone is saying that you need to
use python 2, I would strongly recommend them to not even think about it.
All
How Can I Use ['get', 'post', 'put', 'patch', 'delete', 'head', 'options',
'trace'] in One Class
On Sun, Sep 22, 2019 at 4:14 PM Ankita Gupta
wrote:
>
>
> On Saturday, September 21, 2019 at 11:07:21 PM UTC+5:30, Sipum wrote:
>>
>> Hi Ankita,
>>
>> In coming January, python 2 is going to retire.
On Saturday, September 21, 2019 at 11:07:21 PM UTC+5:30, Sipum wrote:
>
> Hi Ankita,
>
> In coming January, python 2 is going to retire. So better to use python 3.
>
Only official access is denied, we can still work in python2. Anyway thanks.
>
>
> Thanks
>
> On Sat, 21 Sep, 2019, 11:02 PM An
okay will get back to you after looking into it
On Sat, Sep 21, 2019 at 11:02 PM Ankita Gupta
wrote:
> Not related to Django, I have a project made in python3 but due to some
> package installation, i need to convert my project to python2. Is there any
> method or package to solve this?
>
> --
>
Hi Ankita,
In coming January, python 2 is going to retire. So better to use python 3.
Thanks
On Sat, 21 Sep, 2019, 11:02 PM Ankita Gupta,
wrote:
> Not related to Django, I have a project made in python3 but due to some
> package installation, i need to convert my project to python2. Is there a
Not related to Django, I have a project made in python3 but due to some
package installation, i need to convert my project to python2. Is there any
method or package to solve this?
--
You received this message because you are subscribed to the Google Groups
"Django users" group.
To unsubscribe
18 matches
Mail list logo
