Search Options

Results per page
Sort
Preferred Languages
Advance

Results 1 - 10 of 198 for brackets (1.97 sec)

  1. docs/en/docs/python-types.md

    As the type, put `list`.
    
    As the list is a type that contains some internal types, you put them in square brackets:
    
    {* ../../docs_src/python_types/tutorial006_py39.py hl[1] *}
    
    /// info
    
    Those internal types in the square brackets are called "type parameters".
    
    In this case, `str` is the type parameter passed to `list`.
    
    ///
    
    Registered: Sun Dec 28 07:19:09 UTC 2025
    - Last Modified: Wed Dec 17 20:41:43 UTC 2025
    - 15.6K bytes
    - Viewed (0)
  2. LICENSES/third_party/forked/gotestsum/LICENSE

          To apply the Apache License to your work, attach the following
          boilerplate notice, with the fields enclosed by brackets "[]"
          replaced with your own identifying information. (Don't include
          the brackets!)  The text should be enclosed in the appropriate
          comment syntax for the file format. We also recommend that a
    Registered: Fri Dec 26 09:05:12 UTC 2025
    - Last Modified: Fri Apr 01 18:49:15 UTC 2022
    - 11.1K bytes
    - Viewed (0)
  3. docs/de/llm-prompt.md

            «««
            ## Typhinweise und –annotationen { #type-hints-and-annotations }
            »»»
    
    3.2) Do not apply rule 3 to the untranslated part of the heading inside curly brackets, which you shall not translate.
    
    
    ### German instructions, when to use and when not to use hyphens in words (written in first person, which is you)
    
    Registered: Sun Dec 28 07:19:09 UTC 2025
    - Last Modified: Fri Dec 26 09:39:53 UTC 2025
    - 11.9K bytes
    - Viewed (0)
  4. LICENSE

          To apply the Apache License to your work, attach the following
          boilerplate notice, with the fields enclosed by brackets "[]"
          replaced with your own identifying information. (Don't include
          the brackets!)  The text should be enclosed in the appropriate
          comment syntax for the file format. We also recommend that a
    Registered: Sat Dec 20 11:21:39 UTC 2025
    - Last Modified: Mon Jan 11 04:26:17 UTC 2021
    - 11.1K bytes
    - Viewed (0)
  5. LICENSE

          To apply the Apache License to your work, attach the following
          boilerplate notice, with the fields enclosed by brackets "[]"
          replaced with your own identifying information. (Don't include
          the brackets!)  The text should be enclosed in the appropriate
          comment syntax for the file format. We also recommend that a
    Registered: Sat Dec 20 08:54:13 UTC 2025
    - Last Modified: Thu Feb 20 19:53:57 UTC 2020
    - 11.1K bytes
    - Viewed (0)
  6. LICENSE.txt

          To apply the Apache License to your work, attach the following
          boilerplate notice, with the fields enclosed by brackets "[]"
          replaced with your own identifying information. (Don't include
          the brackets!)  The text should be enclosed in the appropriate
          comment syntax for the file format. We also recommend that a
    Registered: Fri Dec 26 11:42:13 UTC 2025
    - Last Modified: Mon Jul 23 14:02:28 UTC 2012
    - 11.1K bytes
    - Viewed (0)
  7. LICENSES/vendor/github.com/containerd/ttrpc/LICENSE

          To apply the Apache License to your work, attach the following
          boilerplate notice, with the fields enclosed by brackets "[]"
          replaced with your own identifying information. (Don't include
          the brackets!)  The text should be enclosed in the appropriate
          comment syntax for the file format. We also recommend that a
    Registered: Fri Dec 26 09:05:12 UTC 2025
    - Last Modified: Fri May 08 04:49:00 UTC 2020
    - 11.2K bytes
    - Viewed (0)
  8. update-credits.sh

          To apply the Apache License to your work, attach the following
          boilerplate notice, with the fields enclosed by brackets "[]"
          replaced with your own identifying information. (Don't include
          the brackets!)  The text should be enclosed in the appropriate
          comment syntax for the file format. We also recommend that a
    Registered: Sun Dec 28 19:28:13 UTC 2025
    - Last Modified: Fri Aug 11 05:08:38 UTC 2023
    - 11.4K bytes
    - Viewed (0)
  9. LICENSE

          To apply the Apache License to your work, attach the following
          boilerplate notice, with the fields enclosed by brackets "[]"
          replaced with your own identifying information. (Don't include
          the brackets!)  The text should be enclosed in the appropriate
          comment syntax for the file format. We also recommend that a
    Registered: Sat Dec 20 09:19:18 UTC 2025
    - Last Modified: Tue May 08 21:35:34 UTC 2018
    - 11.1K bytes
    - Viewed (0)
  10. LICENSE

          To apply the Apache License to your work, attach the following
          boilerplate notice, with the fields enclosed by brackets "[]"
          replaced with your own identifying information. (Don't include
          the brackets!)  The text should be enclosed in the appropriate
          comment syntax for the file format. We also recommend that a
    Registered: Sat Dec 20 13:04:59 UTC 2025
    - Last Modified: Mon Jan 11 04:30:09 UTC 2021
    - 11.1K bytes
    - Viewed (0)
Back to top