STY: Import PageAttributes as PG not PA

[j-t-1]

For codebase consistency.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 96.95%. Comparing base (01c98a5) to head (67acbff).
⚠️ Report is 52 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #3402      +/-   ##
==========================================
- Coverage   96.96%   96.95%   -0.01%     
==========================================
  Files          55       55              
  Lines        9343     9341       -2     
  Branches     1708     1708              
==========================================
- Hits         9059     9057       -2     
  Misses        169      169              
  Partials      115      115              

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

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[stefan6419846]

I would prefer to refactor all calls to use PageAttributes as PA - PG is somehow confusing in this context. This will conflict with PagesAttributes currently being imported as PA, thus it might need further discussions.

[j-t-1]

Agree; the reason I found this was because of confusion about PA vs PG.

Suggestions:

from .constants import PagesAttributes

from .constants import PagesAttributes as PPA

[stefan6419846]

Another thought: Do we need these abbreviations at all? Or could we just use the full name here to avoid confusion completely?

[j-t-1]

Like it.

In this PR could do this:

from .constants import PagesAttributes as PA -> from .constants import PagesAttributes

Then codebase is consistent, and any further removal done in other PRs.