#9589 http://code.djangoproject.com/ticket/9589 was closed for a
reason that didn't make any sense--it looks like someone closed the
ticket after reading only the first comment. The later patches fixed
those problems. I asked about this in the ticket, but didn't get a
response.
--
Glenn Maynar
Djangonauts,
To help speed along development on Django, I'd like us to start
holding regularly-scheduled sprints. I've previously contacted core
committers to see who would be willing to supply the commit bits for
the sprint workflow. I'm now looking for members of the dev list to
help organiz
On Tue, Nov 10, 2009 at 11:00 AM, Jeremy Dunck wrote:
>
> Djangonauts,
> To help speed along development on Django, I'd like us to start
> holding regularly-scheduled sprints. I've previously contacted core
> committers to see who would be willing to supply the commit bits for
> the sprint work
On Tue, Nov 10, 2009 at 11:14 AM, Sean Brant wrote:
>
> Alex, I can help you out in Chicago if you need it.
>
> Sean
>
> >
>
Sure that'd be great, I guess we don't really need to start planning
until it gets a little closer, but if we want to have any discussions
about the local things let's try
On Tue, Nov 10, 2009 at 10:04 AM, Alex Gaynor wrote:
...
> From December 19th through January 24th I will be willing to do
> anything necessary to organize a sprint in Chicago, hopefully it won't
> be too hard to drag our local core devs there :). Let me know what
> the sprint date would be over
Alex, I can help you out in Chicago if you need it.
Sean
--~--~-~--~~~---~--~~
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 unsubscr
> Sure that'd be great, I guess we don't really need to start planning
> until it gets a little closer, but if we want to have any discussions
> about the local things let's try to revive the django-chicago mailing
> list :)
>
> Alex
Yeah, I agree. If you need admin access to that list I think To
I haven't had a chance to look at the patch yet, but what you describe
here sounds good. I don't have any problem with you "hijacking" the work.
Did your patch deal at all with the unit tests in my patch that
intentionally failed to expose things that weren't working right yet?
Mike
Johannes
I would be up for getting one together in Lawrence. Our offices at LJ World
have always been a good place in the past, and I'm sure we can use them
again.
--
Eric Holscher
Web Developer at The World Company in Lawrence, Ks
http://ericholscher.com
--~--~-~--~~~---~--
I'd be willing to help organize one in the Triangle area of North
Carolina (Raleigh, Durham, Chapel Hill). We're just getting a Django
Users Group setup (TriDjUG) and there is already a thriving Python
Users Group (TriZPUG) in the area. I'm sure we could get a decent turn
out.
Thanks for kicking
Great news! Have you discussed the workflow yet?
I.e. will a DVCS be involved, and if yes, will there be
a central repo for coordinating the effort?
A special repo on Github would otherwise be perfect,
but as mentioned before, we have a problem with re-forking:
http://support.github.com/discussio
Am 10.11.2009 um 17:22 schrieb Michael Glassford:
>
> I haven't had a chance to look at the patch yet, but what you describe
> here sounds good. I don't have any problem with you "hijacking" the
> work.
>
> Did your patch deal at all with the unit tests in my patch that
> intentionally failed
This is still a little ways out, but Mahalo.com will be hosting a sprint in
the next round in February in Santa Monica, CA. We're still looking for core
developers in the area, so if you know any or are one, let me know.
-Jeff
On Tue, Nov 10, 2009 at 9:06 AM, mrts wrote:
>
> Great news! Have yo
Esteemed django developers,
I'm a coordinator for the Python track at ConFoo.ca, a major Web
development conference in Montréal, featuring a very large array of Web
related subjects including PHP, Python, Ruby, standards, security,
scaling, and system administration.
There are only a few days le
I haven't seen any notes on the subject, so I pose the question:
Would there be warm reception for a new built-in filter called "in",
to provide the template system with the Pythonic keyword? A full-blow
`{% if a in B %}` syntax would be great, but either one works. The
template language so int
Stop me if you have heard this one before. Anyone else find it
annoying that direct_to_template takes the kwarg "template" and most
other generic views take "template_name". Smells a little like php to
me.
Is this something that should be / can be fixed?
Sean
--~--~-~--~~---
Ah, so it is. Thank you. Somehow I overlooked that one.
Any commentary on the filter implementation? My use case above, for `
{% firstof ... %}` was a little dodgy. A better use case would be
using the filter with the "with" tag. I've thought however that
altering "with" to also accept the "
On Tue, Nov 10, 2009 at 3:54 PM, Tim wrote:
>
> I haven't seen any notes on the subject, so I pose the question:
>
> Would there be warm reception for a new built-in filter called "in",
> to provide the template system with the Pythonic keyword? A full-blow
> `{% if a in B %}` syntax would be gr
On Wed, Nov 11, 2009 at 5:06 AM, Sean Brant wrote:
>
> Stop me if you have heard this one before. Anyone else find it
> annoying that direct_to_template takes the kwarg "template" and most
> other generic views take "template_name". Smells a little like php to
> me.
>
> Is this something that sho
19 matches
Mail list logo
