|
|
@ -33,7 +33,7 @@ guarantee that this won't happen on Python 3. |
|
|
|
Few Users |
|
|
|
Few Users |
|
|
|
--------- |
|
|
|
--------- |
|
|
|
|
|
|
|
|
|
|
|
Although moving to Python 3 should be done someday, most people still uses |
|
|
|
Although moving to Python 3 should be done someday, most people still use |
|
|
|
Python 2 for now. As a result many of the problems you will encounter are |
|
|
|
Python 2 for now. As a result many of the problems you will encounter are |
|
|
|
probably hard to search for on the internet if they are Python 3 specific. |
|
|
|
probably hard to search for on the internet if they are Python 3 specific. |
|
|
|
|
|
|
|
|
|
|
@ -45,8 +45,8 @@ support Python 3 yet. |
|
|
|
|
|
|
|
|
|
|
|
Even if you start your project with knowing that all you will need is |
|
|
|
Even if you start your project with knowing that all you will need is |
|
|
|
supported by Python 3 you don't know what happens six months from now. |
|
|
|
supported by Python 3 you don't know what happens six months from now. |
|
|
|
But if you are familiar Python 3 and Flask extension, you can start porting |
|
|
|
But if you are familiar with Python 3 and Flask extension, you can start |
|
|
|
libraries on your own. |
|
|
|
porting libraries on your own. |
|
|
|
|
|
|
|
|
|
|
|
Recommendations |
|
|
|
Recommendations |
|
|
|
--------------- |
|
|
|
--------------- |
|
|
|