Jump to content

CPU: Intel Core i5 4690K @ 4.6Ghz CPU Cooler: Noctua NH-D15 GPU: GTX 1070 TI RAM: Crucial Ballistix Tactical 16GB (4x4) Mobo: ASUS Z97-PRO(Wi-Fi ac) PSU: Corsair RM Series RM750 Case: Fractal Design Define R4 no window

Link to post
Share on other sites

1 minute ago, Skreedles said:

...I saw that I was asking for opinions.

What do you want to do with it?

CPU: Intel Core i5 4690K @ 4.6Ghz CPU Cooler: Noctua NH-D15 GPU: GTX 1070 TI RAM: Crucial Ballistix Tactical 16GB (4x4) Mobo: ASUS Z97-PRO(Wi-Fi ac) PSU: Corsair RM Series RM750 Case: Fractal Design Define R4 no window

Link to post
Share on other sites

alot of it goes both ways with minor syntax changed, so either way you learn abit of both, but personally I dwell in 3 the most

Quote

print 'Hello World'

Quote

print('Hello World')

 

                     .
                   _/ V\
                  / /  /
                <<    |
                ,/    ]
              ,/      ]
            ,/        |
           /    \  \ /
          /      | | |
    ______|   __/_/| |
   /_______\______}\__}  

Spoiler

[I5-12600k | 32gb DDR5 6000 | RTX5070 | 2x1tb M.2]

 

[Ryzen 5 1600 | 16gb DDR4 3200 | GTX1030 | 4x 8tb HDD] 

 

Link to post
Share on other sites

Python 2 is being phased out with most of the libraries having already been converted to Python 3 so I'd suggest learning Python 3 unless you know that a library you will be working with does not yet have a Python 3 version. Although that would be rather unlikely and converting from one language to another is really easy so if you ever end up needing to use Python 2, it'd only take a few minutes to convert to it.

Link to post
Share on other sites

Do you already know that you will specifically need a library that is only compatible with Python 2, and you can't reasonably work around needing it?  Do you already know that you'll be doing most of your Python in a legacy or restricted environment (e.g., company computer) that only uses Python 2?  Do you already know that you'll be working largely with old code bases written in Python 2?

 

If yes to any of those, go with Python 2.  It's still commonly used in a lot of more industry-oriented cases because of the Python Software Foundation's decision to keep supporting Python 2 rather than trying to force a migration to Python 3 (this led to a sort of split among Python users).  Python 2 has only seen bug fixes and basic maintenance ever since 2.7 was released; no new features have been added in years.  But, if you know you'll be dealing with Python 2, then go with that.

 

In all other cases, Python 3.  It's where the active development is--new features being added, updates to more than just bug fixes and general housecleaning, etc.  It also cleans up some quirks of Python 2 and makes the language a bit more uniform.  Plus, pretty much every useful library has been ported to Python 3, with the exception of working for a company or on a code base that's still exclusively Python 2, there's not much reason to use the older version.

Link to post
Share on other sites

Python 3 definitely.

i5 4670k @ 4.2GHz (Coolermaster Hyper 212 Evo); ASrock Z87 EXTREME4; 8GB Kingston HyperX Beast DDR3 RAM @ 2133MHz; Asus DirectCU GTX 560; Super Flower Golden King 550 Platinum PSU;1TB Seagate Barracuda;Corsair 200r case. 

Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×