Re: #6735 -- Class based generic views: call for comment

Jacob Kaplan-Moss a écrit : On Tue, Oct 5, 2010 at 8:03 AM, Russell Keith-Magee wrote: * Are there any outstanding tickets on generic views that will be closed by merging this branch, and do they ask for any features that aren't fixed by this branch? Almost

Re: #6735 -- Class based generic views: call for comment

this happen: * Documentation. It looks like David Larlet has made a start on this already, but there's lots more required. Yes, only a start but I'm working on it, any help is really appreciated. * Conversion of the github project into a patch on trunk. Do you see that as a total replacement

Re: Proposal: Revised form rendering

Hi, Le 11 juil. 2010 à 17:36, Russell Keith-Magee a écrit : > I'd like to propose a few extensions to Django's form library for 1.3. First of all, thanks or your proposal, the current form rendering is the worst part of Django to me and I'd like to help to improve that in 1.3. > Layout > --

Re: Class based generic views in 1.3?

Le 28 mai 2010 à 00:01, Luke Plant a écrit : > On Thursday 27 May 2010 17:29:28 David Larlet wrote: >> Hello, >> >> We're working on this with Ben during djangocon.eu sprint [1]. Any >> comment appreciated, still a work in progress though. > > Looks cool. I th

Re: Class based generic views in 1.3?

Hello, We're working on this with Ben during djangocon.eu sprint [1]. Any comment appreciated, still a work in progress though. Regards, David [1] http://github.com/bfirsh/django-class-based-views -- You received this message because you are subscribed to the Google Groups "Django

Re: [Proposal] Adding optional SITE_DOMAIN and SITE_NAME variables in settings.py

Le 14 mars 2010 à 12:27, James Bennett a écrit : > On Fri, Mar 12, 2010 at 4:39 PM, aditya wrote: > >> Currently, Django uses "example.com" for both the domain and the >> name. The only way to change that is to wade into the actual >> database. > 2. If it turns out

Re: shortcut proposal

Le 16 oct. 2009 à 23:15, Sean Brant a écrit : > Using a decorator allows you to do cool things like > > @provides_html('myapp/mypage.html') > @provides_json(optional_serialize_callback_can_go_here) > def my_view(request): >return {'foo': 'bar') > > Then your provides_* could check the

Re: Offering sponsorship to work on improving Django

Le 20 juil. 09 à 22:46, Alex Dedul a écrit : > I want to offer sponsorship if anyone would like to work on improving > Django. We can organize it in the way GSOC do this - i.e. you specify > subproject on Django you want to do, some community decision made > about usefulness about this

Re: "Delete selected objects" in admin batch edit

Le 24 mars 09 à 09:36, Elliott a écrit : > Given these reasons it only makes sense to me to leave delete off by > default and provide an easy way to enable it, both globally or for > each model. I agree with Elliott, admin actions are great and we were all impatients to see it in action - no

Re: MarkupField

Le 23 févr. 09 à 23:27, James Turk a écrit : > To me there are a few big problems with the markup_func proposal as > I see it: > > * it removes the ability to provide multiple markup_types on a given > field > * what is unpythonic about taking in two extra parameters to > customize the

Re: When Django will run on python3k?

Le 19 févr. 09 à 09:58, martin.xu a écrit : > > I like python 3k.,but I cannot run Django on python 3k? > > Is there any pacth that port Django to Python 3.0? First result in google: http://wiki.python.org/moin/PortingDjangoTo3k Regards, David

Re: App Engine port

Le 10 févr. 09 à 17:53, Alex Gaynor a écrit : > David, I think I mentioned this to you, but I believe that by using > the new F() objects we can actually remove the raw SQL entirely, I'd > need to put some more thought into this(and perhaps Malcolm already > has) but it should be possible.

Re: App Engine port

Le 10 févr. 09 à 05:25, Malcolm Tredinnick a écrit : > There's also > simple enough stuff like removing the last vestiges of raw SQL from a > couple of places (most notable related fields, but that should > probably > go after, or in tandem with, a rewrite of related fields to clean them > up

