ango-developers+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/django-developers/0c6ca059-d50e-4c84-bef6-ab0742fc4fa9n%40googlegroups.com
> <https://groups.google.com/d/msgid/django-developers/0c6ca059-d50e-4c84-bef6-ab0742fc4fa9n
Hi Albert,
I think you are going in the wrong direction here; We should leave the 'pk'
alias in place, not because it would be hard to remove, and not because it
exists in many places, but because aliasing is a stonking great idea.
It exists in many places for precisely that reason ; its such a
Contributions to Django itself)" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to django-developers+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/django-developers/20210415213200.7
to django-developers+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/django-developers/CAEE%2BrGqvVXrAZbWwuieitTVTNuKzR%2B%2BWWqc-6HsO4LO0OhvEog%40mail.gmail.com
> <https://groups.google.com/d/msgid/django-developers/CAEE%2Br
e36ded7-2f3d-43c2-881c-cbc75c80b5c2n%40googlegroups.com
> <https://groups.google.com/d/msgid/django-developers/7e36ded7-2f3d-43c2-881c-cbc75c80b5c2n%40googlegroups.com?utm_medium=email_source=footer>
> .
>
--
--
==
Daryl Egarr, Director
Kawhai Consultants Ltd
Ce
>
> In this word developers said "We 100% support BLM, we against any racism.
> Some of community members have sent proposal for renaming blacklist, but we
> 100% sure, that this term has nothing to do with racism. Moreover, terms
> can't explain things 100% clear, we just use those terms to
ho have posted on the list who *disagree* with the
changes, none have written an argument with substantial merit in my opinion.
Remember, it's all about the future users of Django, not just the current
users.
D
On Mon, 22 Jun 2020 at 08:10, Alexander Lyabah wrote:
> Daryl, that is ver
use 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+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
>
;>>>>
>>>>>>>>>>> Feedback and criticism is highly appreciated.
>>>>>>>>>>>
>>>>>>>>>>> Thanks!
>>>>>>>>>>> Kind regards
>>>>>>>>&
Hi All,
When running tests I often end up crashing things and when restarting
the tests i get the line;
Creating test database for alias 'default'...
Got an error creating the test database: (1007, "Can't create database
'test_x'; database exists")
Type 'yes' if you would like to try
simply orthogonal to this.
--
Daryl
On Wed, May 28, 2008 at 12:25 AM, koenb <[EMAIL PROTECTED]> wrote:
>
> On 22 mei, 18:28, "Ben Ford" <[EMAIL PROTECTED]> wrote:
>> Hi all,
>>
>> I've now re-applied Daryls patch (which was against qsrf) to a clon
gt; everyone who's interested.
Thanks Ben.
--
Daryl
On Wed, May 21, 2008 at 3:33 AM, Ben Ford <[EMAIL PROTECTED]> wrote:
> Hi all,
>
> I'll sort out the hg repo (it now needs to point at trunk - not qsrf) and
> trac project if I get time this evening and make it public read
Perhaps bedros meant to ask if anyone is working on support in Django
for any "document based" databases.
strokeDB looks (to my untrained eye) similar to CouchDB. You'll find
plenty to read if you do a search for "couchdb django".
--
Daryl
On Tue, May 20, 2008 at 4
.
I would still like to get my patch working so others (and myself) can
start testing it. I won't have time this week, but so far it looks
like I may be able to make some time next week. If I don't, I see if
I can at least make enough time to write up the API I came up with at
PyCon.
--
Daryl
Ah. I'm glad I brought it up.
When the time comes to port my code, I'll try skipping step 1 first.
--
Daryl
On Fri, Mar 28, 2008 at 5:48 PM, Martin v. Löwis
<[EMAIL PROTECTED]> wrote:
>
> > I think you misunderstand the role of 2.6. See the seven steps under
> &
oject to Python 2.6."
And step 6 is "If problems are found, make corrections to the 2.6
version of the source code and go back to step 3." I take this to
mean that one likely needs to make 2.6-specific changes in order to
get the code working on 3.0 after running it through 2to3.
-
ss I'm missing something, wouldn't Django likely have to include
code that would only work on 2.6 for this to work?
--
Daryl
On Fri, Mar 28, 2008 at 8:57 AM, Jacob Kaplan-Moss
<[EMAIL PROTECTED]> wrote:
>
> On Thu, Mar 27, 2008 at 5:10 PM, Martin v. Löwis
> <[EMAIL P
Jacob writes:
> It's hard enough maintaining 2.3, 2.4, and 2.5 side-by-side...
Do you maintain them side-by-side, or do you just reject patches that
require new features introduced in 2.4 and 2.5? (I just assumed that
you maintain 2.3 compatibility by testing on 2.3.)
--
Daryl
On Thu,
18 matches
Mail list logo
