RUST_LOG='codex_api::sse::responses=trace' codex exec --skip-git-repo-check -s read-only -m 'gpt-5.3-codex' 'hi' 2>&1 >/dev/null | rg -o --replace '$1' '"model":"([^"]+)"' | head -n1
о нет!
о нет!
Если вы хотите убрать блокировки то:
>> Завтро тоесть, 22.10.10 в пятницу.
>> Не заходим винтернет весь день.
>> Рейтинг РКН упадёт.
>> И мы добьёмся своего. >> НЕ ЗДАВАЙТЕСЬ..Потерпите 1 день за то потом
>> нормальная скорость.
>> ОТПРАВЬ СВОИМ ДРУЗЬЯМ......
>> Завтро тоесть, 22.10.10 в пятницу.
>> Не заходим винтернет весь день.
>> Рейтинг РКН упадёт.
>> И мы добьёмся своего. >> НЕ ЗДАВАЙТЕСЬ..Потерпите 1 день за то потом
>> нормальная скорость.
>> ОТПРАВЬ СВОИМ ДРУЗЬЯМ......
❤5
КАЖДЫЙ РАЗ, КОГДА ЖЕНЩИНА ЗАСТАВЛЯЕТ СВОЕГО МУЖЧИНУ МЫТЬСЯ, ЕГО ГИПОФИЗ ВЫРАБАТЫВАЕТ ПРОЛАКТИН, КОТОРЫЙ СНИЖАЕТ ТЕСТОСТЕРОН, ТАК НЕОБХОДИМЫЙ ЕМУ ДЛЯ ПОБЕДЫ В КОМПЬЮТЕРНОЙ ИГРЕ
> be me
> writing python
> run
> dependencies not locked
> “we trust semver”
> narrators voice: they should not have
> indirect dependency bumps patch version
> changelog says “minor cleanup”
> api removed
> no deprecation
> dependency A pins
> dependency B requires
> pip nods politely
> installs both somehow
> import time civil war
>
> now takes 40 minutes
> uses all cores
> still wrong
> one package ships only sdist
> needs gcc
> ci image does not have gcc
> local machine does
> package version on pypi
> tag does not exist on github
> source code archaeology begins
> release uploaded without
> windows wheels only
> linux builds from source
> missing file at runtime
> project claims “python >=3.8”
> uses
> setup.cfg, setup.py, pyproject.toml
> all three present
> disagree on metadata
> extras
> transitive dependency drags in tensorflow
> optional dependency is not optional
> import at top level
> crash unless installed
>
> silently downgrades something else
> no one knows why
> library forgot to vendor a file
> works from source tree
> breaks when installed
> nobody noticed
> package published with wrong version number
> 1.2.3 > 1.10.0
> semantic versioning is a suggestion
> wheel built against old glibc
> imports locally
> prod container says no
> enjoy recompiling in docker
> package imports
> distutils removed
> surprise archaeology of setuptools internals
> two libraries monkeypatch the same global
> order-dependent behavior
> nondeterministic bugs unlocked
> pip cache corrupted
> deleting
> no explanation offered
> requirements.txt generated by hand
> no hashes
> someone committed
> linux installs different wheels
> dependency vendored dependency
> both loaded
> two copies of same library
> project uses
> slow but fine
> upgrade replaces it
> behavior changes
> library forgot to bump major version
> breaks api anyway
> nightly ci fails
> rerun passes
> nobody trusts green anymore
> someone deletes lockfile in cleanup commit
> “it was outdated”
> now everything is outdated
> vendored code patched locally
> upstream releases new version
> patch lost
> bug resurrected
> open issue on github
> maintainer says “please send pr”
> repo unmaintained since 2019
> fork dependency
> add one-line fix
> now you maintain it forever
> six months later
> another upgrade
> same class of problems
> different package names
> realize python packaging is not broken
> it is functioning exactly as designed
> add
> pin hashes
> freeze universe
> writing python
> run
pip install -r requirements.txt> dependencies not locked
> “we trust semver”
> narrators voice: they should not have
> indirect dependency bumps patch version
> changelog says “minor cleanup”
> api removed
> no deprecation
> dependency A pins
<2.0> dependency B requires
>=2.1> pip nods politely
> installs both somehow
> import time civil war
>
pip resolver “improved”> now takes 40 minutes
> uses all cores
> still wrong
> one package ships only sdist
> needs gcc
> ci image does not have gcc
> local machine does
> package version on pypi
> tag does not exist on github
> source code archaeology begins
> release uploaded without
__init__.py> windows wheels only
> linux builds from source
> missing file at runtime
> project claims “python >=3.8”
> uses
| types> setup.cfg, setup.py, pyproject.toml
> all three present
> disagree on metadata
> extras
[dev] pull in half of pypi> transitive dependency drags in tensorflow
> optional dependency is not optional
> import at top level
> crash unless installed
>
pip install --upgrade> silently downgrades something else
> no one knows why
> library forgot to vendor a file
> works from source tree
> breaks when installed
> nobody noticed
> package published with wrong version number
> 1.2.3 > 1.10.0
> semantic versioning is a suggestion
> wheel built against old glibc
> imports locally
> prod container says no
> enjoy recompiling in docker
> package imports
distutils> distutils removed
> surprise archaeology of setuptools internals
> two libraries monkeypatch the same global
> order-dependent behavior
> nondeterministic bugs unlocked
> pip cache corrupted
> deleting
~/.cache/pip fixes everything> no explanation offered
> requirements.txt generated by hand
> no hashes
> someone committed
pip freeze from mac> linux installs different wheels
> dependency vendored dependency
> both loaded
> two copies of same library
> project uses
pkg_resources entrypoints> slow but fine
> upgrade replaces it
> behavior changes
> library forgot to bump major version
> breaks api anyway
> nightly ci fails
> rerun passes
> nobody trusts green anymore
> someone deletes lockfile in cleanup commit
> “it was outdated”
> now everything is outdated
> vendored code patched locally
> upstream releases new version
> patch lost
> bug resurrected
> open issue on github
> maintainer says “please send pr”
> repo unmaintained since 2019
> fork dependency
> add one-line fix
> now you maintain it forever
> six months later
> another upgrade
> same class of problems
> different package names
> realize python packaging is not broken
> it is functioning exactly as designed
> add
requirements.lock> pin hashes
> freeze universe
❤3
[[Topic of discussion]] is not [[analogy]].
[[Dramatic fact given own line]].
[[Dramatic fact given own line]].
[[Dramatic fact given own line]].
[[Dramatic summary sentence.]] [[Topic of discussion]] is [[different analogy]].
[[Implications delivered with certainty]].
[[Dramatic fact given own line]].
[[Dramatic fact given own line]].
[[Dramatic fact given own line]].
[[Dramatic summary sentence.]] [[Topic of discussion]] is [[different analogy]].
[[Implications delivered with certainty]].
❤2