asyncio.StreamReader raises BufferError with active memoryview

Bug report

Bug description:

Summary

When StreamReader has an active memoryview export of its internal buffer, methods that mutate the buffer in place can raise:

BufferError: Existing exports of data: object cannot be re-sized

This appears in real workloads with async database drivers, but the root cause is in StreamReader buffer mutation behavior.

Steps to reproduce

import asyncio

async def main():
    r = asyncio.StreamReader()
    r.feed_data(b"AABBCCDD")

    # Simulate a consumer that keeps a memoryview alive
    mv = memoryview(r._buffer)

    # Triggers BufferError in current implementation
    await r.readexactly(4)

    mv.release()

asyncio.run(main())

Expected behavior

readexactly(4) should return b"AABB" without raising BufferError.

Actual behavior

BufferError: Existing exports of data: object cannot be re-sized

Why this happens

Some StreamReader paths mutate bytearray in place, for example slice deletion and clear operations. In-place resize is not allowed while a memoryview export exists.

Affected methods

• read
• readline
• readuntil
• readexactly

Environment

• Python: 3.13.x, 3.14.x (also reproducible in local tests with newer builds)
• OS: macOS (also observed in Linux server workloads)
• Third-party context where this is frequently hit: async DB drivers using memoryview over packet buffers

Possible fix direction

Replace in-place buffer mutations with non-mutating replacement assignments, for example:

• replace slice delete with reassignment to remaining bytes
• replace clear with assigning a new empty bytearray

If useful, I can open a PR with tests covering the regression paths.

CPython versions tested on:

3.13

Operating systems tested on:

macOS

Linked PRs

• gh-146380

從 asyncio.StreamReader 以及報告中描述的 read、readline、readuntil 和 readexactly 路徑開始；執行提供的重現步驟，以觀察存在作用中的 memoryview 時的 BufferError。完成標準是這些方法在不引發例外的情況下回傳預期資料，並為受影響的緩衝區變更路徑提供回歸涵蓋率。