Yeah, I'm a big +1 on this. I try to comment my code as much as
possible to make it possible for me to go back months later and pick
up where I left off in terms of understanding and this patch will
greatly beautify comments.
I know in the past a core dev or two resisted adding another tag
I imagine there are some people here who (like me) want to open
source some of their Django code, contrib apps, or other things but
cant run Subversion or Trac on their host. Google to the rescue, as
always:
http://code.google.com
Hopefully this can be useful to many of you.
-Tyson
--~--
On 7/27/06, Ian Holsman <[EMAIL PROTECTED]> wrote:
> I for one would like a 0.95 release.
...
Earlier today:
On 7/27/06, Adrian Holovaty <[EMAIL PROTECTED]> wrote:
...
> We're working on the .95 release as I type
> this, though.
>
> Adrian
--~--~-~--~~~---~--~~
Y
On 7/27/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
>
> When you talk all I hear is poop hitting a toilet.
...
> astablished
...
> use there nightly build it a production
> enviroment?
...
> last nights kernal build
...
> If you have ever worked on a non-kiddy project (ie $$$) you will
> unde
It'd be nice if .95 would take care of at least *some* of the bugs
that have been piling up in Trac. I understand the few who have commit
access are insanely busy, but I just can't fathom a .95 release with
the current state of trunk. (Whatever happened to the bug-fix sprint?)
It's a little dishe
On 7/26/06, monkeynut <[EMAIL PROTECTED]> wrote:
> http://code.djangoproject.com/ticket/2433
> .. hopefully I didn't miss anything, I've been out in the sun all day.
>
> Pete.
Not sure if you're the same Pete, but hopefully that patch can work
well with this one: http://code.djangoproject.com/tic
On 7/26/06, Malcolm Tredinnick <[EMAIL PROTECTED]> wrote:
> It'll get fixed one day, since it's useful functionality. Somebody can
> submit a patch or I'll write it one day (low priority). It's really just
> waiting on a patch that has reasonable API.
>
> Regards,
> Malcolm
I'm +50 on this becaus
On 7/21/06, monkeynut <[EMAIL PROTECTED]> wrote:
> OK, patch mark 2 is up.. the only problem (and it might be a biggie) is that
> this effectively breaks things for people who're using the arguments in
> their intended way (eg. getting tomorrow and yesterday, etc.)?
>
> Pete.
I think the two poss
Thanks again to James for catching the problems in my test case - it
looks like I made a number of mistakes in the translation from my
real project to the minimal test case and didn't catch them. I really
appreciate the help.
On Jul 20, 2006, at 8:41 PM, James Bennett wrote:
>> 10. Navigat
please, I'm begging, can someone, *anyone*, acknowledge these
problems, at the very least? I'm at the end of my rope with these
problems. I've spent the past two weeks trying to get the barest
acknowledgment of these problems on the lists and on IRC, but I feel
like a
On 7/18/06, Adrian Holovaty <[EMAIL PROTECTED]> wrote:
I haven't had a chance to look at this issue, but I'll point out thatthere's no way this is a "show-stopper" problem, given that, ifgeneric views don't suit you, you can just write five-or-so lines of
view code manually...AdrianBut surely bugs
thing!
Regards,
Tyson
On Jul 16, 2006, at 2:10 PM, Tyson Tate wrote:
>
> Note: I originally posted part of the following to the users list,
> but I realized today that it's probably better posted here because it
> deals with a potential bug and developer rationale behind some
> gen
us Month: {{ next_month|date:"F Y"}}
{% endif %}
{% if previous_month %}
Next Month: {{ previous_month|date:"F Y"}}
{% endif %}
---
Thanks in advance for any help/suggestions,
Tyson Tate
--
Tyson Tate
- CalPoly Graphic Design Student
- Work: Graphic Designer (CalPoly L
On Jun 30, 2006, at 5:04 AM, Russell Keith-Magee wrote:
> ...
> Reporter.objects.filter(article=a)
>
> ...
> However, since this change could effect people in the field, I
> thought I'd check for objections before I commit.
>
> Comments?
>
> Russ Magee %-)
I'm +1 on this too. I've done it many
On Jun 24, 2006, at 11:14 AM, Tyson Tate wrote:
>
> Most comment systems that I know of allow the commenter to optionally
> supply an e-mail address and/or a URL along with their comment for
> attribution or administrator records. I thought it would be really
> handy to have i
calls.
Regards,
Tyson
--
Tyson Tate
* Graphic Designer, CalPoly Library
* Assistant Librarian & Member, Mustang Band
* Team Member, CalPoly Triathlon Team
* Webmaster & Active, Kappa Kappa Psi
* Freelance Graphic Designer
--~--~-~--~~~---~--~~
You receive
ink.
Regards,
Tyson
--
Tyson Tate
* Graphic Designer, CalPoly Library
* Assistant Librarian & Member, Mustang Band
* Team Member, CalPoly Triathlon Team
* Webmaster & Active, Kappa Kappa Psi
* Freelance Graphic Designer
--~--~-~--~~~---~--~~
You received
On Jun 21, 2006, at 8:50 PM, James Bennett wrote:
> Has the world honestly learned not one single solitary thing form
> PHP's magic_quotes fiasco? Autoescaping all output by default is
> something that is unequivocally not acceptable.
Oh - I haven't heard of the magic_quotes fiasco. Do you have a
On Jun 21, 2006, at 6:57 PM, Jacob Kaplan-Moss wrote:
> Yes, I agree -- I've never been against a template tag which does
> autoescape because that's still leaving power in the hands of the
> template authors.
Then again, how often do you *want* to allow your users to put HTML
and JS in and al
On Jun 21, 2006, at 4:49 PM, Malcolm Tredinnick wrote:
> What are the use cases for this sort of construction?
> [...]
I've always thought that any decent computer tool should either a) do
what you tell it to, or b) tell you why it can't/won't do what you
want it to (warnings, exceptions, et
On Jun 21, 2006, at 3:31 PM, Jacob Kaplan-Moss wrote:
> [...]
> Another place to start solving the XSS problem is at the input level;
> a policy of "don't trust data from the web" makes a lot more sense to
> me than one of "don't trust the template author".
Modded "+5 Insightful" :) I can attest
s a signup list, which has a one-to-many
relationship with signup slots.)
I have two ideas on how this could be addressed:
1. Throw a warning or error in Syncdb, letting the user know that
every model must have at least one explicit field.
2. Build the field as the programmer defined them.
Any
22 matches
Mail list logo
