Add support for django 4.2

[irtazaakram]

Description

This is related to ongoing effort to update to Django 4.2 in openedx.
edx/upgrades#381

Supporting information

Changes:

problem_builder/tests/unit/test_answer_mixin.py

• https://github.com/django/django/blob/f474ba4cb52a41a62da6d6fb3492a95eeb8b3999/django/utils/crypto.py#L51
  bit length is required argument for get_random_string in 4.2

pylintrc

pylint: Command line or configuration file:1: UserWarning: Specifying exception names in the overgeneral-exceptions option without module name is deprecated and support for it will be removed in pylint 3.0. Use fully qualified name (maybe 'builtins.BaseException' ?) instead.

Can we also have a new release when this PR is merged?

Thanks,

[codecov]

Codecov Report

Patch coverage: 50.00% and no project coverage change.

Comparison is base (42c2d2f) 45.08% compared to head (c0cee35) 45.08%.

Additional details and impacted files

@@           Coverage Diff           @@
##           master     #359   +/-   ##
=======================================
  Coverage   45.08%   45.08%           
=======================================
  Files          40       40           
  Lines        3309     3309           
  Branches      463      463           
=======================================
  Hits         1492     1492           
  Misses       1769     1769           
  Partials       48       48           

Flag	Coverage Δ
unittests	45.08% <50.00%> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

Files Changed	Coverage Δ
problem_builder/dashboard.py	24.26% <0.00%> (ø)
problem_builder/__init__.py	100.00% <100.00%> (ø)

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

[Agrendalath]

Thank you for your contribution, @irtazaakram!

Can we also have a new release when this PR is merged?

Please see this comment. I explained why we don't need to update the version in such a case. We mistakenly include the tests in the Python package in this repository, but we do not use them anywhere.

[irtazaakram]

Hi @Agrendalath,

Thanks for the review. I've added integration test for Django 4.2. Let me know if this is the right approach.

Thanks,

[Agrendalath]

@irtazaakram, the approach looks good, but I'd like to understand where these additional changes (mentioned in the review comments) come from.

[Agrendalath]

👍

• I tested this: checked that the CI uses Django 3.2 and 4.2.
• I read through the code
• I checked for accessibility issues: n/a
• Includes documentation: n/a
• I made sure any change in configuration variables is reflected in the corresponding client's configuration-secure repository: n/a