excludedPackages.add("org.gradle.plugins.ide.idea.model");
        excludedPackages.add("org.gradle.api.tasks.testing.logging");

        // TODO - rename some incubating types to remove collisions and then remove these exclusions
        excludedPackages.add("org.gradle.plugins.binaries.model");

        // Exclude classes that were moved in a different package but the deprecated ones are not removed yet

Using these ideas, JWT can be used for way more sophisticated scenarios.

In those cases, several of those entities could have the same ID, let's say `foo` (a user `foo`, a car `foo`, and a blog post `foo`).

So, to avoid ID collisions, when creating the JWT token for the user, you could prefix the value of the `sub` key, e.g. with `username:`. So, in this example, the value of `sub` could have been: `username:johndoe`.

#include "tensorflow/core/platform/errors.h"

namespace tensorflow {
namespace gradients {
namespace {

// TODO(b/172558015): Using the pointer address as the identifier for the tensor
// may lead to collisions. Introduce another way to get a unique id for this
// tensor.
int64_t ToId(const AbstractTensorHandle* t) {
  return static_cast<int64_t>(reinterpret_cast<uintptr_t>(t));
}

   *       </ul>
   *   <li>another java.util.Set delegate implementation. In most modern JDKs, normal java.util hash
   *       collections intelligently fall back to a binary search tree if hash table collisions are
   *       detected. Rather than going to all the trouble of reimplementing this ourselves, we
   *       simply switch over to use the JDK implementation wholesale if probable hash flooding is

```

Чтобы узнать больше о Python-пакетах и модулях, прочитайте [официальную документацию Python о модулях](https://docs.python.org/3/tutorial/modules.html).

///

### Избегайте конфликтов имён { #avoid-name-collisions }

Мы импортируем подмодуль `items` напрямую, вместо того чтобы импортировать только его переменную `router`.

Это потому, что у нас также есть другая переменная с именем `router` в подмодуле `users`.

Um mehr über Python-Packages und -Module zu erfahren, lesen Sie [die offizielle Python-Dokumentation über Module](https://docs.python.org/3/tutorial/modules.html).

///

### Namenskollisionen vermeiden { #avoid-name-collisions }

Wir importieren das Submodul `items` direkt, anstatt nur seine Variable `router` zu importieren.

Das liegt daran, dass wir im Submodul `users` auch eine weitere Variable namens `router` haben.

Python Packages ve Modules hakkında daha fazlası için, [Python'ın Modules ile ilgili resmi dokümantasyonunu](https://docs.python.org/3/tutorial/modules.html) okuyun.

///

### İsim Çakışmalarını Önleyin { #avoid-name-collisions }

`items` submodule’ünü doğrudan import ediyoruz; sadece içindeki `router` değişkenini import etmiyoruz.

Çünkü `users` submodule’ünde de `router` adlı başka bir değişken var.

Eğer şöyle sırayla import etseydik:

   * bulkGet(keys)} operation. See <a href="http://www.mathpages.com/home/kmath199.htm">Balls in
   * Bins model</a> for mathematical formulas that can be used to estimate the probability of
   * collisions.
   *
   * @param keys arbitrary non-null keys
   * @return the stripes corresponding to the objects (one per each object, derived by delegating to

```

第二種是「絕對匯入」：

```Python
from app.routers import items, users
```

想了解更多關於 Python 套件與模組，請閱讀[官方的模組說明文件](https://docs.python.org/3/tutorial/modules.html)。

///

### 避免名稱衝突 { #avoid-name-collisions }

我們直接匯入子模組 `items`，而不是只匯入它的變數 `router`。

這是因為在子模組 `users` 中也有另一個名為 `router` 的變數。

如果我們像下面這樣一個接一個匯入：

```Python
from .routers.items import router
from .routers.users import router
```

```Python
from app.routers import items, users
```

Python Packages와 Modules에 대해 더 알아보려면 [Modules에 대한 Python 공식 문서](https://docs.python.org/3/tutorial/modules.html)를 읽어보세요.

///

### 이름 충돌 피하기 { #avoid-name-collisions }

submodule `items`를 직접 import하고, 그 안의 `router` 변수만 import하지는 않습니다.

이는 submodule `users`에도 `router`라는 이름의 변수가 있기 때문입니다.

만약 다음처럼 순서대로 import했다면:

```Python
from .routers.items import router