Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Suggestion: Provide a suitable, default namespace for each task #90

Open
Andrew-S-Rosen opened this issue Jan 7, 2024 · 0 comments
Open

Suggestion: Provide a suitable, default namespace for each task #90

Andrew-S-Rosen opened this issue Jan 7, 2024 · 0 comments

Comments

@Andrew-S-Rosen
Copy link

Andrew-S-Rosen commented Jan 7, 2024 •
edited
Loading

I see the warning that in the future, the redun_namespace variable will need to be set on the module-level and/or the namespace provided in the @task. Personally, I would like to make an alternate suggestion: make the default namespace for each task be task.func.__module__. The combination of the __module__ in the namespace and the __name__ in the name will yield a unique identifier in virtually all practical cases.
@Andrew-S-Rosen Andrew-S-Rosen changed the title Suggestion: Make a unique, default redun_namespace for each @task Suggestion: Make the default name for @tasks be task.func.__module__ / task.func.__name__ Jan 7, 2024
@Andrew-S-Rosen Andrew-S-Rosen changed the title Suggestion: Make the default name for @tasks be task.func.__module__ / task.func.__name__ Suggestion: Provide a suitable, default namespace for each task Jan 7, 2024
@Andrew-S-Rosen Andrew-S-Rosen closed this as not planned Won't fix, can't repro, duplicate, stale Jan 7, 2024
@Andrew-S-Rosen Andrew-S-Rosen reopened this Jan 7, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@Andrew-S-Rosen