Skip to content

on_after_finalize documentation just repeats the name. #7280

Description

@boatcoder

Checklist

  • I have checked the issues list
    for similar or identical bug reports.
  • I have checked the pull requests list
    for existing proposed fixes.
  • I have checked the commit log
    to find out if the bug was already fixed in the master branch.
  • I have included all related issues and possible duplicate issues in this issue
    (If there are none, check this box anyway).

Related Issues and Possible Duplicates

  • None

Related Issues

  • None

Possible Duplicates

  • None

Description

Suggestions

I'd suggest using finalize in a way that fits with a normal definition but that might be a big ask considering all the existing code and people using it. So maybe it could just be described better. Basically I'm trying to use on_after_configure.connect and that appears to be too early in the run to be importing things from tasks.py. So I can here looking to see if I could use on_after_finalize based on this page which mentions it, but now I'm not sure what finalize means anymore....

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions