많은 사용 사례에 더 잘 맞기 때문에 이전 대안들보다 선택되고 있습니다.

많은 개발자와 팀이 이미 자신의 프로젝트를 위해 **FastAPI**에 의존하고 있습니다(저와 제 팀도 포함해서요).

하지만 여전히, 앞으로 나올 개선 사항과 기능들이 많이 있습니다.

**FastAPI**의 미래는 밝습니다.

設定例:

* [VS Code](https://code.visualstudio.com/docs/python/environments#_select-and-activate-an-environment)
* [PyCharm](https://www.jetbrains.com/help/pycharm/creating-virtual-environment.html)

/// tip | 豆知識

この設定は通常、仮想環境を作成した際に**一度だけ**行います。

///

## 仮想環境の無効化 { #deactivate-the-virtual-environment }

プロジェクトの作業が終了したら、その仮想環境を**無効化**できます。

 * article on <a href="https://github.com/google/guava/wiki/ListenableFutureExplained">{@code
 * ListenableFuture}</a>.
 *
 * <p>The main purpose of {@code ListenableFuture} is to help you chain together a graph of
 * asynchronous operations. You can chain them together manually with calls to methods like {@link
 * Futures#transform(ListenableFuture, Function, Executor) Futures.transform}, but you will often

        assertEquals("/header.jsp", FessHtmlPath.path_HeaderJsp.getRoutingPath());
        assertEquals("/footer.jsp", FessHtmlPath.path_FooterJsp.getRoutingPath());
        assertEquals("/help.jsp", FessHtmlPath.path_HelpJsp.getRoutingPath());
    }

    @Test
    public void test_loginPaths() throws Exception {
        // Test login-related paths

    /** The path of the HTML: /header.jsp */
    HtmlNext path_HeaderJsp = new HtmlNext("/header.jsp");

    /** The path of the HTML: /help.jsp */
    HtmlNext path_HelpJsp = new HtmlNext("/help.jsp");

    /** The path of the HTML: /index.jsp */
    HtmlNext path_IndexJsp = new HtmlNext("/index.jsp");

    /** The path of the HTML: /login/index.jsp */

* Improves how 'kubectl' uses the terminal size when printing help and usage. ([#34502](https://github.com/kubernetes/kubernetes/pull/34502), [@fabianofranz](https://github.com/fabianofranz))

✨ [**FastAPI'ye sponsor olarak**](../help-fastapi.md#sponsor-the-author) ✨ bu şirketler, framework'ün ve **ekosisteminin** sağlıklı ve **sürdürülebilir** kalmasına yardımcı olur.

- Graduated Job's `ManagedBy` field...

- The kube-controller-manager managed signers can now have distinct signing certificates and keys.  See the help about `--cluster-signing-[signer-name]-{cert,key}-file`.  `--cluster-signing-{cert,key}-file` is still the default. ([#90822](https://github.com/kubernetes/kubernetes/pull/90822), [@deads2k](https://github.com/deads2k)) [SIG API Machinery, Apps and...

- If a bad flag is supplied to a kubectl command, only a tip to run `--help` is printed, instead of the usage menu.  Usage menu is printed upon running `kubectl command --help`. ([#82423](https://github.com/kubernetes/kubernetes/pull/82423), [@sallyom](https://github.com/sallyom))