}} release: {{ .Release.Name }} heritage: {{ .Release.Service }} data: initialize: |- {{- include (print $.Template.BasePath "/_helper_create_bucket.txt") . | nindent 4 }} add-user: |- {{- include (print $.Template.BasePath "/_helper_create_user.txt") . | nindent 4 }} add-policy: |- {{- include (print $.Template.BasePath "/_helper_create_policy.txt") . | nindent 4 }} {{- range $idx, $policy := .Values.policies }} # Policy: {{ $policy.name }} policy_{{ $idx }}.json: |- {{- include (print $.Template.BasePath...

	<licenses>
		<license>
			<name>GNU Lesser General Public License, version 2.1</name>
			<url>http://www.gnu.org/licenses/old-licenses/lgpl-2.1.txt</url>
			<distribution>repo</distribution>
		</license>
	</licenses>
	<organization>
		<name>CodeLibs Project</name>
		<url>https://www.codelibs.org/</url>
	</organization>
	<developers>
		<developer>

```Python
with open("./somefile.txt") as f:
    contents = f.read()
    print(contents)
```

Im Hintergrund erstellt das `open("./somefile.txt")` ein Objekt, das als „Kontextmanager“ bezeichnet wird.

```Python
with open("./somefile.txt") as f:
    contents = f.read()
    print(contents)
```

Internamente, `open("./somefile.txt")` crea un objeto llamado "Context Manager".

Cuando el bloque `with` termina, se asegura de cerrar el archivo, incluso si hubo excepciones.

   * behavior that the {@link File} API does not already account for. For example, on NTFS it will
   * report {@code "txt"} as the extension for the filename {@code "foo.exe:.txt"} even though NTFS
   * will drop the {@code ":.txt"} part of the name when the file is actually created on the
   * filesystem due to NTFS's <a

"minio.chart" . }} release: {{ .Release.Name }} heritage: {{ .Release.Service }} data: initialize: |- {{ include (print $.Template.BasePath "/_helper_create_bucket.txt") . | indent 4 }} add-user: |- {{ include (print $.Template.BasePath "/_helper_create_user.txt") . | indent 4 }} add-policy: |- {{ include (print $.Template.BasePath "/_helper_create_policy.txt") . | indent 4 }} {{- range $idx, $policy := .Values.policies }} # {{ $policy.name }} policy_{{ $idx }}.json: |- {{ include (print $.Template.BasePath ...

- Apache Commons Compress (for archive tests)

### Test Resources:
- `extractor/msoffice/test.doc`
- `extractor/msoffice/test.xls`
- `extractor/msoffice/test.ppt`
- `extractor/test.txt`
- `extractor/zip/test.zip`

## Key Improvements Tested

### 1. Resource Management
- ✅ Try-with-resources usage in MS Office extractors
- ✅ Proper closure of POI objects
- ✅ No resource leaks on exception

이것은 함수를 "**비동기 컨텍스트 매니저**"라고 불리는 것으로 변환시킵니다.

{* ../../docs_src/events/tutorial003.py hl[1,13] *}

파이썬에서 **컨텍스트 매니저**는 `with` 문에서 사용할 수 있는 것입니다. 예를 들어, `open()`은 컨텍스트 매니저로 사용할 수 있습니다:

```Python
with open("file.txt") as file:
    file.read()
```
최근 버전의 파이썬에서는 **비동기 컨텍스트 매니저**도 있습니다. 이를 `async with`와 함께 사용합니다:

```Python
async with lifespan(app):
    await do_stuff()
```

```Python
with open("./somefile.txt") as f:
    contents = f.read()
    print(contents)
```

Por baixo dos panos, o código `open("./somefile.txt")` cria um objeto que é chamado de "Gerenciador de Contexto".

```Python
with open("./somefile.txt") as f:
    contents = f.read()
    print(contents)
```

Underneath, the `open("./somefile.txt")` creates an object that is called a "Context Manager".

When the `with` block finishes, it makes sure to close the file, even if there were exceptions.