Yes, with python, you can web development :)
I recommend the django framework: https://www.djangoproject.com/
and Flask: https://flask.palletsprojects.com/
If you want to read more, I can recommend you this article:
https://www.imaginarycloud.com/blog/why-use-python-for-web-development/
These days python for web devlopment is increasingly becoming popular.
flask for frontend dev
RESOURCES:
https://www.youtube.com/watch?v=x_c8pTW8ZUc (CS50 harvard)
django for backend dev
RESOURCES:
https://www.youtube.com/watch?v=o0XbHvKxw7Y (michigan univ)Beautiful is better than ugly.
Explicit is better than implicit.
Simple is better than complex.
Complex is better than complicated.
Flat is better than nested.
Sparse is better than dense.
Readability counts.
Special cases aren't special enough to break the rules.
Although practicality beats purity.
Errors should never pass silently.
Unless explicitly silenced.
In the face of ambiguity, refuse the temptation to guess.
There should be one-- and preferably only one --obvious way to do it.
Although that way may not be obvious at first unless you're Dutch.
Now is better than never.
Although never is often better thn *right* now.
If the implementation is hard to explain, it's a bad idea.
If the implementation is easy to explain, it may be a good idea.
Namespaces are one honking great idea --let's do more of those!Yes, with python, you can web development :)
I recommend the django framework: https://www.djangoproject.com/
and Flask: https://flask.palletsprojects.com/
If you want to read more, I can recommend you this article:
https://www.imaginarycloud.com/blog/why-use-python-for-web-development/
These days python for web devlopment is increasingly becoming popular.
flask for frontend dev
RESOURCES:
https://www.youtube.com/watch?v=x_c8pTW8ZUc (CS50 harvard)
django for backend dev
RESOURCES:
https://www.youtube.com/watch?v=o0XbHvKxw7Y (michigan univ)Beautiful is better than ugly.
Explicit is better than implicit.
Simple is better than complex.
Complex is better than complicated.
Flat is better than nested.
Sparse is better than dense.
Readability counts.
Special cases aren't special enough to break the rules.
Although practicality beats purity.
Errors should never pass silently.
Unless explicitly silenced.
In the face of ambiguity, refuse the temptation to guess.
There should be one-- and preferably only one --obvious way to do it.
Although that way may not be obvious at first unless you're Dutch.
Now is better than never.
Although never is often better thn *right* now.
If the implementation is hard to explain, it's a bad idea.
If the implementation is easy to explain, it may be a good idea.
Namespaces are one honking great idea --let's do more of those!