So, the contributor guidelines page about unit tests mentions running
database specific tests:
https://docs.djangoproject.com/en/2.1/internals/contributing/writing-code/unit-tests/#testing-other-python-versions-and-database-backends
I am working on ticket 29984, and it seems to me that since the
I just joined as a contributor, but I've shipped an appliance install
running using rpms, anaconda (the other one), and pungi. Depending on
sqlparse doesn't seem to me a big deal. It already gets invoked for me
during migrations. I cannot recall what caused it to be installed. One
thing we
OK - why borrow trouble. There is plenty to do just maintaining current
interfaces, and adding major features - like the new db functions in 2+.
On Saturday, November 3, 2018 at 7:36:00 PM UTC-4, Adam Johnson wrote:
>
> I have code in my package Django-MySQL that uses the internals of
> queryset
I have code in my package Django-MySQL that uses the internals of
querysets. It’s not so bad to maintain with enough test coverage and
ensuring it keeps up to date with the latest Django. The fact the interface
is private means that it could change at any time, but practically that
doesn’t mean oft
Week ending November 3, 2018
Triaged
---
https://code.djangoproject.com/ticket/29904 - Not Null CharField Doesn't
generate DB constraint on Oracle (invalid)
https://code.djangoproject.com/ticket/29908 - Foreign key isn't set on
object after related set access if ForeignKey uses to_field
I was thinking of providing a package containing a couple of DRF renderers
that work directly from querysets. DRF Serializers are great when you
need to render a hierarchical structure, and/or when you expect to parse a
POST body containing the structure. For returning non-hierarchical
resul
Hi All,
I saw Carlton's short keynote at DjangoCon last month and he suggested that
I message this group.
I'm one of the maintainers of Django-Pgcrypto-Fields which offers field
level encryption using the PostgeSQL pgcryto library. We support Django
1.11, and 2+ including filtering, aggregates
> So you want to add it to Django's install_requires even though it won't
be necessary if SQLite isn't used?
That's my understanding and what I was advocating for.
Simon
Le samedi 3 novembre 2018 10:09:55 UTC-4, Tim Graham a écrit :
>
> So you want to add it to Django's install_requires even th
This mailing list is for the development of Django itself, not for support.
Use the django-usersmailing list for that, or IRC #djangoon freenode, or a
site like StackOverflow.
On Sat, 3 Nov 2018 at 13:48, Elias Coutinho
wrote:
> Good morning people.
>
> As always my problem is conceptual. I have
This mailing list is for the development of Django itself, not how to solve
problems with Django. Please don't cross-post from django-users.
On Saturday, November 3, 2018 at 9:57:41 AM UTC-4, Elias Coutinho wrote:
>
> Good morning people.
>
> As always my problem is conceptual. I have improved a
So you want to add it to Django's install_requires even though it won't be
necessary if SQLite isn't used? It seems okay to me. It's an extra 40k or
so of disk space but that's not much compared to all the extra stuff Django
comes with that every Django project doesn't necessarily use. We also h
Good morning people.
As always my problem is conceptual. I have improved a lot, but still in the
fight.
1 - I have a list of data and I know how to add it to another model at one
time. (Easy)
2 - It turns out that in this list some data will be filled by the user
before saving and will be repea
12 matches
Mail list logo