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.

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

upgrade to Python 3.11 and Django 4.2 #435

Merged
merged 1 commit into from
Apr 17, 2024
Merged

Conversation

TimidRobot
Copy link
Member

@TimidRobot TimidRobot commented Apr 17, 2024

Fixes

Description

upgrade to Python 3.11 and Django 4.2

Technical details

  • Django 4.2 release notes | Django documentation | Django
  • Python module changes:
    --- piplist.old	2024-04-17 10:56:22
    +++ piplist.new	2024-04-17 10:56:22
    @@ -6 +6 @@
    -black                24.3.0
    +black                24.4.0
    @@ -15 +15 @@
    -Django               3.2.25
    +Django               4.2.11
    @@ -18,2 +18,2 @@
    -Faker                24.4.0
    -filelock             3.13.3
    +Faker                24.11.0
    +filelock             3.13.4
    @@ -25 +25 @@
    -idna                 3.6
    +idna                 3.7
    @@ -45 +44,0 @@
    -pytz                 2024.1
    @@ -48 +47 @@
    -regex                2023.12.25
    +regex                2024.4.16
    @@ -50 +49 @@
    -setuptools           69.2.0
    +setuptools           69.5.1
    @@ -54 +53 @@
    -sqlparse             0.4.4
    +sqlparse             0.5.0
    @@ -56 +54,0 @@
    -tomli                2.0.1
    @@ -59 +56,0 @@
    -typing_extensions    4.10.0
    @@ -61 +58 @@
    -virtualenv           20.25.1
    +virtualenv           20.25.3

Tests

  1. coverage
    ./dev/coverage.sh
    Name    Stmts   Miss Branch BrPart    Cover   Missing
    -----------------------------------------------------
    TOTAL    1662      0    616      0  100.00%
    
    20 files skipped due to complete coverage.
    
  2. publish
    docker compose exec app ./manage.py publish -v2
    • confirmed there were no changes to published files

Screenshots

Checklist

  • My pull request has a descriptive title (not a vague title like Update index.md).
  • My pull request targets the default branch of the repository (main or master).
  • My commit messages follow best practices.
  • My code follows the established code style of the repository.
  • I added or updated tests for the changes I made (if applicable).
  • I added or updated documentation (if applicable).
  • I tried running the project locally and verified that there are no
    visible errors.

Developer Certificate of Origin

For the purposes of this DCO, "license" is equivalent to "license or public domain dedication," and "open source license" is equivalent to "open content license or public domain dedication."

Developer Certificate of Origin
Developer Certificate of Origin
Version 1.1

Copyright (C) 2004, 2006 The Linux Foundation and its contributors.
1 Letterman Drive
Suite D4700
San Francisco, CA, 94129

Everyone is permitted to copy and distribute verbatim copies of this
license document, but changing it is not allowed.


Developer's Certificate of Origin 1.1

By making a contribution to this project, I certify that:

(a) The contribution was created in whole or in part by me and I
    have the right to submit it under the open source license
    indicated in the file; or

(b) The contribution is based upon previous work that, to the best
    of my knowledge, is covered under an appropriate open source
    license and I have the right under that license to submit that
    work with modifications, whether created in whole or in part
    by me, under the same open source license (unless I am
    permitted to submit under a different license), as indicated
    in the file; or

(c) The contribution was provided directly to me by some other
    person who certified (a), (b) or (c) and I have not modified
    it.

(d) I understand and agree that this project and the contribution
    are public and that a record of the contribution (including all
    personal information I submit with it, including my sign-off) is
    maintained indefinitely and may be redistributed consistent with
    this project or the open source license(s) involved.

@TimidRobot TimidRobot self-assigned this Apr 17, 2024
@TimidRobot TimidRobot requested review from a team as code owners April 17, 2024 18:05
Copy link
Member

@Shafiya-Heena Shafiya-Heena left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you!!

@TimidRobot TimidRobot merged commit 556605d into main Apr 17, 2024
2 checks passed
@TimidRobot TimidRobot deleted the python-3-11-and-django-4-2 branch April 17, 2024 18:30
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