Custom date formats and admin

Hello, Today I tried to handle custom dates formats in admin and there are a couple of issues related to that. First on rendering, AdminDateWidget doesn't inherit from DateTimeInput which seems more logic to me. I eventually update the patch #7656 and it works. Is there any reason against

Re: Feedback from django-roa module

Le 19 janv. 09 à 18:43, David Larlet a écrit : > I got an issue with M2M relations because SQL is hardcoded and I > can't catch it in Query(Set) object: > http://code.djangoproject.com/browser/django/trunk/django/db/models/fields/related.py#L428 > It is/will be an issue for all non

Feedback from django-roa module

in order to help the community. Regards, David Larlet #9749 http://code.djangoproject.com/ticket/9749 #373 http://code.djangoproject.com/ticket/373 --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django devel

Re: Dropping Python 2.3 compatibility for Django 1.1

Le 27 nov. 08 à 02:39, Eduardo O. Padoan a écrit : > > On Tue, Nov 25, 2008 at 3:08 PM, Jacob Kaplan-Moss > <[EMAIL PROTECTED]> wrote: >> >> Hi folks -- >> >> I'd like to officially drop Python 2.3 support in Django 1.1. >> Discuss. >> >> Jacob > > +1 -- because reusable apps developers could

Re: A (last-minute) compromise on {% url %}

Le 29 août 08 à 17:18, Jacob Kaplan-Moss a écrit : > > Hi folks -- > > While working on some URL-related issues, I ran across a pretty big > problem with having ``{% url %}`` propagate ``NoReverseMatch`` up into > the templates: if it does that, there's no way to have "optional" > links. The

Re: One more issue with file storage

Le 10 juil. 08 à 21:11, Marty Alchin a écrit : > > On Thu, Jul 10, 2008 at 2:52 PM, [EMAIL PROTECTED] > <[EMAIL PROTECTED]> wrote: > >> This was also influenced by the Amazon S3 API which was going to be >> implemented as an alternate strategy for this project. > > There's also work being done

Re: URL Resolvers: a little refactoring goes a long way

Ken, It looks interesting but are there any examples of your urlresolver usage? David Le 24 juin 08 à 21:35, Ken Arnold a écrit : > > newforms-admin has a special-cased URL dispatcher in site.py. (see > #6470) > > Various REST-ish frameworks have a '.*' url mapping and a similar > hacky

Re: Introducing ModelView, a RESTful class-based view of your resources

Salut Clément, Le 19 juin 08 à 16:15, tifosi a écrit : > > Hi David, > > Thank for your code and the repository, I use the django-rest- > interface and > it's good news, that someone continue the job. > > I would like to get nested resources (e.g.: /articles/1/comments/ or >

Re: One more issue with file storage

Le 9 juin 08 à 19:11, Marty Alchin a écrit : > I've been fairly quiet on the file storage front for a while, since > it's basically done now, and is just waiting on the streaming upload > ticket to hit trunk first. Since I got to that point, however, I've > had two different people, working on

Re: Introducing ModelView, a RESTful class-based view of your resources

Le 9 juin 08 à 13:52, David Larlet a écrit : > > Le 8 juin 08 à 16:11, Ivan Sagalaev a écrit : >> >> David Larlet wrote: >>> This is not a secret that I'm interested in both Django and Semantic >>> Web. I'm following discussion about Django+REST for more t

Re: Django releases

Le 10 juin 08 à 03:16, Karen Tracey a écrit : > I'd trade your controversial part for an alternative: merge mewforms- > admin back to trunk now. +1 if involved people in this branch agree (I hadn't found the time to test it yet...). > I think it's a shame newforms-admin wasn't done in a

Re: Introducing ModelView, a RESTful class-based view of your resources

Le 8 juin 08 à 16:11, Ivan Sagalaev a écrit : > > David Larlet wrote: >> This is not a secret that I'm interested in both Django and Semantic >> Web. I'm following discussion about Django+REST for more than two >> years and when I realize that newforms-admin branch

Introducing ModelView, a RESTful class-based view of your resources

