## Dependencias Globales { #global-dependencies }

## Dependências globais { #global-dependencies }

## Globale Abhängigkeiten { #global-dependencies }

		//
		// GNU tar v1.27.1 applies global headers to subsequent records,
		// but does not do the following properly:
		//	* It does not treat an empty record as deletion.
		//	* It does not use subsequent global headers to update previous ones.
		//
		//	$ gnutar -tvf pax-global-records.tar
		//	---------- 0/0               0 2017-07-13 19:40 global1
		//	---------- 0/0               0 2017-07-13 19:40 file2

## Définir des dépendances globales { #global-dependencies }

Lee Hinman <******@****.***> 1492181453 -0600

Nevertheless, if you just use `pip` directly, the packages would be installed in your **global Python environment** (the global installation of Python).

### The Problem { #the-problem }

So, what's the problem with installing packages in the global Python environment?

Néanmoins, si vous utilisez simplement `pip` directement, les packages seraient installés dans votre environnement Python global (l’installation globale de Python).

### Le problème { #the-problem }

Alors, quel est le problème d’installer des packages dans l’environnement Python global ?

	return auth.Credentials{
		AccessKey: accessKey,
		SecretKey: secretKey,
	}
}

// Initialize KMS global variable after valiadating and loading the configuration.
// It depends on KMS env variables and global cli flags.
func handleKMSConfig() {
	present, err := kms.IsPresent()
	if err != nil {
		logger.Fatal(err, "Invalid KMS configuration specified")
	}

    /**
     *
     *
     * @return the global toolchains file
     * @since 3.3.0
     * @deprecated use {@link #getInstallationToolchainsFile()}
     */
    @Deprecated
    File getGlobalToolchainsFile();

    /**
     *
     * @param globalToolchainsFile the global toolchains file
     * @return this request
     * @since 3.3.0