Ningú

Results 73 comments of Ningú

Such PR essentially removing this amount of compatibility boilerplate and still passing the test suite for python 3.6-3.10 and pypy can only be approved! Looks Very Good To Me. I...

Bear with us, StaleBot, for this issue is pinned! Can someone add whatever label is due?

Indeed, this https://docs.ansible.com/ansible/latest/modules/postgresql_privs_module.html is the module that implements this feature

FWIW, we extended the anxs.postgresql role with an aditional task that implements this: ``` - name: PostgreSQL | Update privileges postgresql_privs: db: "{{item.db}}" objs: "{{item.objs | default(omit)}}" privs: "{{item.privs |...

The tests can be reduced so something like ``` from django.core.management import call_command def test_migrations(db): call_command("makemigrations", "--check", "--dry-run") def test_check(db): call_command("check", "--fail-level", "WARNING") ``` I am somewhat bored of copypasting...

> I am currently on a hunt to figure out if there's a better way to bind typevars to class members or metaclass members @tgross35 My actual factory declarations are...

``` class Data(factory.DictFactory): coordinates = factory.Dict({ "lat": factory.Faker("pyfloat", max_value=90, min_value=-90), "lng": factory.Faker("pyfloat", max_value=180, min_value=-180), }) ``` Indeed, composing values from params and other declarations is sometimes cumbersome, but I am...

> One more note, I understand the intended use case for factory_boy is for generating test fixtures. I suppose I am somewhat abusing it in the first place, as I...

The function that recalls what you are asking would be the `instantiate` method from the options class. You could always override it like ``` import factory.django class HackyOptions(factory.django.DjangoOptions): def instantiate(self,...

I think repeating the ``` if session_persistence == SESSION_PERSISTENCE_FLUSH: session.flush() elif session_persistence == SESSION_PERSISTENCE_COMMIT: session.commit() ``` block in the `use_postgeneration_results`/`_after_postgeneration` functions would fix this, but the challenge is being aware...