Hello, This is not a secret that I'm interested in both Django and Semantic Web. I'm following discussion about Django+REST for more than two years and when I realize that newforms-admin branch will use class- based generic views [1], I decided that it's probably the right moment to do

Re: Django-RDF

Stefan, It looks really promising but it's really hard to evaluate it without any code (or detailled examples). I can't wait for the ready-for- release time :) Is there any reason that you don't use any existing lib (rdflib, librdf, rdfalchemy, etc)? Anyway, let me know if I can help, I'd

Re: QSRF Related

Le 29 avr. 08 à 22:38, David Cramer a écrit : > > Yes im aware of the backwards incompatibility page but that mostly > covers the public api. A lot of time for our uses we have to go > beyond just using the public api. This is another situation where > having more releases could help :)

Re: API question for model saving

Le 28 avr. 08 à 09:33, David Danier a écrit : > >> Sometimes when calling save(), we know (for business reasons) that it >> must create a new object or raise an error. Similarly, in other >> cases, >> it either must update an existing object or raise an error. > > I think discussion about

Re: Easier URL patterns

Le 8 avr. 08 à 08:25, Adrian Holovaty a écrit : > > On Mon, Apr 7, 2008 at 3:49 PM, Rob Hudson <[EMAIL PROTECTED]> > wrote: >> would be much less daunting to those that haven't read the Friedl >> book >> than this: >> >>url(r'^(?P[-\w]+)/$', myview), > > Note that this example is more

Re: GSoC proposal: Resource-based Models

Le 2 avr. 08 à 02:09, [EMAIL PROTECTED] a écrit : > > > Models in Django are conceputally based on tables in a database. I'd > like to enhance that with the introduction of resource-based models. > The basic idea comes from Ruby on Rails' ActiveResource, which allows > for interaction between two

Re: django-restapi Improvements Proposal

Le 7 mars 08 à 20:26, Jared Flatow a écrit : > > On Mar 7, 2008, at 3:19 AM, versae wrote: >> After working with great intensity with django-restapi we discovered >> some fails and some unimplemented features, > > Anything in particular? Same here, we (my team) need to fix a lot of things in

Re: extends headaches

gt; > On Thu, 2008-02-07 at 15:06 +0100, David Larlet wrote: >> >> Le 6 f�vr. 08 � 21:01, SmileyChris a �crit : >> >>> >>> On Feb 6, 9:43 pm, Malcolm Tredinnick <[EMAIL PROTECTED]> >>> wrote: >>>> It already results in a broken s

Re: extends headaches

Le 6 févr. 08 à 21:01, SmileyChris a écrit : > > On Feb 6, 9:43 pm, Malcolm Tredinnick <[EMAIL PROTECTED]> > wrote: >> It already results in a broken site, we're now just being a lot >> clearer >> about that. > > Actually, it only resulted previously in a broken site if the extended >

Re: [7084] extends headaches

Le 5 févr. 08 à 22:05, Malcolm Tredinnick a écrit : > > > On Tue, 2008-02-05 at 16:14 +0100, David Larlet wrote: >> Hello, >> >> I'd just updated my local version of django and it raises errors due >> to 7084 changeset (extends should be the first tag). I put al

[7084] extends headaches

Hello, I'd just updated my local version of django and it raises errors due to 7084 changeset (extends should be the first tag). I put all my extends tags above all my load tags in every templates and I realize that it raises errors for comment tags too... I used to keep svn infos at the

Re: Add Add "georss" tag to feeds

Le 20 déc. 07 à 10:27, Daniel de la Cuesta a écrit : > Hi all, > > I want to add the geo tag (with latitude and longitude) to each item > of my feeds: > > 45.256 -71.92 > I am using the feeds framework: > class LatestEvents(Feed):title = "Latest Events"link > = "/events/"

Re: Django 1.0 features -- the definitive list

Le 30 nov. 07 à 07:33, Adrian Holovaty a écrit : > > Let's get a definitive list of features we want in Django 1.0, and > let's release it. Just great. > > Without further ado, here's my list: > > * newforms-admin > * queryset-refactor > * django.newforms becomes django.forms > * Model-level

