For example:

{* ../../docs_src/metadata/tutorial001_1_py39.py hl[31] *}

## Metadata for tags { #metadata-for-tags }

You can also add additional metadata for the different tags used to group your path operations with the parameter `openapi_tags`.

It takes a list containing one dictionary for each tag.

Each dictionary can contain:

	// TargetStrip > 0 we strip the left most TargetStrip labels from the
	// DNS name.
	TargetStrip int `json:"targetstrip,omitempty"`

	// Group is used to group (or *not* to group) different services
	// together. Services with an identical Group are returned in
	// the same answer.
	Group string `json:"group,omitempty"`

	// Key carries the original key used during Put().
	Key string `json:"-"`

- **Consistency** - All languages have consistent access to the same APIs and ergonomics in the DSL.
- **Reduce the size of the Gradle distribution** - We no longer need to carry multiple standard libraries for different languages.

## Decision

We do not introduce new public API methods that include Groovy types in their signatures.
Existing Groovy methods will not be removed immediately.

## Status

ACCEPTED

  /** Returns the connection to use, which might be different from [connection]. */
  override fun handleSuccess(): RealConnection {
    call.client.routeDatabase.connected(route)

    val connection = this.connection!!
    connection.connectionListener.connectEnd(connection, route, call)

    // If we raced another call connecting to this host, coalesce the connections. This makes for
    // 3 different lookups in the connection pool!

        @Override
        public CredentialsInternal renew() {
            // Returns null to represent an implementation that could not renew
            return null;
        }
    }

    // Provide different implementation behaviors to a parameterized test
    static Stream<Arguments> implementations() {
        return Stream.of(Arguments.of("returns self", (Supplier<SmbRenewableCredentials>) SelfRenewingCreds::new, true, false),

import static org.junit.jupiter.api.Assertions.assertTrue;
import static org.mockito.Mockito.mock;
import static org.mockito.Mockito.when;

/**
 * Unit tests for the {@link ConsoleIcon} enum.
 * Tests icon rendering with different terminal charsets and fallback behavior.
 */
@DisplayName("ConsoleIcon")
class ConsoleIconTest {

    @Test
    @DisplayName("should return Unicode icons when terminal supports UTF-8")

	s2, err := os.Lstat(filepath.Dir(strings.TrimSuffix(path, "/")))
	if err != nil {
		return false
	}

	// If the directory has a different device as parent, then it is a mountpoint.
	ss1, ok1 := s1.Sys().(*syscall.Stat_t)
	ss2, ok2 := s2.Sys().(*syscall.Stat_t)
	return ok1 && ok2 &&
		// path/.. on a different device as path
		(ss1.Dev != ss2.Dev ||
			// path/.. is the same i-node as path - this check is for bind mounts.
			ss1.Ino == ss2.Ino)

### The Problem { #the-problem }

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

At some point, you will probably end up writing many different programs that depend on **different packages**. And some of these projects you work on will depend on **different versions** of the same package. 😱

/**
 * A domain name service that resolves IP addresses for host names. Most applications will use the
 * [system DNS service][SYSTEM], which is the default. Some applications may provide their own
 * implementation to use a different DNS server, to prefer IPv6 addresses, to prefer IPv4 addresses,
 * or to force a specific known IP address.
 *
 * Implementations of this interface must be safe for concurrent use.
 */
fun interface Dns {
  /**

            assertNotEquals(data1, null);
        }

        @Test
        @DisplayName("Should not be equal to different type")
        void testNotEqualToDifferentType() {
            assertNotEquals(data1, "string");
        }

        @Test
        @DisplayName("Should not be equal with different server")
        void testNotEqualDifferentServer() {