Opened 6 years ago
Last modified 6 years ago
#29046 closed Bug
possible race condition with manager logic — at Version 1
| Reported by: | Andy Grabow | Owned by: | nobody |
|---|---|---|---|
| Component: | Database layer (models, ORM) | Version: | 2.0 |
| Severity: | Normal | Keywords: | |
| Cc: | Triage Stage: | Unreviewed | |
| Has patch: | no | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
Description (last modified by )
Hi,
i tried a lot to explain this weird behaviour, but since it happens sometimes and doenst at other times i think that its due to some weird race condition.
Please have a look at the travis build logs:
https://travis-ci.org/kakulukia/django-undeletable
https://travis-ci.org/kakulukia/django-undeletable/builds/331788403 (build #23)
Most of the time django 1.11 under python2 is failing.
So please could someone with more knowledge about django manager magic have a look at my module?
git clone https://github.com/kakulukia/django-undeletable.git
git checkout cookiecutter-version
make init2
pipenv shell
pip install django=1.11.9
make test
In the last 4 years of me using that module in different projects, this bug never happend. This might be due to the striped to the basics version of this unittest compared to a project with multiple other modules to load before actually executing any ORM logic. Just a guess.
BTW: The django sources have been uploaded to pypi resulting in a python2 pip trying to install django 2 which aint working. Is there a workaround? Why are the sources uploaded to pypi?