Re: form_for_instance and form argument, empty form?

Marty Alchin a écrit : > On 11/7/07, David Larlet <[EMAIL PROTECTED]> wrote: > >> Unfortunately, what happens with my Form is exactly what I'd like to do: >> create a generic form from a Form class which define fields (with >> widgets, etc) and methods and which i

Re: form_for_instance and form argument, empty form?

Marty Alchin a écrit : >>> On 11/7/07, David Larlet <[EMAIL PROTECTED]> wrote: >>> >>>> Hi all, >>>> >>>> I'd spent a long time finding that bug but I want to be sure before >>>> submittin

form_for_instance and form argument, empty form?

Hi all, I'd spent a long time finding that bug but I want to be sure before submitting it on Trac. If you pass a form argument to form_for_instance like that: forms.form_for_instance(foo, form=FooForm) with an instance of foo which only contains a basic field (let's say a CharField) and

Re: Changes to request_response have broken django-rest-interface

2007/10/18, Malcolm Tredinnick <[EMAIL PROTECTED]>: > > On Tue, 2007-10-16 at 21:52 +0200, David Larlet wrote: > > 2007/10/10, David Larlet <[EMAIL PROTECTED]>: > > > > > > BTW, no more thought about the way of handling PUT? I've just added a >

Re: Changes to request_response have broken django-rest-interface

2007/10/10, David Larlet <[EMAIL PROTECTED]>: > > BTW, no more thought about the way of handling PUT? I've just added a > patch against test.client which add .put() and .delete(), I'm waiting > for (a) reaction(s) to add tests and documentation. > Sorry for in

Re: Changes to request_response have broken django-rest-interface

2007/10/8, Peter Nixon <[EMAIL PROTECTED]>: > > Hi David > > Thanks for doing this. I have written a patch for mod_python and added it to > the ticket. I have tested it and deployed it with a patched rest api in > production ;-) > Ok, can you add your patch against django.http.__init__.py too,

Re: django-rest-api use [was Re: Changes to request_response have broken django-rest-interface]

2007/10/7, Malcolm Tredinnick <[EMAIL PROTECTED]>: > > The Resource class is quite as independent from everything as we would > have liked. I say "we" here because towards the end of the SoC period, > Andreas and I spent quite a long time trying to loosen a few of the > couplings between output

Re: Changes to request_response have broken django-rest-interface

2007/10/7, Malcolm Tredinnick <[EMAIL PROTECTED]>: > > On Sun, 2007-10-07 at 02:39 +0200, David Larlet wrote: > > The > > option (3) seems more natural to me to make the difference between > > what you post and the POST verb, it's more explicit. What about

Re: Changes to request_response have broken django-rest-interface

2007/10/6, Malcolm Tredinnick <[EMAIL PROTECTED]>: > > I had a quick read of it. Looks like you're on the right track. Thanks for your reactivity. > > The main problem I see with it is that you're over-populating the data > structures a bit. If the request is a PUT, you're still populating >

Re: Changes to request_response have broken django-rest-interface

2007/10/5, Malcolm Tredinnick <[EMAIL PROTECTED]>: > > On Fri, 2007-10-05 at 16:17 +0300, Peter Nixon wrote: > > On Thu 04 Oct 2007, Malcolm Tredinnick wrote: > > > On Thu, 2007-10-04 at 18:10 +0300, Peter Nixon wrote: > > > > I tried to open the following ticket but it thinks my IP is a spammer,

Re: GenericForeignKey and GenericRelation, possible bug?

2007/9/6, David Larlet <[EMAIL PROTECTED]>: > Hi all, > > Before submitting a bug I'd like to be sure that it hadn't been done > intentionally, here is the issue: > > I had a model with two GenericForeignKeys which where defined like that: > > class

GenericForeignKey and GenericRelation, possible bug?

