m the unprotected thread to the protected one.
[1] https://man.archlinux.org/man/seccomp.2
[2] https://lwn.net/Articles/634391/
Cheers,
Filipe Laíns
signature.asc
Description: This is a digitally signed message part
___
Python-ideas mailin
ee with the point that directories are not resources, in fact:
https://github.com/python/importlib_resources/blob/main/importlib_resources/_adapters.py#L96-L100
Cheers,
Filipe Laíns
signature.asc
Description: This is a digitally signed message part
___
Pyt
abstracting the FS
away. Packages are akin to directories, files are akin to resources, when
operating on a FS.
Cheers,
Filipe Laíns
signature.asc
Description: This is a digitally signed message part
___
Python-ideas mailing list -- python-ideas@python.
;
> --
> Greg
It's not contradictory. "the individual resources may not be files on disk at
all" hints that the resource might be for eg. an entry on a database that
contains binary data.
Directory are not binary data, they cannot be a r
se
needing a file on the file system is sort of common, but from my experience the
same is not true for directories.
While I can see the value in what you propose, I worry it is not a common enough
use-case. Some code examples would definitely help out here.
Cheers,
Filipe Laíns
signature.asc
) method
> returning a context manager.
>
> Thoughts ?
>
> Thanks,
bpo: https://bugs.python.org/issue25625
PR: https://github.com/python/cpython/pull/28271
Filipe Laíns
signature.asc
Description: This is a digitally signed message part
___
y exists natively in Python, please put some example
> or documentation link below.
>
> Thanks in advance.
Hi Leonardo,
Please check out subtests, they allow you to achieve what you are looking for :)
https://docs.python.org/3/library/unittest.html#distinguishing-test-iterations-using-subte
at `...` refers to, so that both could not be assigned a new value.
>
Perhaps Ellipsis could get the same treatment as None here, but I am not sure if
there's enough reasoning to justify that, especially considering that it would
be a backwards incompatible change.
ived at
> https://mail.python.org/archives/list/python-ideas@python.org/message/UEHUJOH4WDYLH4QPN7RC3HXCEUK3OAMO/
> Code of Conduct: http://python.org/psf/codeofconduct/
I support this change.
It would also be fairly trivial to make the hard error be descriptive and user-
friendly, like the Pyth
