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

Sync with upstream #4

Closed
wants to merge 23 commits into from
Closed

Sync with upstream #4

wants to merge 23 commits into from

Conversation

aleksandr-shtaub
Copy link

Drop all peopledoc commits

rbarrois and others added 23 commits March 9, 2020 18:37
- Drop Python2
- Only test Django 1.11 on Python3
- Only test the latest Django version (3.0) and the previous LTS (2.2)
- Remove python2_unicode_compatible
- Drop unicode/str conversions
- Replace ugettext_lazy with gettext_lazy, since the `unicode` class no
  longer exists;
- Rename `MIDDLEWARE_CLASSES` to `MIDDLEWARE`
Use `./manage.py test` instead of a custom runner setup.
Include migrations for the `djworkflows` project.
Semantically closer to the actual goal.
Only keep the "Build with Makefile" part in setup.py, as that part is
required for properly compiling the .po/.mo files.

Requirements are now described in extras, relying only on the standard
supported tools.
A package's `sdist` archive should contain all files required for
building said projects, including tests, docs, etc.
Use a standardized package layout, with centralized tool configuration.
Also add a `docs` check environment.

Note: explicit installation of `gettext` is now required.
Not supported on Github Actions.
Django 3.x requires Python >= 3.6
Due to CI limitations, it is no longer possible to test the code with
Python 3.4.
With Django 3.2, projects must specify whether the implicit autofield
used for models is an integer or a big integer.
Since that doesn't actually matter in our test setup, simply use the
recommended BigAutoField.

Note that this change has no effect on the default "Workflow transition
log" models.
XWorkflows recommends not using `@transition(..., after=)` for quite
many releases; replace this pattern with the supported
`@after_transition` pattern.
In order to quickly detect pending deprecation warnings in our
supporting libraries, mark warnings as errors in our automated testing
setups.
There is a small typo in docs/index.rst.

Should read `functionalities` rather than `functionnalities`.
@aleksandr-shtaub aleksandr-shtaub deleted the sync-with-upstream branch January 17, 2024 10:21
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.

3 participants