Hi all, Before submitting a bug I'd like to be sure that it hadn't been done intentionally, here is the issue: I had a model with two GenericForeignKeys which where defined like that: class Foo(models.Model): item = generic.GenericForeignKey(ct_field="item_content_type",

Re: Time for a new release?

2007/8/26, James Bennett <[EMAIL PROTECTED]>: > > On 8/26/07, David Larlet <[EMAIL PROTECTED]> wrote: > > I agree that users do not try to read the local docs for the moment, > > but maybe it's because the ReST style discourage them to do so. Let's > > try to a

Re: Time for a new release?

2007/8/26, Simon Greenhill <[EMAIL PROTECTED]>: > > On Aug 26, 9:56 pm, "David Larlet" <[EMAIL PROTECTED]> wrote: > > I agree that users do not try to read the local docs for the moment, > > but maybe it's because the ReST style discourage them

Re: Time for a new release?

2007/8/26, James Bennett <[EMAIL PROTECTED]>: > > On 8/26/07, Nicola Larosa <[EMAIL PROTECTED]> wrote: > > They shouldn't have to go the web site: the release docs should be on their > > disk, within the installed release itself (see my other message). > > See above. I'm sure you mean well, but

Re: GSoC 2007 Status Update VII: Django REST interface

2007/8/19, Andreas Stuhlmüller <[EMAIL PROTECTED]>: > > On 8/17/07, David Larlet <[EMAIL PROTECTED]> wrote: > > Just one (latest?) thought, it's a bit hard to debug because > > 400 errors are not really verbose, is it possible to find a > > way to make

Re: GSoC 2007 Status Update VII: Django REST interface

2007/8/13, Andreas Stuhlmüller <[EMAIL PROTECTED]>: > I added code for forms to TemplateResponder (create_form, > update_form), an example that shows how to use this code and another > example that shows how to specify the data format at the end of your > URLs. I didn't know the curry function,

Re: GSoC 2007 Status Update VI: Django REST interface

2007/8/12, Andreas Stuhlmüller <[EMAIL PROTECTED]>: > > On 8/11/07, David Larlet <[EMAIL PROTECTED]> wrote: > > Here is my suggestion: the current forms from model or instance are > > great but you often need a custom form, what about an extra-argument > >

Re: GSoC 2007 Status Update VI: Django REST interface

2007/8/5, Andreas Stuhlmüller <[EMAIL PROTECTED]>: > > I am currently reading "RESTful Web Services" by Leonard Richardson > and Sam Ruby. See [3] for a summary of the main points from the > chapter on best practices for REST-oriented architectures with short > notes on where the REST interface

Re: GSoC 2007 Status Update IV: Django REST interface

2007/8/3, Andreas Stuhlmüller <[EMAIL PROTECTED]>: > > On 7/13/07, David Larlet <[EMAIL PROTECTED]> wrote: > > * About users, how can I handle django users' permissions? John > > Sutherland had already done some work on django-crudapi [1] and it > > could

Re: Proposal: QuerySet.exists() method

2007/7/14, Gary Wilson <[EMAIL PROTECTED]>: > > James Bennett wrote: > > On 7/13/07, Adrian Holovaty <[EMAIL PROTECTED]> wrote: > >> I'm biased, because I have an immediate need for this in a project, > >> but this seems general and useful enough for inclusion in QuerySet. > > > > Implementing

Re: GSoC 2007 Status Update IV: Django REST interface

2007/6/23, Andreas Stuhlmüller <[EMAIL PROTECTED]>: > > As always, criticism, ideas and suggestions are welcome! > Ok let's go :-) First of all, thanks for your awesome work, I eventually take time to review it and it sounds exactly what I expected. Here are some random thoughts about the

Re: Status of contrib.comments rewrite?

2007/6/26, Jacob Kaplan-Moss <[EMAIL PROTECTED]>: > > On 6/26/07, David Larlet <[EMAIL PROTECTED]> wrote: > > I'm just curious, I've read somewhere (maybe here) that the > > contrib.comments package need to be rewritten in order to allow more > > flexibilit

Status of contrib.comments rewrite?

Hi, I'm just curious, I've read somewhere (maybe here) that the contrib.comments package need to be rewritten in order to allow more flexibility (like user.get_profile) and to use newforms. I thought that's the main reason why this part is not documented. What's the status of this update? Did

Re: 'retrieve': the missing permission?

2007/6/20, David Larlet <[EMAIL PROTECTED]>: > 2007/6/20, Gábor Farkas <[EMAIL PROTECTED]>: > > > > David Larlet wrote: > > > 2007/6/18, David Larlet <[EMAIL PROTECTED]>: > > >> Hi, > > >> > > >> I've just tr

'retrieve': the missing permission?

Hi, I've just tried to use the permission_required decorator for my views and I realise that there is a missing 'retrieve' permission. It's a bit odd because others ones follow the CRUD permissions. Am I missing something here? The patch is trivial: Add 'retrieve' to the

Re: signals

2007/6/10, Brian Harring <[EMAIL PROTECTED]>: > Curious, how many folks are actually using dispatch at all? I use signals this way: http://groups.google.com.mt/group/django-users/browse_thread/thread/dcc8ed4b26fd261c/12a19040ad7af699?lnk=gst=2#12a19040ad7af699 and it can be useful too when you

Re: Ping: Extend "for" tag to allow unpacking of lists

2007/6/5, SmileyChris <[EMAIL PROTECTED]>: > > Ticket http://code.djangoproject.com/ticket/3523 has been sitting > quietly for a couple of months as a design decision and it's a > reasonably common question in the IRC channel so I thought I'd ask a > core developer for a decision. > I'm not a

archive_year generic view and object_list order

Hi, I just wonder why the archive_year function returns an object_list (with make_object_list parameter to True) which is ordered by date_field. I know that I can use the reverse argument in for loop tag but I wonder if I'm the only one to have this issue? What order did you expect by default? I

Re: RESTful web services for Django

First of all, thanks for your GSoC proposition, it looks very interesting and I hope it will be integrated to the trunk at the end of the summer because I really need it ;-). 2007/5/8, Andreas Stuhlmüller <[EMAIL PROTECTED]>: > > I will try to come up with a concrete example that allows me to >

