Εγκαταστήστε το Django (δείτε το άρθρο οδηγός εγκατάσταση).
Περιηγηθείτε μέσα στον οδηγό μας.
Δείτε το υπόλοιπο documentation του Django και ρωτήστε την κοινότητα αν έχετε κάποιο πρόβλημα.
Django requires Python. See the table in the next question for the versions of\nPython that work with each version of Django. Other Python libraries may be\nrequired for some use cases, but you’ll receive an error about them as they’re\nneeded.
\nFor a development environment – if you just want to experiment with Django –\nyou don’t need to have a separate web server installed or database server.
\nDjango comes with its own lightweight development server.\nFor a production environment, Django follows the WSGI spec, PEP 3333, which\nmeans it can run on a variety of web servers. See Deploying Django for more information.
Django runs SQLite by default, which is included in Python installations.\nFor a production environment, we recommend PostgreSQL; but we also officially\nsupport MariaDB, MySQL, SQLite, and Oracle. See Supported Databases for more information.
\nDjango έκδοση | \nPython εκδόσεις | \n
|---|---|
3.2 | \n3.6, 3.7, 3.8, 3.9, 3.10 (added in 3.2.9) | \n
4.0 | \n3.8, 3.9, 3.10 | \n
4.1 | \n3.8, 3.9, 3.10, 3.11 (added in 4.1.3) | \n
4.2 | \n3.8, 3.9, 3.10, 3.11, 3.12 (added in 4.2.8) | \n
5.0 | \n3.10, 3.11, 3.12 | \n
Για κάθε έκδοση της Python, μόνο η τελευταία micro release (A.B.C) υποστηρίζεται επισήμως. Μπορείτε να βρείτε την τελευταία micro version για κάθε σειρά της Python στην επίσημη σελίδα της.
\nTypically, we will support a Python version up to and including the first\nDjango LTS release whose security support ends after security support for that\nversion of Python ends. For example, Python 3.9 security support ends in\nOctober 2025 and Django 4.2 LTS security support ends in April 2026. Therefore\nDjango 4.2 is the last version to support Python 3.9.
\nSince newer versions of Python are often faster, have more features, and are\nbetter supported, the latest version of Python 3 is recommended.
\nYou don’t lose anything in Django by using an older release, but you don’t take\nadvantage of the improvements and optimizations in newer Python releases.\nThird-party applications for use with Django are free to set their own version\nrequirements.
\nGenerally, if you’re using code in production, you should be using a\nstable release. The Django project publishes a full stable release\nevery eight months or so, with bugfix updates in between. These stable\nreleases contain the API that is covered by our backwards\ncompatibility guarantees; if you write code against stable releases,\nyou shouldn’t have any problems upgrading when the next official\nversion is released.
\n