On Nov 26, 1:19 pm, Aymeric Augustin
wrote:
> On 24 nov. 2011, at 16:53, Marcob wrote:
>
> > I realize that this is a volunteer-based project, but I was wondering
> > if you have any updates regarding the wiki page for the 1.4 roadmap?
> > (https://code.djangoproject.com/wiki/Version1.4Roadmap)
>
BitBucket has full git support btw.
--
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To view this discussion on the web visit
https://groups.google.com/d/msg/django-developers/-/Ax7zncVO2FYJ.
To post to this group, send email to django-deve
My point was the social factor. I mean the GitHub community is quite
bigger. It's not big issue if we're using mercurial instead of git. Sure, I
prefer git, it's faster and stuff, but it's not a big deal, right now.
Anyway, I'm trying to get into making the tests run and if I see some
result f
2011/11/27 Mikołaj Siedlarek :
> Hi,
> I've just posted a new ticket with everything the feature proposal needs -
> motivation, idea and actual implementation.
> https://code.djangoproject.com/ticket/17301
>
> It definitely needs some discussion, so please -- ask, discuss, criticize,
> share some t
On Mon, Nov 28, 2011 at 5:05 PM, Marcob wrote:
> On Nov 26, 1:19 pm, Aymeric Augustin
> wrote:
>> On 24 nov. 2011, at 16:53, Marcob wrote:
>>
>> > I realize that this is a volunteer-based project, but I was wondering
>> > if you have any updates regarding the wiki page for the 1.4 roadmap?
>> > (
Hi Russel,
My patch obviously was not posted to be merged into trunk in it's current
state.
It is meant to be a message "i'd like to do that, seriously". Now that I
see general
community support I can perfect it. There several more things I'd like to
do, mainly:
1. "Dogfooding" (which is a
On Sat, Nov 26, 2011 at 1:33 AM, Vinay Sajip wrote:
> I'm working on a port of Django to Python 3. I'm getting close, and in
> terms of
> test coverage pretty much almost there, but a few remaining test
> failures are
> eluding me, and I could probably use some help to speed things up.
Hi Vinay,
2011/11/28 Mikołaj Siedlarek :
> Hi Russel,
> My patch obviously was not posted to be merged into trunk in it's current
> state.
> It is meant to be a message "i'd like to do that, seriously". Now that I see
> general
> community support I can perfect it. There several more things I'd like to
> do,
Hi Vinay,
Many thanks for your efforts so far, as you can imagine I have a few
questions, both procedural and technical. I should note though that
I haven't reviewed all your changes in detail yet, since they are..
massive :)
I'm a bit concerned that you didn't get in touch with us before you
sta
On Nov 28, 1:04 pm, Jannis Leidel wrote:
>
> I'm a bit concerned that you didn't get in touch with us before you
> started with the work, since tracking the changes would have been
> easier. FWIW, Martin von Löwis, Alex and me would be those you can
> ask if you need any further help, usually als
On Nov 28, 9:29 am, Kiril Vladimirov wrote:
> My point was the social factor. I mean the GitHub community is quite
> bigger. It's not big issue if we're using mercurial instead of git. Sure, I
> prefer git, it's faster and stuff, but it's not a big deal, right now.
Well, it's not as if there's a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Mikołaj,
Thanks for your work on contributing to Django!
I am a bit skeptical about defining form fieldsets in Python code, as
they have no effect on server-side interpretation or validation of form
data, they are purely an HTML/presentational iss
On 28.11.2011, at 18:08, Vinay Sajip wrote:
> On Nov 28, 1:04 pm, Jannis Leidel wrote:
>>
>> I'm a bit concerned that you didn't get in touch with us before you
>> started with the work, since tracking the changes would have been
>> easier. FWIW, Martin von Löwis, Alex and me would be those you
On Nov 28, 4:40 am, Russell Keith-Magee
wrote:
> Any practical suggestions on how we can improve on this situation will
> be gratefully accepted.
Core has grown, but it seems to me there is a fair amount of cultural
and procedural knowledge that more veteran core members have not yet
transferr
> Yeah, that implementation seems preferable. What was the reason for backing
> it out?
Not sure. What would be the procedure for getting this changed? Open a
new ticket, I assume?
--
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to
There was an old thread about this at
https://groups.google.com/group/django-developers/browse_frm/thread/6e41ee7b08d50710/9cf6375d97bed499?lnk=gst&q=update+signal#9cf6375d97bed499
which fizzled out last summer with no conclusion.
(I'd reply to that thread but google groups apparently won't let me
On Nov 28, 5:36 pm, Jannis Leidel wrote:
>
> Ah, that makes sense, in fact your approach is much closer to what I
> remember doing when pip and virtualenv was ported.
Right, since I did those ports originally :-)
> Honestly, I'm not sure how hard the merge is, as I'm not sure how much
> changed
On Nov 28, 7:14 pm, Vinay Sajip wrote:
> suite is a boon in this regard. Though having worked through the
> tests, it doesn't seem like the DRY principle is followed as much as
> it could be ... for example, the same literals being used over and
> over again in copy/paste fashion, requiring patch
On Mon, Nov 28, 2011 at 6:40 AM, Russell Keith-Magee
wrote:
> So -- what we need is for someone in the core team who is able to find
> the resources in their schedule to commit to shepherding a release.
> Speaking for myself, I know that this almost certainly isn't going to
> be me -- my work life
I assumed I needed the votes here to get going on that. In the past when
I've started with a ticket I've been directed here to gather support first.
--
Steven
On Mon, Nov 28, 2011 at 11:59 AM, Jamie Matthews
wrote:
> > Yeah, that implementation seems preferable. What was the reason for
> backing
On 28 nov. 2011, at 21:33, Adrian Holovaty wrote:
> And that someone will be me. See my post here:
> http://www.holovaty.com/writing/back-to-django/
Awesome!
> Is there a list somewhere of what needs to get done?
> If not, I can make it, but obviously it'd be great if that already existed.
I d
On Nov 28, 9:33 pm, Adrian Holovaty wrote:
> On Mon, Nov 28, 2011 at 6:40 AM, Russell Keith-Magee
>
> wrote:
> > So -- what we need is for someone in the core team who is able to find
> > the resources in their schedule to commit to shepherding a release.
> > Speaking for myself, I know that this
22 matches
Mail list logo
