FYI I have posted a tentative first draft of this feature, feedback is
greatly appreciated!
https://github.com/django/django/pull/16417
https://code.djangoproject.com/ticket/31300
On Saturday, February 3, 2018 at 5:06:08 p.m. UTC-7 raider...@gmail.com
wrote:
> Hey,
>
> So has this stalled? Be
of similarities between the requirements of
> generated fields and my project django-shared-property:
> https://django-shared-property.readthedocs.io/en/latest/
>
> On Sunday, December 25, 2022 at 10:23:10 AM UTC+10:30 jeremy...@gmail.com
> wrote:
>
>> I'd love to help imple
I'd love to help implement this if we can find a rough syntax! I've made a
proof of concept in Postgres, and there are two outstanding limitations to
address:
- The generated field value is not set until the model is reloaded from the
database
- The `GENERATED ALWAYS` expression requires an arg
Hi all, I'd like to propose a new django filter: *__iin*. As the name
implies, this filter finds results that match one of the given values,
ignoring case. In other words, this is a hybrid of *__in *and *__iexact*.
It surprises me that there are filters for* qs.filter(field__iexact='text')*
, *q
The Django test runner currently only displays tests that failed, and not
those that succeeded. It would be nice if Django were to print out a list
of tests that succeeded. First of all, it is satisfying to see tests
succeed. Second of all, it would be easier to debug (if certain tests were
not
An alternative that might work well is to triage tickets to mentors, so
that a list of tickets with willing mentors is available. It would feel
less judge-y than "easy pickings" and also broaden the pool of tickets that
could be worked by a newcomer. Of course it hinges on a willing pool of
mento
There is a whole section on Contributing to Django in the documentation.
https://docs.djangoproject.com/en/dev/internals/contributing/
Start by following the instructions there.
On June 22, 2017 at 1:54:52 PM, dilipchand...@eng.pdn.ac.lk (
dilipchand...@eng.pdn.ac.lk) wrote:
I'm new to this pro
Hi Xristos,
This mailinglist is for developing the django framework itself, not for
getting help with your code. If you need help with your code please see the
Django Users group:
https://docs.djangoproject.com/en/dev/internals/mailing-lists/
--
Jeremy Spencer
www.jeremyspencer.me
40googlegroups.com
> <https://groups.google.com/d/msgid/django-developers/7623cc18-d1ef-4893-9e74-e08ce8b01903%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>
--
---
Jeremy Spencer
www.jeremyspencer.me
--
633cd9-e678-4916-938e-28b7c79a1743%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>
--
---
Jeremy Spencer
www.jeremyspencer.me
--
You received this message because you are subscribed to the Google Groups
"
default in Django.
Jeremy
On Fri, Oct 14, 2016 at 7:48 PM Florian Apolloner
wrote:
> Hi,
>
>
> On Saturday, October 15, 2016 at 1:38:32 AM UTC+2, Ricardo Prado wrote:
>
> An internal montior is initialized for apply changes runtime. Would be
> good have this option in product
There is a whole section on the django website
<https://docs.djangoproject.com/en/dev/internals/contributing/> about
starting to contribute.
--
Jeremy Spencer
www.jeremyspencer.me
www.linkedin.com/in/jeremylspencer
www.facebook.com/jeremyspencerllc
On July 17, 2016 at 4:28:55 PM, Rizwan
as recommended in the
documentation.
Thanks in advance for your insights!
Jeremy
--
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 i
You can use atomic just over the section that causes the error. The issue
is that different db engines have different semantics under error during
transaction. Rolling back to the last savepoint (as atomic does when
nested) recovers the ability to complete the remainder of the transaction.
With a
I've had this scenario before - you have two interleaving units of work
(through composition of code from different sources or concerns). You want
progress recorded for one unit of work, but perhaps not the other. Without
django, you'd have two open connections. In my experience the simplest way
I suspect you have 2 different definitions of the signal under different
import paths. Ensure your python path doesn't have overlapping
directories, and that your signal imports refer to the same sys.modules key
(e.g. some_app.signals.foo all over, not proj.some_app.signals.foo and
some_app.signal
If getting proper support for other template backends would only delay the
1.8 release timeline by a couple weeks, I think that is preferable to a
generalized 1.8 backend which only include DTL until 1.9.
What do others think?
On Sat, Jan 3, 2015 at 3:23 PM, Aymeric Augustin <
aymeric.augus...@p
Thank you, Tim, for shepherding this.
On Jan 3, 2015 8:09 AM, "Tim Graham" wrote:
> Here is the fourth update with a week to go until alpha. At this time, I
> am thinking we'll have the feature freeze on Monday, January 12 as planned,
> but perhaps issue the actual alpha release a couple days lat
'class': 'django.core.files.storage.FileSystemStorage',
'trusted': False,
'OPTIONS': {
'location': settings.MEDIA_ROOT,
'base_url': settings.MEDIA_URL
}
}
}
On Mon, Sep 29, 2014 at 2:26 PM, Aymeric Augustin <
aymeric.
Right now, I think that static/media handling is fairly confused in the
documentation, and a bit confused in the code itself.
We have a few special-cases floating around:
default_storage (needed for legacy before storage backends)
staticfiles_storage (needed for collectstatic/handling)
{
As someone affected by an issue that would fall under the proposed change
[1], I still support an explicit guideline about external behavior
influencing internal acceptance. The safety of all members is more
important than the risk of misapplication of the rule.
[1]
http://doubleunion.tumblr.com/
I use this method on my own test subclasses, and I find it useful as a
tripwire: a cause for review and consideration, more than a hard error. Did
the number of queries go up on this change? Is that reasonable or a
mistake? Have we blown the perf budget so we should refactor? Or maybe the
number sh
I'm attempting to implement narrow writes (that is, writing only fields
which have changed).
I would be able to do this as a 3rd-party Mixin library if some changes
were made to Model.save_base.
1) returned whether the row was created or updated, e.g. if .save_base
returned the `updated` value
How about adding a flag to Operations? implied_null, perhaps.
On May 14, 2014 7:52 AM, "Andrew Godwin" wrote:
> Hi,
>
> That's currently the only approach I'm afraid - there's an open issue
> (raised by Shai Berger I believe) that column_sql should be broken down
> into more component pieces so i
On the None -> IS NULL issue, I presume there are, for any given use case,
not that many argument permutations of None and not None passed. I suggest
that the PreparedStatement abstraction map to multiple actual prepared
statements, one for each None/not None permutation. Then when executing,
you
2014 at 8:12 AM, Luke Plant wrote:
> On 05/03/14 23:05, Jeremy Dunck wrote:
>
> > if ...
> > elif isinstance(value, LazyObject):
> > pass
> > elif callable(value):
> > ...
>
> My gut instinct is that if Django's template code has to be patched a
I recently had a need for a LazyObject which was callable. The __call__
meta method isn't forwarded to _wrapped, so it's an error to call, even if
the underlying _wrapped does support it.
In my case, was trying to do the following:
User = SimpleLazyObject(lambda: get_user_model())
User()...
I
It may be useful to place a comment where @wraps was removed, lest some later
do-gooder "fix" it.
On Sep 17, 2013, at 12:06 AM, Marc Tamlyn wrote:
> Can't say I'm hugely worried about perfect tracebacks and introspection with
> internal kind of functions here if it affects performance. The pat
I've had this issue and have used {% with %} or moved the my.bonnet() call
into the view/context.I agree, not ideal, but I was never moved to make
it better in general.
If you're suggesting a general caching layer in the template such that a
given expression is only called once in the course o
After reading that ticket, I'm not sure what Alex and I are
disagreeing on. I was suggesting using django.utils.simplejson
internally until it's removed, so that at least people could be
consistent with django itself. That way, DjangoJSONEncoder would be a
simplejson.JSONEncoder (if simplejson is
ils.simplejson only
> being in a pending deprecation state, is broken.
>
> On Thu, Apr 11, 2013 at 9:22 PM, Alex Gaynor wrote:
>> When doing what? What do I need to do to trigger this?
>>
>> Alex
>>
>> On Apr 11, 2013 6:16 PM, "Jeremy Dunck"
ying to use something from the
> standard library with simplejson, which is obviously wrong.
>
> Alex
>
>
> On Thu, Apr 11, 2013 at 5:51 PM, Jeremy Dunck wrote:
>> I've just seen a documented example of this breaking things in the wild.
>>
>> https://github.c
I've just seen a documented example of this breaking things in the wild.
https://github.com/simplejson/simplejson/issues/37
I think we broke backwards-compat here - django 1.5.1. plus sentry
5.4.5 dies because django's own DjangoJSONEncoder depends on stdlib
json, but sentry (and lots of things)
"easy" is for people new to contributing django or to open source in
general. Your view of "easy" may be different than our intended
meaning. :)
On Mon, Apr 8, 2013 at 2:58 PM, Lennart Regebro wrote:
> On Mon, Apr 8, 2013 at 4:57 PM, Jacob Kaplan-Moss wrote:
>> Thanks, please let me know if you
Ahem:
[1] https://groups.google.com/forum/?fromgroups#!forum/django-core-mentorship
:)
On Wed, Apr 3, 2013 at 11:44 AM, Jeremy Dunck wrote:
> Hey all,
> I've just created django-core-mentorship[1] with founding members
> including Carl Meyer, Jacob Kaplan-Moss, Simon Charett
Hey all,
I've just created django-core-mentorship[1] with founding members
including Carl Meyer, Jacob Kaplan-Moss, Simon Charette, and Russell
Keith-Magee.
Modeled after pythonmentors.com, the intention is to help more
people make the leap from using django to contributing to it. It is a
com
I'm not sure what you mean by "maps to".
The basic signal framework is in django.dispatcher. If you're
implementing https://code.djangoproject.com/ticket/11398 then you
probably want to import: from django.dispatcher import Signal.
django.db imports django.core.signals because it is a *consumer*
It sounds like we need a way to tell the worker that we are done sending
requests to it so that the worker can do cleanup (of which db conn close is one
task). This mirrors the previous request_finished "coupling" to
requests_finished.
(OS?) Signal? Sentinel queue/socket/named pipe + backgroun
I, for one, would prefer that we not recommend TransactionMiddleware
so highly. Now that I'm doing active development with Rails, it's
quite clear to me that a major difference in the ORM layers are which
DB they grew up with -- the django orm is tuned best to postgres,
while working passably on m
I'm not sure what you're referring to here - integrity, uniqueness,
and locking are handled at the individual query level - transactions
just cause locks to be held (if needed) until commit or rollback. Can
you give a concrete example of an exception being raised at commit
time?
On Tue, Mar 5, 2
On Mon, Mar 4, 2013 at 1:34 AM, Aymeric Augustin
wrote:
> On 4 mars 2013, at 01:07, Shai Berger wrote:
...
>> The use of savepoints in Django apps so far has been very little, as far as
>> I know. One point
>> I'm unsure of is the interaction of savepoints with cursors, since querysets
>> are l
Please do not send recruitment emails to this mailing list. This is
your one warning. Repeating will result in you being banned from the
list.
On Fri, Jan 25, 2013 at 12:47 PM, wrote:
> We are looking for a Full stack engineer with strong python and django
> development skills. Our client is a
For the record: It's bad timing for Idan. He lives in Tel Aviv which
is currently receiving intermittent rocket attacks. He may be a bit
slow to respond. ;)
Let's wish him and his family safety and the luxury of worrying about
django's admin in good time.
On Thu, Nov 15, 2012 at 7:23 AM, Victo
+1, this looks like a good change anyway and doesn't smell to me.
On Fri, Nov 16, 2012 at 6:09 AM, Daniel Sokolowski
wrote:
> I like this approach.
>
> From: George Hickman
> Sent: Thursday, November 15, 2012 7:27 AM
> To: django-developers@googlegroups.com
> Subject: Re: Class based views: A sta
If you use/monitor/graph metrics (the idea, not Coda's library, but that
would be good, too), I'd like to hear from you.
What sort of metrics, under what implementation, would be useful to you
operationally?
--
You received this message because you are subscribed to the Google Groups
"Django de
Would it be reasonable to have a backend-specific hook to determine a
fingerprint, where that could be mtime or md5 or whathaveyou as long as
equality (or maybe ordering) works?
On Oct 8, 2012, at 10:23 AM, Alex Ogier wrote:
> On Mon, Oct 8, 2012 at 1:06 PM, ptone wrote:
> While git may be
I was searching around for a different old blog post and found this one:
http://jacobian.org/writing/why-django/
It made me smile - we've come a ways since then. :)
--
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group, sen
On Tue, Sep 18, 2012 at 11:23 AM, Jeremy Dunck wrote:
...
> And the last one, I hesitate to raise because it's likely to be
> specific to my machine, but... our (django-nose-based) test runner
> hangs after completing the suite but before tearing down. Using
> dtruss I can se
In response to the call to test py2.x on django's current master, I
ran the test suite for Votizen. Our codebase is currently running
with django 1.4.x.
Our codebase is ~100kloc, ~32kloc of which is tests. We use abstract
model inheritance a good bit, but no concrete inheritance. No i18n or
mul
On Thu, Sep 6, 2012 at 12:16 PM, Anssi Kääriäinen
wrote:
> On 3 syys, 07:40, Anssi Kääriäinen wrote:
>> I would like to make the TransactionTestCase faster. Currently when
>> running Django's test suite, for every test ran you will truncate
>> around 1000 tables, then create around 4000 objects (
I have been working on a master/slave router library [1] and have run
into some trouble testing a client application of it.
The issue is that TestCase (as designed) holds test db writes in a
transaction, but the read slave connection (which is to the same DB
under TEST_MIRROR) does not have visibi
That sounds good to me, though I'm not a committer on the tree as far
as I know. Anssi?
On Fri, Aug 10, 2012 at 8:12 AM, Flavio Curella
wrote:
> Just to clarify, the plan is:
>
> 1) Merge in patch v8 (2d index for 2-dimensional fields, _nd index for 3D
> and up)
> 2) Open a new ticket for the
On Thu, Aug 9, 2012 at 2:42 PM, Flavio Curella wrote:
> From the benchmark, my understanding is that, on PostGIS 2.0:
>
> 1) for the 2D case, the best index is 'gist (columname)'
> 2) for the 3D case, the best index is 'gist (columname
> gist_geometry_ops_nd)' only when using specific 3D operators
I'm fairly familiar with the django gis code, but I haven't been
following postgis 2.0. Could you point me towards some discussion of
the index changes from 1.5 to 2.0? On the face of it, I'm doubtful
that they've removed a useful form of indexing with no
replacement/alternative.
It's hard for m
>>
>> Obviously this page would need to be kept up to date - maybe even just
>> "some people said these things about Django best practices, read these
>> blogposts for information" would be fine - just some starting pointers. I
>> know especially on Wi
Can I get a review of the branch? 25% performance improvement of
Model.__init__ in stock django seems worth landing. :)
On Wed, Jul 18, 2012 at 3:48 AM, Jeremy Dunck wrote:
> On Sun, Jul 15, 2012 at 11:07 AM, Jeremy Dunck wrote:
>>
>> That is indeed what I meant, but I think A
On Thu, Jul 26, 2012 at 11:26 PM, Anssi Kääriäinen
wrote:
> On 27 heinä, 08:15, Jeremy Dunck wrote:
...
>> I would have expected something along the lines of :
>>
>> DELETE FROM `api_voter_districts` WHERE `voter_id` = 1
>>
>> But instead it's 2 queries:
I have 2 models:
class District(Model):
pass
class Voter(Model):
districts = ManyToManyField(District)
Sometimes I want to reset the m2m list:
voter.districts = other_districts
I noticed that this uses ManyRelatedManager._clear_items, which, among
other things, boils down to:
voter.distr
On Sun, Jul 15, 2012 at 11:07 AM, Jeremy Dunck wrote:
>
> That is indeed what I meant, but I think Anssi's probably right that
> this belongs in contribute_to_class instead of a new adhoc thing in
> ModelBase.__new__.
>
> I'll take a swing at making this change.
>
On Fri, Jun 8, 2012 at 7:57 AM, Anssi Kääriäinen
wrote:
> On 8 kesä, 17:28, Luke Plant wrote:
>> First, thanks so much to Aymeric and Anssi and others for the
>> contribution guidelines, they're very helpful.
>>
>> I've got some questions that are due to my ignorance of git (I have
>> managed to
I noticed this hasn't made it to master yet. Could it? I'm running
sprints and there's a bit of confusion on how to contribute to git.
Cheers,
Jeremy
On Thu, Jun 7, 2012 at 9:53 AM, Aymeric Augustin
wrote:
> On 6 juin 2012, at 21:09, Anssi Kääriäinen wrote:
>> I am s
.
I could go either way - my preferred approach isn't right in all
cases, and it might seem a distraction to the absolute beginner or a
person who has their own opinions.
On Mon, Jul 16, 2012 at 11:15 PM, Aymeric Augustin
wrote:
> 2012/7/16 Jeremy Dunck :
>> On August 4, Py
they want to fill
collaborate on a new outline
split off for specific prose writing
then final edit pass (or 2) to fix editorial voice/congruence problems
If you would like more information or disagree with the general
direction, please speak up.
Cheers,
Jeremy
--
You received this message be
certain fields in ModelBase, then it means that third-parties with the
>> same requirement won't be able to exploit the same API entry point. In
>> the case of GenericForeignKey specifically, it also means that we
>> would be introducing a dependency (even if it was name-onl
I was poking around in our (Votizen's) use of signals and thinking
about making some tooling so that signal usage was a bit more
transparent.
In doing so, I noticed that GenericForeignKey hooks the model pre_init
signal. It does that because GFK needs a chance to munge kwargs from
the GFK field n
On Jun 28, 2012, at 6:57 AM, Luke Plant wrote:
> Hi all,
>
> 2) Any better name than 'html_fragment'?
>
I like the general approach, but I miss the security-minded namse of "escape"
and "mark safe". Maybe "safe_html_fragment" or "make_safe_html_fragment"?
Getting annoyingly long, I know.
I've just opened signup for our 2nd sprint - Saturday, June 16th, from
10a to 6p:
http://sfdjangosprint2.eventbrite.com/
Please sign up if you plan to attend -- it's free of course.
On Tue, May 22, 2012 at 2:30 PM, Jeremy Dunck wrote:
> My company, Votizen, now has an office in
or beverage, I'll make
sure you're publicly noted and thanked.
To all who came, thank you for contributing to the core and the
community. To all who didn't, please consider joining us next time.
I'll be putting up a signup form for the next one shortly.
Cheers,
Jeremy
[1]
https
On Fri, Apr 20, 2012 at 9:01 AM, Anssi Kääriäinen
wrote:
> On Apr 12, 10:27 pm, Anssi Kääriäinen wrote:
>> > So perhaps we do need the signal inheritance behavior to be opt-in when
>> > connecting the signal handler. I think I'd like to see a deprecation
>> > path so that eventually the inheritan
On Fri, Jun 1, 2012 at 2:26 AM, Russell Keith-Magee
wrote:
> On Fri, Jun 1, 2012 at 8:53 AM, Jeremy Dunck wrote:
...
>> Candidate.context('site') would return a manager depending on the
>> requested context.
>> (or perhaps Candidate.obje
It feels to me that each place that ._default_manager is mentioned
here is a misfeature:
https://github.com/django/django/blob/2cd516002d43cdc09741618f0a0db047ee6d78fd/django/db/models/fields/related.py
As an example, we (Votizen) currently have some default managers which
show subsets of all obje
My company, Votizen, now has an office in San Francisco, just a block
from the 4th St Caltrain station. We have room to host sprints -
easily 25 people, though we can grow if there is demand. We have a
professional kitchen, great coffee gear, and maybe a kegerator soon.
There are many great place
On Tue, May 8, 2012 at 9:33 AM, Alex Ogier wrote:
> My guess is that Django is doing some normalization on the name you are
> importing. It does this to prevent double imports, for example importing
> 'projectname.appname' and 'appname' which would otherwise be considered
> separate modules even i
On Thu, Apr 12, 2012 at 3:06 PM, Craig Lucas wrote:
> i have developed a database for a client that uses camel casing in the
> database. we are now trying to get a models.py file to mimic the
> database structure and i have run into a few bugs with regards to
> using quoted table names.
>
> The fi
On Thu, Apr 12, 2012 at 9:31 AM, Carl Meyer wrote:
> Hi all,
>
> There's a discussion ongoing on ticket #18094
> (https://code.djangoproject.com/ticket/18094) that has enough potential
> back-compat implications that it seems worth getting feedback here.
Small note, I'll try to respond to the who
On Mon, Mar 19, 2012 at 11:17 PM, Tim Diggins wrote:
> Hi -
>
> I'm wondering what the lines at the end of django/db/models/
> deletion.py do:
>
> for model, instances in self.data.iteritems():
> for instance in instances:
> setattr(instance, model._meta.pk.attname
On Thu, Mar 1, 2012 at 9:28 PM, Carl Meyer wrote:
> The "only_fields" kwarg suggestion comes from ticket 4102, and it is
> primarily intended as a performance optimization for large models by
> only sending the values of certain fields to the database at all,
> something that your proposed co
You've mailed the django-developers list which is for development *of
Django itself*. The proper mailing list about *using* Django is
django-users. Please send this message to django-users unless you're
proposing a change to Django.
http://groups.google.com/group/django-users
On Mon, Feb 27,
On Sat, Feb 25, 2012 at 2:13 AM, Anssi Kääriäinen
wrote:
> On Feb 25, 9:24 am, Jeremy Dunck wrote:
>> I have a master and a replica. In test, the TEST_MIRROR on the
>> replica points to master. I make writes to master, then read from
>> replica, then assert some numbers.
I have a master and a replica. In test, the TEST_MIRROR on the
replica points to master. I make writes to master, then read from
replica, then assert some numbers.
def test_stuff(self):
Foo.objects.using('master').create()
number_received = do_expensive_computations()
# Down in some
On Thu, Jan 19, 2012 at 5:14 PM, Adrian Holovaty wrote:
> On Wed, Jan 18, 2012 at 1:07 PM, Shai Berger wrote:
>> I have a small improvement to suggest for one-to-one fields: Make them cache
>> back-references on related objects. That is, assume
>
> Yes! Good improvement. And we should do the same
There's a known problem w/ latest pg (2.4.2) and we decided not to
backport the fix to 1.3.x because there's a workaround.
https://code.djangoproject.com/ticket/16250
All well and good, but someone coming to Django w/ postgres will have
a bad first-run experience because the docs don't mention th
On Wed, Jan 18, 2012 at 11:07 AM, Shai Berger wrote:
> Do you see a reason why I should not post a ticket?
+1
--
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group, send email to django-developers@googlegroups.com.
To unsu
On Sun, Jan 8, 2012 at 2:57 PM, Arnoud van Heuvelen
wrote:
...
> 3) Save the password hash (or part of it) in the session and compare
> it against our data. If the hash is not the same, the user needs to be
> logged out. This wouldn't change the database, but the downside is
> that this causes ove
Hello all,
My apologies for the silence on the sprint plans - holidays and all that.
I'm back to looking for space for the sprint - Bitbucket has only
recently moved into their new space and are still settling in. Thanks
to them for the initial offer.
In light of that, I'd like to push the
Hi Ryan,
Actually, I'm still looking to firm up plans. I should have sent
info earlier - I'm sorry about that.
I'm now hoping to run the sprint Jan 21-22. It may be at
Bitbucket's office, or it may not. I'll follow up with more specifics
on this tomorrow if at all possible.
On Mon, Jan 2,
On Thu, Dec 29, 2011 at 12:10 PM, Paul McMillan wrote:
...
>> That seems like a simpler workaround than arch upgrade or replacing
>> dict implementation.
>
> This problem has nothing to do with slowloris.
>
> Replacing dict implementation prevents an attacker from producing keys
> which are intent
On Thu, Dec 29, 2011 at 8:19 AM, Christophe Pettus wrote:
...
> It's an interesting result, but I'm not sure how much to be worried about it
> in the field. A SlowLoris or similar attack would seem to be far more
> effective and less implementation-dependent.
Slow Loris can be avoided by putti
On Mon, Dec 26, 2011 at 4:33 PM, Etienne Robillard wrote:
> What thus you Django developers all think of this proposed law and how could
> this may affect open source communities such as Django and Python
> to develop novel apps specifically for creating user-generated content?
This feels off-top
I suppose I should read the whole doc and not just ctrl-F before reporting
omissions. :)
On Dec 25, 2011, at 10:03 PM, Karen Tracey wrote:
> On Mon, Dec 26, 2011 at 12:58 AM, Jeremy Dunck wrote:
> I think Multi-TZ should get soms love in the release notes.
>
I think Multi-TZ should get soms love in the release notes.
https://code.djangoproject.com/changeset/17106
https://docs.djangoproject.com/en/dev/releases/1.4-alpha-1/
Was it an oversight?
--
You received this message because you are subscribed to the Google Groups
"Django developers" group.
T
On Mon, Dec 5, 2011 at 7:28 AM, Carl Meyer wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On 12/05/2011 08:10 AM, Vinay Sajip wrote:
>> Not too bad for a first complete pass. Over two and a half hours to
>> run, and that' s running from /dev/shm (IIUC effectively RAMdisk) and
>> with
On Sun, Dec 4, 2011 at 5:10 PM, Vinay Sajip wrote:
>
> On Dec 5, 12:57 am, Anssi Kääriäinen wrote:
>
>> There is one easy thing you can do for testing, set fsync to off in
>> postgresql.conf. The file is probably at /etc/postgresql/9.1/main/
>> postgresql.conf. Then restart the server and tests s
On Sat, Dec 3, 2011 at 1:27 PM, Brodie Rao wrote:
> Bitbucket/Atlassian would love to host a sprint. We're about to move
> from the Mission to our own office building in SoMa in a couple of
> weeks. We'll have plenty of space for anyone who wants to attend.
Thanks for the offer, Brodie. I'll wri
On Sat, Dec 3, 2011 at 7:59 PM, Russell Keith-Magee
wrote:
> On Saturday, December 3, 2011, Jeremy Dunck wrote:
>> Hey all,
>> With the 1.4 release coming up, I thought it'd be a good time to
>> schedule a sprint to get in any ponies or help shake out bugs.
>
>
'm just getting started with the plan. I'm
coordinating w/ David Cramer who orgs the SF meetup.
I assume meeting in the city proper would be better for attendance,
but we could also probably go to Hacker Dojo in Mountain View. Do
people feel strongly about this?
Cheers,
Jere
On Wed, Nov 30, 2011 at 2:26 PM, Adrian Holovaty wrote:
> Just to be clear, how would you get the "diff" of what's changed?
> Would it automatically change the fixture files after you close the
> shell session? Or would that be up to you?
Yes, I was thinking of catching SystemExit, KeyboardI
On Wed, Nov 30, 2011 at 11:30 PM, Aymeric Augustin
wrote:
...
> In my current job we're using https://github.com/rbarrois/factory_boy, we've
> dropped all but the most trivial fixtures (sites, languages, an admin user),
> and we haven't looked back.
Nifty, thanks.
--
You received this message
Hi all,
I've got a codebase with a fair bit of fixtures and have been
experiencing some pain around it. One of the pains is migrating the
format of fixtures when a schema change occurs.
I posted a thread to south-users to discuss the idea of adding a
feature to aid applying migrations to fixt
On Sun, Oct 30, 2011 at 4:19 PM, Jeremy Dunck wrote:
> On Sun, Oct 30, 2011 at 8:48 AM, Jim Dalton wrote:
> ...
>> Anyhow, I honestly agree with you and Aymeric that a simple cache.clear() is
>> fine, but I thought the CLEAR_BETWEEN_TESTS flag was a good way to answer
>>
1 - 100 of 609 matches
Mail list logo
