import okhttp3.Headers.Companion.headersOf
import okhttp3.RequestBody.Companion.toRequestBody
import okhttp3.TestUtil.assumeNotWindows
import okhttp3.internal.RecordingOkAuthenticator
import okhttp3.internal.duplex.AsyncRequestBody
import okhttp3.internal.duplex.MockSocketHandler
import okhttp3.testing.PlatformRule
import okio.BufferedSink
import org.junit.jupiter.api.AfterEach
import org.junit.jupiter.api.Assertions.assertTrue

        TestRule rule2 = new TestRule("rule2", false);
        TestRule rule3 = new TestRule("rule3", true);

        ruleManager.addRule(rule1);
        ruleManager.addRule(rule2);
        ruleManager.addRule(rule3);

        assertTrue(ruleManager.hasRule(rule1));
        assertTrue(ruleManager.hasRule(rule2));
        assertTrue(ruleManager.hasRule(rule3));
        assertEquals(3, ruleManager.getRuleCount());
    }

 * limitations under the License.
 */
package okhttp3.internal.duplex

import java.util.concurrent.BlockingQueue
import java.util.concurrent.LinkedBlockingQueue
import java.util.concurrent.TimeUnit.SECONDS
import okhttp3.MediaType
import okhttp3.RequestBody
import okio.BufferedSink
import org.junit.jupiter.api.Assertions.assertTrue

/** A duplex request body that keeps the provided sinks so they can be written to later.  */

        TestRule rule2 = new TestRule("rule2", sharedProcessor, false);
        TestRule rule3 = new TestRule("rule3", sharedProcessor, true);

        // Same processor instance
        assertSame(sharedProcessor, rule1.getResponseProcessor());
        assertSame(sharedProcessor, rule2.getResponseProcessor());
        assertSame(sharedProcessor, rule3.getResponseProcessor());

        // Different rule IDs

Nota que la variable `item` es uno de los elementos en la lista `items`.

Y aún así, el editor sabe que es un `str` y proporciona soporte para eso.

#### Tuple y Set

Harías lo mismo para declarar `tuple`s y `set`s:

//// tab | Python 3.9+

```Python hl_lines="1"
{!> ../../docs_src/python_types/tutorial007_py39.py!}
```

////

//// tab | Python 3.8+

        rule2.setMatchResult(true);

        TestAbstractRule rule3 = new TestAbstractRule();
        rule3.crawlerContainer = container;
        rule3.setRuleId("rule3");
        rule3.setMatchResult(false);

        // Register in order
        rule1.register(0);
        rule2.register(1);
        rule3.register(2);

        // Get matching rule

Notice that the variable `item` is one of the elements in the list `items`.

And still, the editor knows it is a `str`, and provides support for that.

#### Tuple and Set { #tuple-and-set }

You would do the same to declare `tuple`s and `set`s:

//// tab | Python 3.9+

```Python hl_lines="1"
{!> ../../docs_src/python_types/tutorial007_py39.py!}
```

////

//// tab | Python 3.8+

Observe que a variável `item` é um dos elementos da lista `items`.

E, ainda assim, o editor sabe que é um `str` e fornece suporte para isso.

#### Tuple e Set

Você faria o mesmo para declarar `tuple`s e `set`s:

//// tab | Python 3.9+

```Python hl_lines="1"
{!> ../../docs_src/python_types/tutorial007_py39.py!}
```

////

//// tab | Python 3.8+

#### تاپل و ست

برای تعریف `tuple`ها و `set`ها هم همین کار رو می‌کنی:

//// tab | Python 3.9+

```Python hl_lines="1"
{!> ../../docs_src/python_types/tutorial007_py39.py!}
```

////

//// tab | Python 3.8+

```Python hl_lines="1  4"
{!> ../../docs_src/python_types/tutorial007.py!}
```

////

یعنی:

И все же редактор знает, что это `str`, и поддерживает это.

#### `Tuple` и `Set`

Вы бы сделали то же самое, чтобы объявить `tuple` и `set`:

{* ../../docs_src/python_types/tutorial007.py hl[1,4] *}


Это означает:

* Переменная `items_t` является `tuple` с 3 элементами: `int`, другим `int` и `str`.
* Переменная `items_s` является `set` и каждый элемент имеет тип `bytes`.