Skip to content

Make 'v1' token storage less accessible - #1265

Closed
sirosen wants to merge 1 commit into
globus:4.x-devfrom
sirosen:bury-v1-tokenstorage
Closed

Make 'v1' token storage less accessible#1265
sirosen wants to merge 1 commit into
globus:4.x-devfrom
sirosen:bury-v1-tokenstorage

Conversation

@sirosen

@sirosen sirosen commented Jul 17, 2025

Copy link
Copy Markdown
Member

NB: This isn't something we've discussed as a team, but I think it aligns with our general naming and deprecation schedule without adding scope-creep to our SDK v4 milestone.

I noted an example which is still showing the 'v1' interface, which I intend to update in a separate follow-up.


This is a small internal change which reduces the size of the globus_sdk.token_storage top-level interface.

It has impact on code completions and the general developer experience when using these legacy tools.

A new section is added to the upgrading guide on the changes in names (not previously covered).


📚 Documentation preview 📚: https://globus-sdk-python--1265.org.readthedocs.build/en/1265/

This is a small internal change which reduces the size of the
``globus_sdk.token_storage`` top-level interface.

It has impact on code completions and the general developer experience
when using these legacy tools.

A new section is added to the upgrading guide on the changes in names
(not previously covered).
@kurtmckee

Copy link
Copy Markdown
Member

Introducing a v1 module on the march to v4 doesn't strike me as desirable.

@sirosen

sirosen commented Jul 18, 2025

Copy link
Copy Markdown
Member Author

I would accept a suggestion for an alternative naming scheme, e.g.

token_storage/
  legacy/
  ...

I care about the advertised/documented import paths more than I do about the physical file layout.

I think it's mildly relevant that this doesn't introduce the name, it just starts to require it. Only in that I'm not "suggesting" v1.

@sirosen

sirosen commented Jul 23, 2025

Copy link
Copy Markdown
Member Author

We want to plan / discuss any rename to handle this, so I'm marking as a draft. It may be superseded.

@sirosen
sirosen marked this pull request as draft July 23, 2025 20:14
@sirosen

sirosen commented Jul 29, 2025

Copy link
Copy Markdown
Member Author

Closed in favor of #1290

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