docs: Switch to project_copyright

[jmgate]

Type: Documentation

Description

Using this alias means we're no longer overshadowing the copyright built-in, so we can remove the comment to ignore that Ruff linting rule.

Summary by Sourcery

Documentation:

• Replaced the usage of the built-in copyright with project_copyright.

[sourcery-ai]

Reviewer's Guide by Sourcery

The pull request renames the copyright variable to project_copyright in the conf.py file to avoid shadowing the built-in copyright keyword. This change also removes the need to ignore the Ruff linting rule.

Class diagram showing configuration variable change

classDiagram
    class conf.py {
        +String project
        -String copyright (removed)
        +String project_copyright (added)
        +String author
    }
    note for conf.py "Renamed copyright to project_copyright to avoid shadowing built-in"

Loading

File-Level Changes

Change	Details	Files
Renamed the copyright variable to project_copyright.	Renamed the copyright variable to project_copyright. Removed the noqa: A001 comment.	doc/source/conf.py

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time. You can also use
  this command to specify where the summary should be inserted.

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[sourcery-ai]

Hey @jmgate - I've reviewed your changes and they look great!

Here's what I looked at during the review

• 🟢 General issues: all looks good
• 🟢 Security: all looks good
• 🟢 Testing: all looks good
• 🟢 Complexity: all looks good
• 🟢 Documentation: all looks good

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 93.97%. Comparing base (907370e) to head (d0a21d5).
Report is 2 commits behind head on master.

Additional details and impacted files

@@           Coverage Diff           @@
##           master     #258   +/-   ##
=======================================
  Coverage   93.97%   93.97%           
=======================================
  Files           2        2           
  Lines         166      166           
  Branches       37       37           
=======================================
  Hits          156      156           
  Misses          4        4           
  Partials        6        6           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[jmgate]

@william76, @GhostofGoes, @jcox10, anyone care to review and approve?

[GhostofGoes]

Is this variable referenced anywhere?