Async tempfile implementation following the existing structure, with a bit extra for SpooledTemporaryFile where delegation is not required unless the in-memory stream is rolled to disk.

Based on [cancelled] pull request 137. Changes:

1. Pythons: Python 3.6 removed, PyPy-3.8 over PyPy3.7;
2. Documentation: Sphinx has not been added yet -> docs need more time;
3. GitHub Actions workflow: the separate coverage job added, actions versions updated;
4. Coverage: 100% reached, the coverage under 90% is considered failure;
5. Functionality:

• asyncify (former wrap) function is more similar to asyncio.to_thread (Py3.9);
• a new isasync function added to check if the function parametre is already an "asynchronous" object.

This PR may address/solve the following issues:

• https://github.com/Tinche/aiofiles/issues/136 - asyncio_mode=strict in pytest.ini;
• https://github.com/Tinche/aiofiles/issues/132 - pyproject.toml enriched, republishing to PyPI should reveal the situation;
• https://github.com/Tinche/aiofiles/issues/129 - now get_running_loop() is used;

Backward compatibility fails for those having used wrap function, therefore, the next version may be 1.0.0, not 0.9.0.

This would fix #96

Adds support for other async frameworks using anyio. The only thing to wait on is the release of anyio version 3, but I'd like to know if there's interest in this!

Cheers.

aiofiles.os.sendfiles not found. Error: AttributeError: module 'aiofiles.os' has no attribute 'sendfile'

pip freeze result:

aiofiles==22.1.0
asyncio==3.4.3
types-aiofiles==22.1.0

or another method copy file to dir like a link? im newbie of python

My dependency bot just detected the new released version 22.0.1. Is there any reason to jump from 0.8 to 22.0 and why is the version marked as TBC? What does TBC means?

Hi there! Pytest is correctly complaining about the use of @coroutine decorator at aiofiles.os line 8. This is for the current latest 0.5.0 version.

https://github.com/Tinche/aiofiles/blob/258e95640d6242c53a1c0d84e68343d79d80d781/aiofiles/os.py#L7-L16

The fix would be to use async def directly:

def wrap(func):
    @wraps(func)
    async def run(*args, loop=None, executor=None, **kwargs):
        if loop is None:
            loop = asyncio.get_event_loop()
        pfunc = partial(func, *args, **kwargs)
        return loop.run_in_executor(executor, pfunc)

    return run

Hi!

I found a minor issue in SpooledTemporaryFile and I fixed it.

Fix https://github.com/Tinche/aiofiles/issues/118

ref) https://github.com/python/cpython/blob/3e43fac2503afe219336742b150b3ef6e470686f/Lib/tempfile.py#L747

e.g. /home/daves/github/aiofiles/.pybuild/cpython3_3.8/build/aiofiles/threadpool/utils.py:33: DeprecationWarning: "@coroutine" decorator is deprecated since Python 3.8, use "async def" instead def method(self, *args, **kwargs):

.pybuild/cpython3_3.8/build/tests/test_simple.py::test_serve_small_bin_file_sync /home/daves/github/aiofiles/.pybuild/cpython3_3.8/build/tests/test_simple.py:28: DeprecationWarning: The loop argument is deprecated since Python 3.8, and scheduled for removal in Python 3.10. server = yield from asyncio.start_server(serve_file, port=unused_tcp_port,

Similar to issue #20 , how can standard pickle interface be used along with aiofiles? How could it be done? By mimicking pickle sourcecode equivalent into aiofiles? Can such support be a feature of aiofiles?

README.md says :

The closing of a file may block, and yielding from a coroutine while exiting from a context manager isn't possible, so aiofiles file objects can't be used as context managers. Use the try/finally construct from the introductory section to ensure files are closed.

Iteration is also unsupported. To iterate over a file, call readline repeatedly until an empty result is returned. Keep in mind readline doesn't strip newline characters.

Python 3.5 provides asynchronous context managers and iterators, using __aenter__, __aexit__, __aiter__ and __anext__. I think adding support for these could provide a nice API for aiofiles, and it wouldn'bt be harder than something along the lines of:

class IterableContextManagerFileWrapper:  # yes it needs a new name
    def __init__(self, *args, **kwargs):
        # store arguments so that file can be created in __aenter__
        self.__args, self.__kwargs = args, kwargs
        self.__file = None  # set in __aenter__

     def __getattr__(self, name):
         assert self.__file is not None, "file context manager not entered"
         return getattr(self.__file, name)   # wrap the async file object

     async def __aenter__(self):
         self.__file = await open(*self.args, **self.kwargs)
         return self  # return self and not file so that the value can be used as iterable

     async def __aexit__(self, exc_type, exc_value, exc_tb):
         await self.close()
         return False  # no reason to intercept exception

     async def __aiter__(self):
         return self  # this object is an iterator, so just has to return itself to be an iterable

     async def __anext__(self):
          line = await self.readline()
          if not line:  # EOF
              raise StopAsyncIteration  # not StopIteration !
          else:
              return line

The resulting wrapper could now be used as :

async with IterableContextManagerFileWrapper("/tmp/lol") as aiofile:
    async for line in aiofile:
        line = line.rstrip()
        ...

My proposed POC has a weird name because I don't really know to integrate it into the class hierarchy, so I made a wrapper that provides the proposed features on top of the objects returned by aiofiles coroutines.

This is also why I submit this is an issue and not a PR, because I would like to get your opinion on what would be the best way to implement.

Make sendfile more lenient for posix systems that don't have sendfile in the os module. This should still achieve the same as the original line on platforms such as windows because windows will not have sendfile as an attribute of os.

How would be the recommended way to list all the files in a directory and then delete them. Using python os you can do it this way:

    def clear_directory(self, dir: str):
       for f in os.listdir(dir):
           os.remove(os.path.join(dir, f))

But I can't seem to find a way to do this with aiofiles.os

While I love context managers, the stack isn't always the the place to perform clean up. open can be used without async with. How can I use aiofiles.open without it?

import asyncio

import aiofiles

async def test():
    f = aiofiles.open('filename.txt', mode='w')
    try:
        #await f.write('123') #  'AiofilesContextManager' object has no attribute 'write'
        await f.send('123') # TypeError: can't send non-None value to a just-started generator
    finally:
        f.close()
asyncio.run(test())

Python 3.10 is issuing a deprecation warning on pytest asyncio_mode:

../../../../usr/lib/python3/dist-packages/pytest_asyncio/plugin.py:191
  /usr/lib/python3/dist-packages/pytest_asyncio/plugin.py:191: DeprecationWarning: The 'asyncio_mode' default value will change to 
'strict' in future, please explicitly use 'asyncio_mode=strict' or 'asyncio_mode=auto' in pytest configuration file.
    config.issue_config_time_warning(LEGACY_MODE, stacklevel=2)

-- Docs: https://docs.pytest.org/en/stable/warnings.html

The stderr output can lead to autopkgtest failures.

Addressed by this patch.

I have a report on a test failure due to the deprecation of a get_event_loop() call (https://github.com/davesteele/aiofiles/pull/2). This patch changes the other occurrences of that call.

Unit tests have failed on ppc64el hardware:

https://ci.debian.net/data/autopkgtest/unstable/ppc64el/a/aiofiles/18419050/log.gz

autopkgtest [08:17:49]: test unittests.py: [-----------------------
============================= test session starts ==============================
platform linux -- Python 3.9.10, pytest-6.2.5, py-1.10.0, pluggy-0.13.0
rootdir: /tmp/autopkgtest-lxc.9mzzz2i1/downtmp/build.Jix/src
plugins: asyncio-0.16.0
collected 155 items

tests/test_os.py ......                                                  [  3%]
tests/test_simple.py ..                                                  [  5%]
tests/threadpool/test_binary.py ........................................ [ 30%]
...........................................................              [ 69%]
tests/threadpool/test_concurrency.py .                                   [ 69%]
tests/threadpool/test_open.py ...                                        [ 71%]
tests/threadpool/test_text.py .......................................... [ 98%]
..                                                                       [100%]

============================= 155 passed in 1.76s ==============================
Task was destroyed but it is pending!
task: <Task pending name='Task-123' coro=<test_slow_file.<locals>.serve_file() running at /tmp/autopkgtest-lxc.9mzzz2i1/downtmp    /build.Jix/src/tests/threadpool/test_concurrency.py:37> wait_for=<Future pending cb=[_chain_future.<locals>._call_check_cancel() at     /usr/lib/python3.9/asyncio/futures.py:384, <TaskWakeupMethWrapper object at 0x7fff84d62070>()]>>
autopkgtest [08:17:51]: test unittests.py: -----------------------]
autopkgtest [08:17:52]: test unittests.py:  - - - - - - - - - - results - - - - - - - - - -
unittests.py         FAIL stderr: Task was destroyed but it is pending!
autopkgtest [08:17:52]: test unittests.py:  - - - - - - - - - - stderr - - - - - - - - - -
Task was destroyed but it is pending!
task: <Task pending name='Task-123' coro=<test_slow_file.<locals>.serve_file() running at /tmp/autopkgtest-lxc.9mzzz2i1/downtmp    /build.Jix/src/tests/threadpool/test_concurrency.py:37> wait_for=<Future pending cb=[_chain_future.<locals>._call_check_cancel() at /usr/lib/python3.9/asyncio/futures.py:384, <TaskWakeupMethWrapper object at 0x7fff84d62070>()]>>

Does test_slow_file() need to verify serve_file() is drained before cleaning up?