[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Design: method in class or general function?

leam hall <leamhall at gmail.com> writes:

> I've wrestled with that discussion for a while and Python 3 loses every
> time.

The context of the thread you started was that you are a *newcomer* to
Python. Now you say you've considered Python 2 versus Python 3 many
times? What explains that apparent contradiction?

> There's literally no good reason for me to move to Python 3 earlier
> than mid-2020's. Please accept the fact that there are hundreds of
> thousands of servers, if not millions, running Python 2.x.

The servers can continue to run Python 2.x to support existing programs.
That doesn't go against the advice given.

The advice is that Python 3 is today the best choice for a Python
*newcomer*, and for writing *new* code such as in the example which
started this thread.

> Whether or not Python 3 has any neat cool stuff is irrelevant to those
> of us seeking to use Python to get today's work done.

If today's work *only* involves maintaining existing Python 2 legacy
programs, go right ahead.

That role will only shrink, though, so it's not a good thing to learn

For people learning Python, or for writing new programs in Python, it is
best to avoid the dead-end Python 2 altogether and use the current
version of Python 3.

 \      ?My interest is in the future, as I am going to spend the rest |
  `\                          of my life there.? ?Charles F. Kettering |
_o__)                                                                  |
Ben Finney