On 1/17/07 5:05 PM, Robert Myers wrote:
> Only one tiny remark, the closed tickets use to show up with a
> strike-through, possibly a missing css param?
Indeed - thanks, and fixed.
Jacob
--~--~-~--~~~---~--~~
You received this message because you are subscribed t
On 1/17/07 5:24 PM, Honza Král wrote:
> I am really looking forward to listing through "patch needs
> improvement" and "has_patch" == no
> whenever I have the time and feel like some coding... ;)
Check out:
http://code.djangoproject.com/wiki/Reports#Ticketsneedingsomework
That should help anyon
On 1/17/07 7:45 PM, telenieko wrote:
Hi, what happened to "Milestones" ? I know there's the "Version" field, but
it only includes already released versions and SVN, I can no longer mark a
bug "blocker of 1.0" (which could be achieved with milestone=1.0 and
priority=blocker) how can "Must be solv
On 1/17/07 8:24 PM, Jorge Gajon wrote:
However, the timeline rss feed seems to be broken now.
Weird - I'll try to track that down.
In the meantime, you could subscribe to django-updates
(http://groups-beta.google.com/group/django-updates); it's essentially the
same data.
Jacob
--~--~
On 1/18/07 7:17 AM, Michael Radziej wrote:
somehow the reopen button went on vacation with the trac udate--can
anyone call it back? It would be very appreciated by ticket #3320 ;-)
(At least, I cannot reopen from closed/invalid)
Very interesting - it looks like that action is being hidden fr
On 1/18/07 8:08 AM, Ramiro Morales wrote:
It's me or the "type" field (defect, enhancement, ...) of a ticket is
also missing?.
We got rid of that field, along with a couple of other fields we don't really
use. In this specific case, besides not using it, the line between "defect"
and "enhan
On 1/18/07 8:15 AM, Jeremy Dunck wrote:
Perhaps the triagers should also get a non-committing apache auth to
boost their no-spam karma?
I've got enabling registration (logged-in users don't get spam filtered) on
the todo list, but it's a little complicated (I've got it using Django's auth,
w
On 1/18/07 4:24 PM, Michael Radziej wrote:
The basic idea is (and this is *my* interpretation), we have enough
tickets. We probably have more tickets than we can process, even with
triaging. There's no use in keeping tickets when the reporter has lost
the interest in helping with it. (Of course
On 1/18/07 8:12 PM, [EMAIL PROTECTED] wrote:
I'm trying to add an attachment to a ticket:
http://code.djangoproject.com/attachment/ticket/3099?action=new
I'm getting the following error:
Yeah, I'm getting that too. I'll try to fix it if I can figure out what's up.
Jacob
--~--~-~--~
On 1/19/07 1:01 PM, SmileyChris wrote:
Done, but can't submit it.
You mean you can't upload attachments? I just tried a few different times and
it seems to work for me... what's the error you're getting?
Jacob
--~--~-~--~~~---~--~~
You received this message
Howdy folks --
Please join me in welcoming James Bennett as Django's release manager!
James is going to be taking over the job of pushing out official releases.
This makes a lot of sense as he's been maintaining the -bugfixes branches already.
Along with that, we'll be putting out two releas
On 1/23/07 9:58 PM, Adrian Holovaty wrote:
> On 1/23/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
>> may I suggest to set properties for the files in svn ?
>>
>> {{{
>> for filename in `find . -type f`; do
>> svn propset svn:keyword "URL Author Date Rev Id" $filename
>> done;
>> }}}
>
> Par
On 1/23/07 9:16 PM, Nate Straz wrote:
> Why does the admin app tie directly to models? Why not applications?
Because sometimes you want certain models within in app *not* to be
admin-editable.
Jacob
--~--~-~--~~~---~--~~
You received this message because you ar
On 1/28/07 8:18 AM, Andrew Durdin wrote:
> * The 'decimal' module from 2.4 is included under django.utils, to
> ensure Python 2.3 compatibility
In order for this to be accepted, we need to know:
* What is the license for the decimal module, and is said license compatible
with the BSD license
On 1/29/07 7:22 AM, Russell Keith-Magee wrote:
> I've just created two new tickets - #3389 and #3390.
I'm +1 on #3390 (the ``DEFERRABLE INITIALLY DEFERRED`` bit); that makes a few
other bulk-insert type tasks besides deserialization much easier.
#3389 seems logical enough, but I'm a bit wary of
On 1/29/07 10:15 AM, Robert Myers wrote:
> I'm seeing the same amount of errors on python 2.3.4, it appears the @
> decorator syntax is being used in the modeltests/test-client/views.py. This
> was introduced in python 2.4, I changed it to the old decorator syntax 'blah
> = decorator(blah)' and st
On 1/28/07 8:42 PM, [EMAIL PROTECTED] wrote:
> i just wanted to spark some discussion of #3369. i implemented it and
> would like to see it get included.
>
> here's an example of what reverse caching of foreign keys would mean:
>
> b = Blog.objects.get(id=1)
> for entry in b.entry_set.
On 2/5/07 10:39 PM, James Bennett wrote:
> http://code.djangoproject.com/ticket/3439 -- Improving the
> dispatcher's performance (why *are* we still using such an old version
> of PyDispatcher? Did it just get forgotten deep down in the code?)
I'm not entirely sure, actually...
I'd prefer to tra
On 2/3/07 7:04 PM, Russell Keith-Magee wrote:
> Has anyone else noticed that since the changes to Trac were rolled
> out, Subversion checkin messages don't seem to be firing the Trac
> triggers?
Sorry -- missed it in the trac upgrade. Should be fixed now (hence the spammy
commit in [4462]).
Jac
Howdy folks --
SSIA; sorry about the bug!
Jacob
--~--~-~--~~~---~--~~
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 unsubscribe from
Hey Jannis --
Thanks for the patch, it looks pretty good. I've got a few bits of
feedback before it can be checked in, however:
* I don't much like the model living in
django.template.loaders.database; that seems like the wrong place for
it. I'd love to see you move the code into django.contrib
On 2/24/07, Jannis Leidel <[EMAIL PROTECTED]> wrote:
> * Moved the models.py to a new contrib app
> "django.contrib.dbtemplates". "dbtemplates" to prevent confusion with
> "templates" directories.
>
> * Moved the "load_template_source" function to the new file django/
> template/loaders/database.p
Howdy folks --
After a wonderful Django meetup here at PyCon (Django: the framework
that buys you pizza), a bunch of us spun off into a little ad-hoc
sprint to talk about improvements to the Django admin.
This email summarizes our plan. It's quite long, mostly because it's
an attempt to distill
On 2/25/07, Jannis Leidel <[EMAIL PROTECTED]> wrote:
> I now moved everything to the django.contrib.dbtemplates app and
> added a utility which syncs all filesystem based templates in
> TEMPLATES_DIRS to the database. The docs are now in dbtemplates.txt.
Awesome :)
> Could someone please explain
On 2/25/07, Michael Radziej <[EMAIL PROTECTED]> wrote:
> One thing comes to my mind, supporting non-ASCII characters in newforms:
Since newforms will still be "new" in 0.96, I'm could take or leave
these before it. I'll try to get to 'em, though.
> http://code.djangoproject.com/wiki/FeatureGrou
On 2/25/07, Brian Harring <[EMAIL PROTECTED]> wrote:
> http://code.djangoproject.com/ticket/3440 , Models.__init__
> refactoring.
#3440 is fixed and has to do with DateQuerySet; did you mean #3438?
Jacob
--~--~-~--~~~---~--~~
You received this message because you
On 2/25/07, Rubic <[EMAIL PROTECTED]> wrote:
> In keeping with the overall theme of testing at this
> year's PyCon, it would be nice to have integrated
> testing (fixtures, ticket #2333) brought to resolution.
I really, really, *really* agree, and I'm going to look at seeing if I
can channel Russ
On 2/26/07, Russell Keith-Magee <[EMAIL PROTECTED]> wrote:
> AFAIK, it is finished, just waiting for Adrian's ok. Is there
> something missing that I'm not aware of?
Oh, I thought there was something missing *I* wasn't aware of :)
Please go ahead and check it in! I'll focus on writing docs (and
On 2/26/07, Tixx <[EMAIL PROTECTED]> wrote:
> I'm looking for a Django developer who help us with the development of
> a feed aggregator based on Django and Universal Feed Parser.
Hi Tixx --
In the future, can you please direct questions of this nature to
django-users? That list is for general d
On 2/26/07, Jeroen van Dongen <[EMAIL PROTECTED]> wrote:
> There are more tickets like this, I also suspect that there are
> tickets which are unreviewed and open, yet quietly solved or otherwise
> no longer relevant as part of the ongoing improvements and changes
> made to Django.
>
> However, th
On 2/26/07, simonbun <[EMAIL PROTECTED]> wrote:
> Now for the inevitable question and probably irritating ;) question:
> when are these changes scheduled to be included in the django tin?
I'm guessing sometime between "tomorrow" and "when Perl 6 ships".
With any luck it'll be closer to the forme
On 2/26/07, Rob Hudson <[EMAIL PROTECTED]> wrote:
> Could we get a design decision on whether to add default, non-django
> looking 404 and 500 templates?
I've close #760 and #3335 with this comment:
"""
Django's not going to ever include a default 404 or 500 template. If
we do, people won't be
On 2/26/07, herbert <[EMAIL PROTECTED]> wrote:
> i've created a ticket (http://code.djangoproject.com/ticket/3538)
> which requests to add a function which returns the current basename of
> an uploaded file to FileFields (ie. only the bare filename, without
> any path information) .. since it was
On 2/27/07, Seattle Daniel <[EMAIL PROTECTED]> wrote:
> As I read it, there is not a way to force InnoDB to check constraints
> at commit. And once there is it will be quite some time before the
> mass of MySQL instances support it.
So... I think that leaves is with two kinda sucky choices:
1. R
On 2/27/07, Alexander Solovyov <[EMAIL PROTECTED]> wrote:
> So I have question - what needs to happen for merging this branch into
> trunk? I read page on wiki (MultipleDatabaseSupport) and examined that
> all features are completed but the docs absent in all. So writing docs
> will cause to mergi
Hey Arvind --
This question is really more appropriate for django-users
(http://groups.google.com/group/django-users/); django-dev is for
discussion of developing Django, not for discussion of using Django.
You'll have a lot more luck if you redirect your question to
django-users.
Thanks!
Jacob
On 2/27/07, Russell Keith-Magee <[EMAIL PROTECTED]> wrote:
[on reverting [4610]]:
> I'm -1 on this. Serialization and fixtures are near useless if you
> can't do forward references. [4610] introduces a test for forward
> references, and fixes a problem with Postgres. [4610] doesn't
> introduce an
On 3/1/07, mralokkp <[EMAIL PROTECTED]> wrote:
> I guess This Group could help me.
No, actually you were right to post the question to django-users.
This list is for discussion of developing Django itself, not questions
about using it.
Thanks!
Jacob
--~--~-~--~~~---
On 3/1/07, Tom <[EMAIL PROTECTED]> wrote:
> Hi it seemed to be a good change to give the admin its own space. Btw
> what about the field specific items like
>
> edit_inline, max_num_in_admin, ...
>
> an so on. Have you made any decision where this should be set in
> future or if this will be left
On 3/5/07, Jeroen van Dongen <[EMAIL PROTECTED]> wrote:
> And that's where I got confused: the contribution page does not say a
> single word about who the triaging crew is, how you can become a
> member of it etc.
Agreed that we need to be more clear about who these people are.
Anyone want to cr
On 3/7/07, Rob Hudson <[EMAIL PROTECTED]> wrote:
> So somewhere else in the ORM it fixes the quoting before it hands it
> over to the database?
Yup, that's correct -- it's actually part of the db-api spec
(http://www.python.org/dev/peps/pep-0249/)
--
Jacob Kaplan-
On 3/13/07, Ivan Sagalaev <[EMAIL PROTECTED]> wrote:
> I was lazily thinking about making {% url %} and "reverse" to work for
> generic views ("GV").
I've been thinking about this a bunch myself. I came up with some
ideas similar to yours, but so far they're just in my head. I'll try
to write 'em
On 3/10/07, Malcolm Tredinnick <[EMAIL PROTECTED]> wrote:
> However, the more I think about this the more I think we should be
> throwing an error if they are using an older version, particularly in
> the new (0.96) release. If you are using the older version you will see
> bugs. There is no quest
On 3/12/07, Gary Wilson <[EMAIL PROTECTED]> wrote:
> I asked Jacob to take a quick look at this ticket during the PyCon
> sprint. His comments were (1) the send method on EmailMessage is
> kinda neat and (2) we would need to keep send_mail() and
> send_mass_mail() functions around for backwards c
Howdy folks --
We still need developers to be mentors for the Summer of Code. This
essentially means helping a student as s/he implements some cool new
feature, and making sure that s/he completes things on time.
If you've been around here for a bit and want to *really* help us out,
please sign
How folks --
Just a quick reminder that Google Summer of Code student applications
are due Monday! If you're a student and want to get paid to work on
Django this summer, you should submit an application ASAP.
We've only gotten a couple of good applications, so if you've got
something interestin
On 3/26/07, Simon G. <[EMAIL PROTECTED]> wrote:
> So - if we do want a BinaryField we could use #2417 and make it
> suitable for larger binary stores (e.g. the VARBINARY used for MySQL
> has a max length of 255 bytes - perfect for the small bin. chunks
> wanted in #2417, but not for larger data),
On 3/26/07, Malcolm Tredinnick <[EMAIL PROTECTED]> wrote:
> However, on a related
> topic, it's easy when writing things like object.person.count to create
> repetitive queries (there's no reuse of that queryset if you type the
> same thing later). So I was thinking in idle moments today about how
On 3/25/07, Malcolm Tredinnick <[EMAIL PROTECTED]> wrote:
> As James mentioned (indirectly), it's all under django/docs.txt -- we
> basically just run rst2html.py over the results before it is displayed
> on the website.
[Actually, it's a bit cooler now: the doc views now pull the reST
source dir
On 3/26/07, SmileyChris <[EMAIL PROTECTED]> wrote:
> Sure: http://code.djangoproject.com/ticket/3826
Sweet; thanks.
I'm gonna wait a couple of days for any objections from Malcom/Adrian,
but unless I hear any I'll add this shortly.
Jacob
--~--~-~--~~~---~--~~
Yo
Hi Mario --
On 3/27/07, Mario Gonzalez <[EMAIL PROTECTED]> wrote:
> Hello, I'm trying to know the callback name after a resolve process
[snip]
Please direct questions of this nature to django-users; django-dev is
used to discuss the development of Django itself, not to answer usage
questions.
On 3/27/07, mario__ <[EMAIL PROTECTED]> wrote:
> well, I think this is Django development question. I need it because
> I'm the author of the thread called: "Authentication issue (Proposal)"
> and to know how resolve() works will be great. It could help me a lot.
I really don't want to be the "b
On 3/27/07, Jannis Leidel <[EMAIL PROTECTED]> wrote:
> I just uploaded a patch [1] to add nightly functionality as discussed
> in ticket #1327 [2] to the django_website application which you may
> find useful.
Nifty nifty :)
I'll work on adding it to the site -- thanks!
Jacob
--~--~-~-
> I don't like newlines within tags purely for aesthetic reasons. A tag
> is a bite-sized, atomic unit. If it's spread over multiple lines, it
> turns into some strange mushy, ugly thing.
>
> Yes, this is highly subjective. I realize that, and I shudder at the
> thought of a 30-message mailing-lis
Hi xav --
Please direct questions of this nature to django-users; django-dev is
used to discuss the development of Django itself, not to answer usage
questions.
Thanks!
Jacob
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Googl
On 3/30/07, Gulopine <[EMAIL PROTECTED]> wrote:
> On the flipside, this certainly qualifies as "non-trivial", so does it
> need thorough discussion on this list before submitting a ticket? I'm
> not sure on this one, since it doesn't modify any existing Django
> code. I plan on bringing it up here
On 3/30/07, Gulopine <[EMAIL PROTECTED]> wrote:
> So once it's ready, would I create a ticket to make that proposal, or
> just suggest it here?
Here, probably. The ticket system is good for relatively
uncontroversial changes, but new contrib apps might be controversial,
so it's best to put it her
Hey Russ --
I'm +0 on spaceless actually being spaceless; -0 on keeping a single
space as an option, -1 on one space being default or allowing an
arbitrary number of spaces.
Jacob
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the G
On 4/1/07, SmileyChris <[EMAIL PROTECTED]> wrote:
> I'm not sure if there's a ticket for this, but I remember talk about
> it being an unnecessary wart which was going to be removed eventually.
> Is it in the 1.0 plan?
Oh, please, yes!
I'd be inclined just to remove 'em wholesale and let things
On 4/1/07, Russell Keith-Magee <[EMAIL PROTECTED]> wrote:
> What about LazyDate? It seems to me that given
> "default=datetime.datetime.now" is legal, LazyDate can be deprecated
> as well.
Yeah, I'd like to get rid of LazyDate, too.
Jacob
--~--~-~--~~~---~--~~
Yo
On 4/2/07, Wolfram Kriesing <[EMAIL PROTECTED]> wrote:
> 1) How can I help getting this functionality into trunk? (enhance the
> patch, write doc, ...)
> 2) Is this something that would be accepted to go into the trunk at all?
When I worked on this, the "fields" bits from the patch didn't seem to
On 4/1/07, James Bennett <[EMAIL PROTECTED]> wrote:
> Anyone have strong opinions against this before I whip up a patch?
+1 on adding "headers", -1 on adding (for the same reason we
leave out).
Jacob
--~--~-~--~~~---~--~~
You received this message because you a
On 4/3/07, Nowell Strite <[EMAIL PROTECTED]> wrote:
> Django currently supoorts COOKIE prefixes, as well as a
> CACHE_MIDDLEWARE_KEY_PREFIX, but I would find it immensely useful to
> have a prefix for all cache key entries (i.e. site's sharing a common
> caching mechanism, with overlapping keys th
> seems like it should be as easy as a function in contrib somewhere:
[snip]
Another option is a trivial field subclass::
class AutoDateTimeField(models.DateTimeField):
def pre_save(self, model_instance, add):
return datetime.datetime.now()
Jacob
--~--~-~--~
On 4/8/07, Simon G. <[EMAIL PROTECTED]> wrote:
> I believe that the plan for 1.1 is to rewrite Django in Lisp or
> Haskell. Or is Scheme the cool one now?
Erlang!
Jacob
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Group
Hi Ryan --
Please direct questions of this nature to django-users; django-dev is
used to discuss the development of Django itself, not to answer usage
questions.
To try to answer your question, though: have you tried phrasing your
queries in less than/greater than form (i.e. filter(lat__gt=-3,
l
On 4/10/07, Todd O'Bryan <[EMAIL PROTECTED]> wrote:
> Given that logic (which, as I said, may or may not be a correct
> recollection), I vote for Jacob's solution. In fact, it might be cleaner
> to have CreationTimestamp and ModifiedTimestamp fields (both subclasses
> of DateTimeField) so that it'
On 4/12/07, sime <[EMAIL PROTECTED]> wrote:
> I'm looking for a talented local programmer to help with a growing
> workload, on a regular contract basis. All projects in django :-)
In the future, please direct job ads to django-users. Django-dev is
used to discuss the development of Django itself
On 4/16/07, Brian Morton <[EMAIL PROTECTED]> wrote:
> For "T", the docs say that it will output the "Time zone of this machine".
> To me, this implies that it will read from tzdata. However, this actually
> outputs the time zone specified in the project settings file, which I think
> is the inten
Hey Michel --
Please direct questions of this nature to django-users; django-dev is
used to discuss the development of Django itself, not to answer usage
questions.
Thanks!
Jacob
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the G
On 4/18/07, Daniel Brandt <[EMAIL PROTECTED]> wrote:
> Something has been bugging me for a while..
This type of complaint seems to come up every few months. I'm always tempted to
ignore it because I have a hard time responding in a way that doesn't end up
making me sound like a dick; usually that
On 4/18/07, Jonathan Daugherty <[EMAIL PROTECTED]> wrote:
> Do you have a resident buildbot? That could be used to run the
> regression tests on (all pythons) x (all databases). It would still
> take time, of course, but it could at least be automated[1][2].
I've spent some time in the past try
On 4/18/07, Matthew Flanagan <[EMAIL PROTECTED]> wrote:
> The script [1] I'm using for the Django pybots [2] is very simple. The
> only thing I'd like to get going is testing against different
> backends. Do you have a problem with running it on pybots, except for
> the fact it isn't testing again
On 4/18/07, Brian Harring <[EMAIL PROTECTED]> wrote:
> What exactly was the issue you were having? Ofhand, a ShellCommand
> with haltOnFailure=True ought to suffice- last I looked, y'alls test
> runner properly set the exit code if a failure was detected, thus you
> should be able to rely on that
On 4/18/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> Would you consider adding a thumbnail capability to Django? I know
> there are contributions out there that do it and the dependency on PIL
> might be a negative but I believe this is a very common use case. How
> many apps have an image
On 4/19/07, Matt Boersma <[EMAIL PROTECTED]> wrote:
> The "boulder-oracle-sprint" branch is ready to come home.
Wahoo!!
Just to clarify, Matt: you're willing to commit to maintaining Oracle
support once we merge this into trunk, yes? If so, I'm +1 on merging
this in (there's a few things we had
On 4/20/07, Malcolm Tredinnick <[EMAIL PROTECTED]> wrote:
> At the risk of asking you not to have a life, could one of you give some
> attention to the various tickets in the Website component whenever you
> next have a chance to sit down and work on some bugs. There are a number
> of documentatio
On 4/23/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> Why isn't patch #2070 added to trunk yet? The current patch(es) won't
> work with trunk either.
You just answered your own question.
Also, please read this:
http://groups.google.com/group/django-developers/msg/f0149a288b776006
Jacob
--
On 4/23/07, Joseph Perla <[EMAIL PROTECTED]> wrote:
> Ping: simple, ready ticket #3182 is at 4 months and counting:
> http://code.djangoproject.com/ticket/3182 . Thank you,
Please don't do this. It's frustrating, annoying, and very impolite.
Please remember that everyone who works on Django doe
On 5/17/07, dtlaura <[EMAIL PROTECTED]> wrote:
> We have a great opportunity for python/django developers. Please check
> out our job posting and apply online if you are interested.
Hey --
Thanks for the job posting -- hope you find a good person! -- but in
the future please limit these types of
> In my opinion it really deserves a spot in the default contrib apps.
Mine as well.
The only thing holding me back from full support is the name; "values"
doesn't explain enough about what the app does to me. Yes, it's
bike-shedding, but Django's always had a nice color scheme. That is,
names
On 5/15/07, jedie <[EMAIL PROTECTED]> wrote:
> Whats about INTERNAL_IPS [1] ?
I think you need to let this one go. Malcom's already given a -1 and
no other developers stepped up with even a +0.
I'd love to see you develop this as an add-on -- a piece of exception
middleware, probably -- but I do
On 5/13/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> - Right now, it looks like I'll end up creating a thumbnails directory
> in /django/tests/regressiontests. Is this the right locattion?
The general rule of thumb is: if you're testing a feature of the ORM
-- a field, a database method, a
On 5/18/07, Malcolm Tredinnick <[EMAIL PROTECTED]> wrote:
> I don't really care one way or the other. I haven't intuited what makes
> something appropriate for contrib or not.
Yeah, I think I might do well to try to write that up (in the
contributing document, eventually). I think I have a feelin
On 5/18/07, Marty Alchin <[EMAIL PROTECTED]> wrote:
> I would definitely recommend that process to anyone else looking to
> write a contrib app for Django, as it makes it much easier for the
> eventual audience to try it out in real-world projects. I got
> suggestions and requests for things I nev
On 5/10/07, Simon Willison <[EMAIL PROTECTED]> wrote:
> I propose the following changes:
I'm +1 on these changes, including using "!" as the "look somewhere
else for the password" designator.
Jacob
--~--~-~--~~~---~--~~
You received this message because you are s
On 5/18/07, Malcolm Tredinnick <[EMAIL PROTECTED]> wrote:
> Don't forget that responses like this are partly written for the archive
> so that we can optimistically assume that the next person to walk this
> path will have either read the archives
Ha!
(Sorry, couldn't resist :)
Jacob
--~--~---
Howdy, all --
Django's been out as an unofficial pre-release for almost a month
now, and it's about time to wrap things up to roll a 1.0 release.
We've decided that Django, like Python itself, should put a very high
priority on backwards compatibility, so now's the time to make any
large
Howdy --
Since there's been so much great info coming on from the community,
I've opened up the wiki at http://code.djangoproject.com/. I would
*really* appreciate it if anyone who's written something interesting
about Django would move it onto the wiki.
Also, this means we need some "g
On Aug 2, 2005, at 12:26 PM, Jeremy Dunck wrote:
Since it's a Trac wiki, it may not be a prime target for spammers
(yet), but gardening would go easier if registration (or some other
speed bump) was required.
If it becomes a problem, I'll set that up (remind me to write a post
about how I in
On Aug 2, 2005, at 6:55 PM, Krzysztof Drozd wrote:
#1 && #41 && #65should be a part of milestone 1.0
On Aug 2, 2005, at 6:41 PM, [EMAIL PROTECTED] wrote:
I just think that #12 should be a part of milestone 1.0
I've added #1 and #65 to version 1.0. I'm not sure about #12 and
#41; they bot
On Aug 10, 2005, at 10:41 AM, Martin Maney wrote:
On Tue, Aug 09, 2005 at 06:04:36PM -0500, Jeremy Dunck wrote:
db.BeginTransaction()
...lots of domain code (maybe a graph) doing various stuff,
including saves
db.CommitTransaction();
On second thought, +1 for something more like this. Sinc
On Aug 11, 2005, at 3:57 PM, Jason Huggins wrote:
At the ChiPy presentation of Django in July month I remember
seeing
something I don't see any documentation for:
In the Admin interface, if a drop down list of choices had too many
entries, you provided a "search icon" to the right of the
On Aug 12, 2005, at 2:03 AM, PythonistL wrote:
Is there available complete syntax of classes/functions for Django?
I'm not exactly sure what you're looking for, but all the
documentation we have is at http://www.djangoproject.com/documentation/.
Or, you can read the source :)
Jacob
Howdy everyone --
I think I was the driving force behind rejecting this ticket --
Adrian's still 50/50 as far as I know -- so let me explain why I
don't like it.
Actually, before I do, I should say that in the end it's really
Adrian's decision in that I'll defer to his judgement should h
On Aug 18, 2005, at 11:36 AM, Martin Maney wrote:
I agree entirely, and I'm saddened to see so much time and effort
being
devoted to such unimportant trim when Django still has some serious
core limitations... granted, they're ones that seem not to affect most
CMS systems, but they make it qui
On Aug 19, 2005, at 12:40 PM, Martin Maney wrote:
The specific problems I
recall offhand were transactions (which are being worked on, or maybe
have been finished by now) and multi-column keys, which no one seemed
to be interested in at all. Maybe the problem is that I don't try to
beat the dru
On Sep 7, 2005, at 12:34 PM, Brant Harris wrote:
core.template.Context
What's the reason for this class? I can't see any point to it other
than as a dictionary wrapper.
It seems better to do:
t.render("answer": 42)
Rather then:
c = Context({"answer": 42)
t.render(c)
It's becaus
On Sep 14, 2005, at 9:25 AM, John Madson wrote:
There's been almost no discussion of Django's approach to security,
either on this list, the users list, Trac, or in the documentation.
Web application security is under heavy scrutiny these days and
there's
nary a frameout out there that's taki
On Sep 15, 2005, at 1:01 AM, Eugene Lazutkin wrote:
Today I submitted new patch, which introduces three new cache
backends:
'locmem:', 'file:', 'sql:'. If you are interested, please test it,
and give
me your feedback. See http://code.djangoproject.com/ticket/515 for
details
and required fi
301 - 400 of 1372 matches
Mail list logo
