The Fix
pip install stripe==14.4.0a2
Based on closed stripe/stripe-python issue #1167 · PR/commit linked
Production note: Most teams hit this during upgrades or environment changes. Roll out with a canary and smoke critical endpoints (health, OpenAPI/docs) before 100%.
@@ -27,6 +27,10 @@ per-file-ignores =
# setup.py is required for tooling
setup.py: IMP102
+ # should not raise a deprecation warning since it needs
+ # to be imported early in `stripe/__init__.py` to avoid
+ # a name conflict
repro.py
root@ed5bfe3d7af7:/# pip install stripe
Successfully installed certifi-2023.11.17 charset-normalizer-3.3.2 idna-3.6 requests-2.31.0 stripe-7.8.1 typing-extensions-4.9.0 urllib3-2.1.0
root@ed5bfe3d7af7:/# python -Xdev -c 'import stripe'
/usr/local/lib/python3.12/site-packages/stripe/app_info.py:5: DeprecationWarning:
The stripe.app_info package is deprecated, please change your
imports to import from stripe directly.
From:
from stripe.app_info import AppInfo
To:
from stripe import AppInfo
warn(
root@ed5bfe3d7af7:/#
verify
Re-run the minimal reproduction on your broken version, then apply the fix and re-run.
fix.md
Option A — Upgrade to fixed release\npip install stripe==14.4.0a2\nWhen NOT to use: This fix should not be used if the deprecation warning is required for legacy code.\n\n
Why This Fix Works in Production
- Trigger: When `DeprecationWarning`s are set to raise and not just warn (e.g. in our test setup), this causes an immediate test failure.
- Mechanism: Addresses a deprecation warning raised when importing the stripe.app_info package by removing the warning.
- Why the fix works: Addresses a deprecation warning raised when importing the stripe.app_info package by removing the warning. (first fixed release: 14.4.0a2).
Production impact:
- If left unfixed, the same config can fail only in production (env differences), causing startup failures or partial feature outages.
Why This Breaks in Prod
- Shows up under Python 3.12 in real deployments (not just unit tests).
- Production symptom (often without a traceback): When `DeprecationWarning`s are set to raise and not just warn (e.g. in our test setup), this causes an immediate test failure.
Proof / Evidence
- GitHub issue: #1167
- Fix PR: https://github.com/stripe/stripe-python/pull/1168
- First fixed release: 14.4.0a2
- Reproduced locally: No (not executed)
- Last verified: 2026-02-08
- Confidence: 0.75
- Did this fix it?: Yes (upstream fix exists)
- Own content ratio: 0.51
Discussion
High-signal excerpts from the issue thread (symptoms, repros, edge-cases).
“### Describe the bug See reproduction notes. When DeprecationWarnings are set to raise and not just warn (e.g. in our test setup), this causes an immediate test failure. ### To Reproduce ### Expected behavior No deprecation warning simply f”
Failure Signature (Search String)
- When `DeprecationWarning`s are set to raise and not just warn (e.g. in our test setup), this causes an immediate test failure.
- The stripe.app_info package is deprecated, please change your
Copy-friendly signature
signature.txt
Failure Signature
-----------------
When `DeprecationWarning`s are set to raise and not just warn (e.g. in our test setup), this causes an immediate test failure.
The stripe.app_info package is deprecated, please change your
Error Message
Signature-only (no traceback captured)
error.txt
Error Message
-------------
When `DeprecationWarning`s are set to raise and not just warn (e.g. in our test setup), this causes an immediate test failure.
The stripe.app_info package is deprecated, please change your
Minimal Reproduction
repro.py
root@ed5bfe3d7af7:/# pip install stripe
Successfully installed certifi-2023.11.17 charset-normalizer-3.3.2 idna-3.6 requests-2.31.0 stripe-7.8.1 typing-extensions-4.9.0 urllib3-2.1.0
root@ed5bfe3d7af7:/# python -Xdev -c 'import stripe'
/usr/local/lib/python3.12/site-packages/stripe/app_info.py:5: DeprecationWarning:
The stripe.app_info package is deprecated, please change your
imports to import from stripe directly.
From:
from stripe.app_info import AppInfo
To:
from stripe import AppInfo
warn(
root@ed5bfe3d7af7:/#
Environment
- Python: 3.12
What Broke
Tests fail immediately when DeprecationWarning is raised due to strict settings.
Fix Options (Details)
Option A — Upgrade to fixed release Safe default (recommended)
pip install stripe==14.4.0a2
When NOT to use: This fix should not be used if the deprecation warning is required for legacy code.
Use when you can deploy the upstream fix. It is usually lower-risk than long-lived workarounds.
Fix reference: https://github.com/stripe/stripe-python/pull/1168
First fixed release: 14.4.0a2
Last verified: 2026-02-08. Validate in your environment.
When NOT to Use This Fix
- This fix should not be used if the deprecation warning is required for legacy code.
Verify Fix
verify
Re-run the minimal reproduction on your broken version, then apply the fix and re-run.
Did This Fix Work in Your Case?
Quick signal helps us prioritize which fixes to verify and improve.
Prevention
- Capture the exact failing error string in logs and tests so you can reproduce via a minimal script.
- Pin production dependencies and upgrade only with a reproducible test that hits the failing path.
Version Compatibility Table
| Version | Status |
|---|---|
| 14.4.0a2 | Fixed |
Related Issues
No related fixes found.
Sources
We don’t republish the full GitHub discussion text. Use the links above for context.