Re: GSoC status?

2007/4/29, Jay Parlar <[EMAIL PROTECTED]>: > > On 4/28/07, David Larlet <[EMAIL PROTECTED]> wrote: > > I just hope those ones will be successful! Maybe we can learn from the > > past and improve students/dev communication in order to help them a > > b

Re: GSoC status?

2007/4/28, James Bennett <[EMAIL PROTECTED]>: > > On 4/28/07, David Larlet <[EMAIL PROTECTED]> wrote: > > I'm just curious about SoC, especially the REST one, listed on this > > page: http://code.google.com/soc/django/about.html > > > > Maybe it's time to

Re: RESTful API

2007/4/25, John Sutherland <[EMAIL PROTECTED]>: > > Evening, > > I've put the RESTful API code that I mentioned in ticket 2553[1]. A > few people have requested the code and so it's now in a Google code > project: > > > Ideas? Suggestions? Requests?

Re: Are we dropping auto_now and auto_now_add for 1.0?

2007/4/6, Brian Beck <[EMAIL PROTECTED]>: > > On Apr 2, 12:52 pm, "trbs" <[EMAIL PROTECTED]> wrote: > > It could be just me, but although i don't mind losing auto_*, it don't > > look very DRY in save. > > > > I know it's only a few lines (like 4 ? for both options, not using > > default= for

Re: Stability of LogEntry in django newforms?

2007/4/3, Adrian Holovaty <[EMAIL PROTECTED]>: > > On 4/3/07, David Larlet <[EMAIL PROTECTED]> wrote: > > I'd like to add a log for some objects of my project and after playing > > a bit with signals, I remember that there is a similar "feature" in > &

Stability of LogEntry in django newforms?

this model for professional use, may I know if this part of the admin is stable and is not intended to be removed in the new branch? Next question is how did you make the difference with signals (post_save) between creation and modification of an item? Thanks, Da

Re: About *Fields, newforms and lazyness

2007/3/6, David Larlet <[EMAIL PROTECTED]>: > Hi, > > I got some troubles today with newforms. I use to create models fields > with a first implicit verbose_name argument: > email = models.EmailField("E-mail") > > Unfortunately newforms fields have quit

