Results of 1 - 10 of about 210 for never (0.036 sec.)
- Pending removal in Python 3.17 — Python 3.14.8 ドキュメント 13068
- ナビゲーション 索引 モジュール | Python » 3.14.8 Documentation » Pending removal in Python 3.17 テーマ 自動 ライト ダーク | Pending removal in Python 3.17 ¶ collections.abc : collections.abc.ByteString is scheduled for removal in Python 3.1
...ally intended to be an abstract class that would serve as a supertype of both bytes and bytearray . However, since the ABC never had any methods, knowing that an object was an instance of ByteString never actually told you anything useful about the ob...ject. Other common buffer types such as memoryview were also never understood as subtypes of ByteString (either at runtime or by static type checkers). See PEP 688 for more details. (Contri...ally intended to be an abstract class that would serve as a supertype of both bytes and bytearray . However, since the ABC never had any methods, knowing that an object was an instance of ByteString never actually told you anything useful about the ob... - https://man.mtool.work/python/3.14/deprecations/pending-removal-in-3.17.html
- Pending removal in Python 3.17 — Python 3.14.8 ドキュメント 13068
- ナビゲーション 索引 モジュール | Python » 3.14.8 Documentation » Pending removal in Python 3.17 テーマ 自動 ライト ダーク | Pending removal in Python 3.17 ¶ collections.abc : collections.abc.ByteString is scheduled for removal in Python 3.1
...ally intended to be an abstract class that would serve as a supertype of both bytes and bytearray . However, since the ABC never had any methods, knowing that an object was an instance of ByteString never actually told you anything useful about the ob...ject. Other common buffer types such as memoryview were also never understood as subtypes of ByteString (either at runtime or by static type checkers). See PEP 688 for more details. (Contri...ally intended to be an abstract class that would serve as a supertype of both bytes and bytearray . However, since the ABC never had any methods, knowing that an object was an instance of ByteString never actually told you anything useful about the ob... - https://man.mtool.work/python/3.14/deprecations/pending-removal-in-3.17.html
- typing --- 型ヒントのサポート — Python 3.14.8 ドキュメント 9266
- ナビゲーション 索引 モジュール | 次へ | 前へ | Python » 3.14.8 Documentation » The Python standard library » 開発ツール » typing --- 型ヒントのサポート テーマ 自動 ライト ダーク | typing --- 型ヒントのサポート ¶ Added in version 3.5. ソース
...s could be vulnerable to an SQL injection attack. より詳しくは PEP 675 を参照してください。 Added in version 3.11. typing. Never ¶ typing. NoReturn ¶ Never and NoReturn represent the bottom type , a type that has no members. They can be used to indica...te that a function never returns, such as sys.exit() : from typing import Never # or NoReturn def stop () -> Never : raise RuntimeError ( 'no way'...) Or to define a function that should never be called, as there are no valid arguments, such as assert_never() : from typing import Never # or NoReturn def never_call... - https://man.mtool.work/python/3.14/library/typing.html
- typing --- 型ヒントのサポート — Python 3.14.8 ドキュメント 9266
- ナビゲーション 索引 モジュール | 次へ | 前へ | Python » 3.14.8 Documentation » The Python standard library » 開発ツール » typing --- 型ヒントのサポート テーマ 自動 ライト ダーク | typing --- 型ヒントのサポート ¶ Added in version 3.5. ソース
...s could be vulnerable to an SQL injection attack. より詳しくは PEP 675 を参照してください。 Added in version 3.11. typing. Never ¶ typing. NoReturn ¶ Never and NoReturn represent the bottom type , a type that has no members. They can be used to indica...te that a function never returns, such as sys.exit() : from typing import Never # or NoReturn def stop () -> Never : raise RuntimeError ( 'no way'...) Or to define a function that should never be called, as there are no valid arguments, such as assert_never() : from typing import Never # or NoReturn def never_call... - https://man.mtool.work/python/3.14/library/typing.html
- 変更履歴 — Python 3.14.8 ドキュメント 8281
- ナビゲーション 索引 モジュール | 次へ | 前へ | Python » 3.14.8 Documentation » What's New in Python » 変更履歴 テーマ 自動 ライト ダーク | 変更履歴 ¶ Python next ¶ Release date: XXXX-XX-XX セキュリティ ¶ gh-157265 : In tarfile , when extrac
...ter the shield was cancelled, even when the exception is retrieved afterwards. The exception is now reported only if it is never retrieved, as with any other future. gh-158563 : Fix turtle.undo() after turtle.teleport() and after an exception in turtl...iteration over a contextvars.Context , with the garbage collector. A reference cycle running through such an iterator was never collected, leaking the whole context it iterated over. gh-154937 : Fix a data race on thread handle identifiers when _thre.... gh-155143 : Fix asyncio.shield() leaking the calling task via the await-graph and callbacks when called on a future that never resolves. gh-154871 : Fixed a crash in asyncio.Task.get_context() when called on an uninitialized task. gh-154855 : Fix cu... - https://man.mtool.work/python/3.14/whatsnew/changelog.html
- 非推奨 — Python 3.14.8 ドキュメント 7995
- ナビゲーション 索引 モジュール | 次へ | 前へ | Python » 3.14.8 Documentation » 非推奨 テーマ 自動 ライト ダーク | 非推奨 ¶ Pending removal in Python 3.15 ¶ The import system: Setting __cached__ on a module while failing to set __spec__.cach
...ally intended to be an abstract class that would serve as a supertype of both bytes and bytearray . However, since the ABC never had any methods, knowing that an object was an instance of ByteString never actually told you anything useful about the ob...ject. Other common buffer types such as memoryview were also never understood as subtypes of ByteString (either at runtime or by static type checkers). See PEP 688 for more details. (Contri...ally intended to be an abstract class that would serve as a supertype of both bytes and bytearray . However, since the ABC never had any methods, knowing that an object was an instance of ByteString never actually told you anything useful about the ob... - https://man.mtool.work/python/3.14/deprecations/
- 非推奨 — Python 3.14.8 ドキュメント 7434
- ナビゲーション 索引 モジュール | 次へ | 前へ | Python » 3.14.8 Documentation » 非推奨 テーマ 自動 ライト ダーク | 非推奨 ¶ Pending removal in Python 3.15 ¶ The import system: Setting __cached__ on a module while failing to set __spec__.cach
...ally intended to be an abstract class that would serve as a supertype of both bytes and bytearray . However, since the ABC never had any methods, knowing that an object was an instance of ByteString never actually told you anything useful about the ob...ject. Other common buffer types such as memoryview were also never understood as subtypes of ByteString (either at runtime or by static type checkers). See PEP 688 for more details. (Contri...ally intended to be an abstract class that would serve as a supertype of both bytes and bytearray . However, since the ABC never had any methods, knowing that an object was an instance of ByteString never actually told you anything useful about the ob... - https://man.mtool.work/python/3.14/deprecations/
- asyncio での開発 — Python 3.14.8 ドキュメント 7148
- ナビゲーション 索引 モジュール | 次へ | 前へ | Python » 3.14.8 Documentation » The Python standard library » ネットワーク通信とプロセス間通信 » asyncio --- 非同期 I/O » asyncio での開発 テーマ 自動 ライト ダーク | asyncio での開発 ¶ 非同期プ
...を使わずにスケジュールされた場合、 asyncio は RuntimeWarning 警告を送出します: import asyncio async def test (): print ( "never scheduled" ) async def main (): test () asyncio . run ( main ()) 出力: test . py : 7 : RuntimeWarning : coroutine 'test' w...as never awaited test () デバッグモードの出力: test . py : 7 : RuntimeWarning : coroutine 'test' was never awaited Coroutine create...on ( "not consumed" ) async def main (): asyncio . create_task ( bug ()) asyncio . run ( main ()) 出力: Task exception was never retrieved future : < Task finished coro =< bug () done , defined at test . py : 3 > exception = Exception ( 'not consumed'... - https://man.mtool.work/python/3.14/library/asyncio-dev.html
- asyncio での開発 — Python 3.14.8 ドキュメント 7148
- ナビゲーション 索引 モジュール | 次へ | 前へ | Python » 3.14.8 Documentation » The Python standard library » ネットワーク通信とプロセス間通信 » asyncio --- 非同期 I/O » asyncio での開発 テーマ 自動 ライト ダーク | asyncio での開発 ¶ 非同期プ
...を使わずにスケジュールされた場合、 asyncio は RuntimeWarning 警告を送出します: import asyncio async def test (): print ( "never scheduled" ) async def main (): test () asyncio . run ( main ()) 出力: test . py : 7 : RuntimeWarning : coroutine 'test' w...as never awaited test () デバッグモードの出力: test . py : 7 : RuntimeWarning : coroutine 'test' was never awaited Coroutine create...on ( "not consumed" ) async def main (): asyncio . create_task ( bug ()) asyncio . run ( main ()) 出力: Task exception was never retrieved future : < Task finished coro =< bug () done , defined at test . py : 3 > exception = Exception ( 'not consumed'... - https://man.mtool.work/python/3.14/library/asyncio-dev.html
- Thread Safety Guarantees — Python 3.14.8 ドキュメント 6724
- ナビゲーション 索引 モジュール | 次へ | 前へ | Python » 3.14.8 Documentation » Python built-ins reference » Thread Safety Guarantees テーマ 自動 ライト ダーク | Thread Safety Guarantees ¶ This page documents thread-safety guarantees for bui
...cked when it is also a list (but not its subclasses). Operations that involve multiple accesses, as well as iteration, are never atomic. For example: # NOT atomic: read-modify-write lst [ i ] = lst [ i ] + 1 # NOT atomic: check-then-act if lst : item...rable is not a dict/set/frozenset: only result locked Operations that involve multiple accesses, as well as iteration, are never atomic: # NOT atomic: read-modify-write d [ key ] = d [ key ] + 1 # NOT atomic: check-then-act (TOCTOU) if key in d : del...# both locked s . issuperset ( other ) # both locked Operations that involve multiple accesses, as well as iteration, are never atomic: # NOT atomic: check-then-act if elem in s : s . remove ( elem ) # NOT thread-safe: iteration while modifying for e... - https://man.mtool.work/python/3.14/builtins/threadsafety.html