Explore tweets tagged as #pythonstatus
@PythonStatus Hello, I'm still having an issue about publishing a new package. I tried both `uv publish` and `twine upload` and I was able to create a new project and upload it to testpypi with difficulty. My package size is lower than 30 kb.
0
0
0
made with @creativecloud I meant @ChatGPTapp 😔 @DiffusionPics I said #pdf were coming , expect more #jinja2 @powerpoint and @github 📄, in #meanie 🚫 💫 @PythonStatus he 🥫 #uv @UvicornApp whoami? I hate #xml @OpenAI the @USDOT @Ubisoft of #dlc.
@kimmonismus yet these models have no concept of reflection, except for @deepseek_ai , no sense of community, models are causal transformations , and also #LaTeX is not implemented , so no nonlinear coupling in #mathjax or something.
0
0
0
Resolved: We have not seen a return of the traffic that caused this incident after removing the temporary block. We will open a new incident if we need to take action again.
1
0
1
Identified: We have identified a flood of requests from a cluster using the `python-requests/2.32.3` User-Agent which do not include a trailing slash to the JSON api endpoints. This causes excessive cache misses, which are overwhelmi…
1
0
0
Verifying: All database tasks are complete and we are now monitoring for stability post-upgrade. Services should be back online in full.
1
0
0
Completed: This maintenance is complete! All metrics have returned to baseline.
0
0
0
Day 89 of 100 - I implemented a chatbot to answer questions about the weather using Python, spaCy NLP, and the OpenWeather API. #100DaysOfCode #mypythonstatus #pythonstatus #python #nlp.
0
2
5
Investigating: We're investigating elevated error rates for
1
0
1
In Progress: Scheduled maintenance is currently in progress. We will provide updates as necessary.
1
0
1
Investigating: We are working to investigate a partial outage in the PyPI backends.
1
0
0
Identified: We are working to resolve an outage impacting our /simple and /json apis.
1
0
0
Scheduled (Jun 11, 2025, 19:00 UTC): PyPI will be undergoing maintenance for a major version database upgrade. We anticipate up to 5-10 minutes of disruption when the cut-over occurs.
1
0
1
Monitoring: We've increased capacity in the worker pools that service /simple and /json and are monitoring as things recover.
2
0
0
Identified: We've identified an issue with database contention arising from locking.
1
0
1
Identified: We have temporarily suspended new project creation and new user registration to mitigate an ongoing malware upload campaign.
0
0
2