Sin embargo, si solo usas `pip` directamente, los paquetes se instalarían en tu **entorno global de Python** (la instalación global de Python).

### El Problema

Entonces, ¿cuál es el problema de instalar paquetes en el entorno global de Python?

No entanto, se você usar `pip` diretamente, os pacotes serão instalados no seu **ambiente Python global** (a instalação global do Python).

### O Problema

Então, qual é o problema em instalar pacotes no ambiente global do Python?

        run: |
          mkdir -p maven-local
          if [ "${{ runner.os }}" = "Windows" ]; then
            unzip maven-dist/apache-maven-*-bin.zip -d maven-local
            # Get the name of the extracted directory
            MAVEN_DIR=$(ls maven-local)
            # Move contents up one level
            mv "maven-local/$MAVEN_DIR"/* maven-local/
            rm -r "maven-local/$MAVEN_DIR"
          else

            "The trust relationship between the primary domain and the trusted domain failed.",
            "The account used is a Computer Account. Use your global user account or local user account to access this server.",
            "The user must change his password before he logs on the first time.", "NT_STATUS_NOT_FOUND",
            "The referenced account is currently locked out and may not be logged on to.",

                    uhe.printStackTrace(log);
                }
            }
        }
        return def;
    }

    /**
     * Get the local host address configured for the client.
     *
     * @return the configured local InetAddress, or null if not configured
     */
    public static InetAddress getLocalHost() {
        final String addr = prp.getProperty("jcifs.smb1.smb.client.laddr");

    }

    @Test
    public void testCreateConnection() throws Exception {
        InetSocketAddress remote = new InetSocketAddress("localhost", 445);
        InetSocketAddress local = null;

        RdmaConnection connection = provider.createConnection(remote, local);
        assertNotNull(connection, "Connection should not be null");
        assertEquals(remote, connection.getRemoteAddress(), "Remote address should match");
    }

    @Test

      Inside ~/.m2/settings.xml:

      <localRepository>/path/to/local/repository</localRepository>
      ]]></configuration>
      <description>The ArtifactRepository instance referencing the local artifact
        repository.</description>
      <cliOptions>
        <cliOption>
          <key>-Dmaven.repo.local=/path/to/local/repo</key>
          <value>Override the local repository location on a per-build basis.</value>
        </cliOption>

     * That may introduce an extra class for each lambda (currently a dozen).
     */
    Logger local = logger;
    if (local != null) {
      return local;
    }
    synchronized (lock) {
      local = logger;
      if (local != null) {
        return local;
      }
      return logger = Logger.getLogger(loggerName);
    }
  }

 * {@linkplain LocalRepository local repositories} and
 * {@linkplain RemoteRepository remote repositories}.</p>
 *
 * <h2>Repository Resolution Process</h2>
 *
 * <p>When resolving dependencies, Maven follows this order:</p><ol>
 * <li>Check Local Repository: Maven first checks if the artifact is available in the local repository.</li>

    /**
     * Get transport connection, with local binding
     *
     * @param tc
     *            context to use
     * @param address the server address
     * @param port the port number
     * @param localAddr the local address to bind to
     * @param localPort the local port to bind to
     * @param hostName the server host name
     * @param exclusive