so _that's_ why I've been adding zip_safe=False to all my setups for
years :P
+1 to encouraging the world to move forward :)
--
Curtis
On 14 July 2015 at 10:40, Russell Keith-Magee wrote:
>
> On Mon, Jul 13, 2015 at 11:00 PM, Donald Stufft wrote:
>>
>> I’m fine with this, but just be warne
On Mon, Jul 13, 2015 at 11:00 PM, Donald Stufft wrote:
> I’m fine with this, but just be warned that it does mean anything
> that ships a Django app will need a zip_unsafe=True or else they
> no longer support being installed with easy_install.
... and I'm sure both the people who still use eas
Created ticket: https://code.djangoproject.com/ticket/25120#ticket
On Monday, July 13, 2015 at 11:01:08 AM UTC-4, Donald Stufft wrote:
>
> I’m fine with this, but just be warned that it does mean anything
> that ships a Django app will need a zip_unsafe=True or else they
> no longer support bein
Wouldn't it be enough to just have link to the correct PostgreSQL site:
http://www.postgresql.org/docs/current/static/non-durability.html
And then some text with "if you want to run your tests on postgresql please
see the docs around non durable postgres"
2015-07-13 18:46 GMT+02:00 Federico Capoan
Sure, i've just done something similar for this project:
http://nodeshot.readthedocs.org/en/latest/topics/install_development.html#how-to-setup-the-test-environment
The *keepdb* option allows to avoid recreating the test database at each
run, hence saving precious time.
If you want to speed up t
Hello Federico,
2015-07-13 16:26 GMT+02:00 Federico Capoano :
> While these are the winners:
>
>- fsync = off
>- synchronous_commit = off
>- full_page_writes = off
>
> Would you like to submit a patch to docs/ref/databases.txt, in the
"PostgreSQL
notes" section, explaining this config
I’m fine with this, but just be warned that it does mean anything
that ships a Django app will need a zip_unsafe=True or else they
no longer support being installed with easy_install.
On July 12, 2015 at 10:53:20 AM, James Bennett (ubernost...@gmail.com) wrote:
> There's not much to this, really,
+1. Eggs have reached the point of obsolescence.
--
You received this message because you are subscribed to the Google Groups
"Django developers (Contributions to Django itself)" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to django-developers+unsubsc
