Search Options

Results per page
Sort
Preferred Languages
Advance

Results 1 - 4 of 4 for standard (0.15 sec)

  1. docs/fr/docs/history-design-future.md

    Par exemple, il était clair que l'idéal était de se baser sur les annotations de type Python standard.
    
    De plus, la meilleure approche était d'utiliser des normes déjà existantes.
    
    Plain Text
    - Registered: Sun May 05 07:19:11 GMT 2024
    - Last Modified: Fri Mar 22 01:42:11 GMT 2024
    - 4.9K bytes
    - Viewed (0)
  2. docs/de/docs/history-design-future.md

    Es war beispielsweise klar, dass es idealerweise auf Standard-Python-Typhinweisen basieren sollte.
    
    Der beste Ansatz bestand außerdem darin, bereits bestehende Standards zu nutzen.
    
    Plain Text
    - Registered: Sun May 05 07:19:11 GMT 2024
    - Last Modified: Sat Mar 30 18:10:48 GMT 2024
    - 4.8K bytes
    - Viewed (0)
  3. docs/en/docs/history-design-future.md

    For example, it was clear that ideally it should be based on standard Python type hints.
    
    Also, the best approach was to use already existing standards.
    
    So, before even starting to code **FastAPI**, I spent several months studying the specs for OpenAPI, JSON Schema, OAuth2, etc. Understanding their relationship, overlap, and differences.
    Plain Text
    - Registered: Sun May 05 07:19:11 GMT 2024
    - Last Modified: Fri Mar 22 01:42:11 GMT 2024
    - 4.1K bytes
    - Viewed (0)
  4. docs/tr/docs/history-design-future.md

    </blockquote>
    
    ## Araştırma
    
    Önceki alternatifleri kullanarak hepsinden bir şeyler öğrenip, fikirler alıp, bunları kendim ve çalıştığım geliştirici ekipler için en iyi şekilde birleştirebilme şansım oldu.
    
    Mesela, ideal olarak standart Python tip belirteçlerine dayanması gerektiği açıktı.
    
    Ayrıca, en iyi yaklaşım zaten mevcut olan standartları kullanmaktı.
    
    Plain Text
    - Registered: Sun May 05 07:19:11 GMT 2024
    - Last Modified: Fri Mar 22 01:42:11 GMT 2024
    - 4.7K bytes
    - Viewed (0)
Back to top