Skip to content

Conversation

Matthew-Jenkins
Copy link
Contributor

I have no idea why you would not want to use a session by default. If you make more than 1 request in your script you benefit by an order of magnitude on wait to reconnect.

I have no idea why you would not want to use a session by default. If you make more than 1 request in your script you benefit by an order of magnitude on wait to reconnect.
@gonchik gonchik merged commit 457e8e3 into atlassian-api:master Aug 8, 2025
4 of 8 checks passed
@gonchik
Copy link
Member

gonchik commented Aug 21, 2025

@Matthew-Jenkins wrapping into readme.
Let's write into doc instead of change as it's affect clients

@Matthew-Jenkins
Copy link
Contributor Author

This looks more like a custom/environmental issue. Likely something is monkey-patched or non-standard in your setup that causes the internally created session object to be GCed, which drops auth state. The proposed “fix” doesn’t actually change anything functionally, both cases are just session=requests.Session().

The only difference is that one is bound weakly inside the class while the other persists in your calling scope, so GC can’t reclaim it between calls. That points to a lifetime/GC issue in your environment rather than a problem in the library.

#1573

@gonchik

@gonchik
Copy link
Member

gonchik commented Aug 21, 2025

@Matthew-Jenkins I think needed to review a full solution.
Honestly, I thought nothing special.
let me collect all info and them pull it

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants