Dessa forma, cada projeto terá seu próprio ambiente virtual (diretório `.venv`) com seus próprios pacotes.

```mermaid
flowchart TB
    subgraph stone-project[philosophers-stone project]
        stone(philosophers-stone) --->|requires| harry-1
        subgraph venv1[.venv]
            harry-1[harry v1]
        end
    end

pkg testing, type CoverBlock struct, Stmts uint16
pkg testing, type TB interface, Error(...interface{})
pkg testing, type TB interface, Errorf(string, ...interface{})
pkg testing, type TB interface, Fail()
pkg testing, type TB interface, FailNow()
pkg testing, type TB interface, Failed() bool
pkg testing, type TB interface, Fatal(...interface{})
pkg testing, type TB interface, Fatalf(string, ...interface{})

¦EcDistœ ¨CSumAlgo ¨PartNums‘ ©PartETagsÀ©PartSizes‘Ñ iªPartASizes‘Ñ i¤SizeÑ i¥MTimeÓ É Ñ©XȧMetaSys ¼x-minio-internal-inline-dataÄ true§MetaUsr‚¤etagÙ 929f74acf4e3cc5de554¬content-type¸application/octet-stream¡v Î ñ ¤nullć VBŽ¤ šPsYUûàwÄ)â ´PÀ•èŸ‹Ç “]Tb€ Þ ¤Name¦bucket§CreatedÇ f*½‚!ê’H«LockEnabled°PolicyConfigJSONÄ µNotificationConfigXMÄ ²Life multisitea/data/disterasure/xl1/.minio.sys/buckets/bucket/.usage-cache.bin.bkp/xl.meta XL2 Æ } Ä$•Ä Ó É žÕô Ä ö / Å Qƒ¤Type ¥V2ObjÞ ¢IDÄ ¤DDirÄ emJ½¥ºI œú\¨U¯...

## 什麼是虛擬環境 { #what-are-virtual-environments }

解決套件都安裝在全域環境中的問題方法是為你所做的每個專案使用一個**虛擬環境**。

虛擬環境是一個**目錄**，與全域環境非常相似，你可以在其中針對某個專案安裝套件。

這樣，每個專案都會有自己的虛擬環境（`.venv` 目錄），其中包含自己的套件。

```mermaid
flowchart TB
    subgraph stone-project[專案 philosophers-stone]
        stone(philosophers-stone) --->|需要| harry-1
        subgraph venv1[.venv]
            harry-1[harry v1]
        end
    end

		}
		t.Log("Roundtrip:", time.Since(start))
	})
}

func TestSingleRoundtripNotReady(t *testing.T) {
	defer testlogger.T.SetLogTB(t)()
	errFatal := func(t testing.TB, err error) {
		t.Helper()
		if err != nil {
			t.Fatal(err)
		}
	}
	grid, err := SetupTestGrid(2)
	errFatal(t, err)
	remoteHost := grid.Hosts[1]
	local := grid.Managers[0]

	// 1: Echo

전역 환경에 모든 패키지를 두는 문제에 대한 해결책은 작업하는 **각 프로젝트마다 가상 환경**을 사용하는 것입니다.

가상 환경은 전역 환경과 매우 유사한 하나의 **디렉터리**이며, 프로젝트의 패키지를 설치할 수 있습니다.

이렇게 하면 각 프로젝트는 자체 가상 환경(`.venv` 디렉터리)과 자체 패키지를 갖게 됩니다.

```mermaid
flowchart TB
    subgraph stone-project[philosophers-stone project]
        stone(philosophers-stone) --->|requires| harry-1
        subgraph venv1[.venv]
            harry-1[harry v1]
        end
    end

// Using this interface, functionalities to be used in tests can be
// made generalized, and can be integrated in benchmarks/unit tests/go check suite tests.
type TestErrHandler interface {
	testing.TB
}

const (
	// ErasureSDStr is the string which is used as notation for Single node ObjectLayer in the unit tests.
	ErasureSDStr string = "ErasureSD"

aGaCVy3hUrlqio0hMVW3=","X-Minio-Internal-Server-Side-Encryption-S3-Kms-Key-Id":"my-minio-key","X-Minio-Internal-Server-Side-Encryption-S3-Kms-Sealed-Key":"IAAfALDbI9XcXXNfktnZ==","X-Minio-Internal-Server-Side-Encryption-S3-Sealed-Key":"IAAfAKht4pFV/Tb+K2vxGO7ei4mNGVa2hXRK/W8UZ4IWTNs+m3voBKgIJpBeCbJ0vVOm==","X-Minio-Internal-Server-Side-Encryption-Seal-Algorithm":"DAREv2-HMAC-SHA256","content-type":"application/octet-stream"}},{"Bucket":"buck1","Name":"go_113/src/cmd/trace/trace_test.go","UserDef...

pkg syscall (windows-amd64), const CTRL_SHUTDOWN_EVENT = 6
pkg syscall (windows-amd64), const CTRL_SHUTDOWN_EVENT ideal-int
pkg testing, method (*B) Cleanup(func())
pkg testing, method (*T) Cleanup(func())
pkg testing, type TB interface, Cleanup(func())
pkg unicode, const Version = "12.0.0"
pkg unicode, var Elymaic *RangeTable
pkg unicode, var Nandinagari *RangeTable
pkg unicode, var Nyiakeng_Puachue_Hmong *RangeTable

simple-url.com
simplesite.com
simplesite.com.br
simplesite.gr
simplesite.pl
sina
sinaapp.com
singles
siracusa.it
sirdal.no
sisko.replit.dev
site
site.rb-hosting.io
site.tb-hosting.com
site.transip.me
siteleaf.net
sj
sjc.br
sk
sk.ca
sk.eu.org
skanit.no
skanland.no
skaun.no
skedsmo.no
skedsmokorset.no
ski
ski.no
skien.no