Re: About *Fields, newforms and lazyness

2007/3/6, Rubic <[EMAIL PROTECTED]>: > You'd be breaking the code of early newforms adopters for an arguable > benefit. It wouldn't affect my development base since I explicitly > use label=, but I can imagine other users might get irritated. Given the fact that label is not always at the same

About *Fields, newforms and lazyness

Hi, I got some troubles today with newforms. I use to create models fields with a first implicit verbose_name argument: email = models.EmailField("E-mail") Unfortunately newforms fields have quite similar argument (label) but it's not the first argument. Moreover, it's a bit annoying because I

Re: ChoiceField and newforms

2007/2/28, Domenico Chierico <[EMAIL PROTECTED]>: > > HI, > > I'm new to django so excuse me if this is the wrong way to manage my > problem. > > I've found a problem into form_for_model function related to > forms.ChoiceField, that seem to be not considered, for IntegerField > and FilePathField

Re: Developer documentation?

2007/2/8, James Bennett <[EMAIL PROTECTED]>: > > Anybody got strong feelings on this? > It takes a lot of time and it depends on the target. If it's to recruit django devs, ok. Otherwise, your django tips are maybe more appropriated. I know it's not the "official" doc but, except if you decide

Some kind of django.contrib.stats?

Hi, I wonder if something like bbclone [1] (especially the "live" view [2]) exists in python? I've just found Peastat [3] which looks new but interesting (fortunately, the author is maybe on this list). What else did you use to know where are your current visitors? Same question for long term

Re: Status update on newforms-admin branch

2007/2/4, Russell Keith-Magee <[EMAIL PROTECTED]>: > > The *Inline classes need not just be data containers - they could > contain all the rendering information for handling their own display, > and the display of the subforms for each related object - and if this > is the case, they can be used

Re: Critical ticket: can cause data loss

2007/1/30, Russell Keith-Magee <[EMAIL PROTECTED]>: > > On 1/30/07, David Larlet <[EMAIL PROTECTED]> wrote: > > I'm +1 on this option. Before making decision what about at least add > > a warning message on the documentation page? > > This is kind of the poin

Re: Critical ticket: can cause data loss

2007/1/29, James Bennett <[EMAIL PROTECTED]>: > > On 1/29/07, Ned Batchelder <[EMAIL PROTECTED]> wrote: > > I don't know that you need to make a release for this fix, but I think you > > should alert people to it. There is a mailing list for announcing releases > > and security issues, right?

Re: Web services in Django

2006/12/22, juampa <[EMAIL PROTECTED]>: > > Hello all: > > I am trying to gather all the information I can about implementing web > services with Django (XML-RPC, SOAP, REST). Can you suggest good > sources of information/examples of implementations? What is the offical > status of WS support in

Re: Spamblocked ticket: #2282 (Urlify in admin compatible with accents)

2006/10/27, orestis <[EMAIL PROTECTED]>: > > Here's a thought: > > Can't every language have its own urlify.js file ? Like urlify.fr.js, > urlify.el.js, urlify.de.js etc. Django selects the correct one by > looking at the Locale settings, or falls back at the default (English) > one if there

Trac and Akismet rejected spam

I'd like to update the french translations urls in http://code.djangoproject.com/wiki/TranslateDocumentation with this new content : http://vrac.biologeek.com/askimet_error.txt and I get an Askimet rejected spam error. So, how can I do to update this page? Regards, David

Slides of Europython 2006?

Hi! I'd like to know if it's possible to have access to django slides of Simon's conf at Europython 2006. Maybe I haven't found those but there are not listed on the official page: http://indico.cern.ch/sessionDisplay.py?sessionId=9=44 Cheers, David Larlet

urlify.js blocks out non-English chars - 2nd try?

difficult (I've pasted a js from a french blog app on my ticket) but I'm conscious there are more problems with other languages. Concerning utf-8 URLs, I don't know if it's really a good idea because this is actually associated to phishing... Cheers, David Larlet