Re: Ticket #34646 Ordering a Django admin column based on multiple model fields

I also lately stumbled across this and was a little surprised that it could not handle multiple fields, as it is the case in other places. So +1 for fixing this from me :) Am 19. Juni 2023 03:05:41 MESZ schrieb David Sanders : >Mariusz is a developer, so that's at least 1 developer's opinion :)

Re: Model icons

w, especially I find this level of coupling acceptable. Cheers, Mark [0] https://docs.wagtail.org/en/stable/reference/contrib/modeladmin/index.html#a-more-complicated-example Am 18.02.23 um 21:31 schrieb Marty: Yeah, I've tried to create templatetag like this: @register.simple_tag

Re: Subparsers for management commands

Thanks Adam, nice solution. On Sunday, 15 January 2023 at 19:23:56 UTC+10 Adam Johnson wrote: > Hi Mark > > I agree that subparsers should use the same error formatting. > > After looking at the problem a bit more, I found a solution to pass > called_from_command_line throug

Subparsers for management commands

ld save repetition but would still require command authors have some special Django knowledge so I'd question whether it's worthwhile. I'm happy to contribute if advised on the preferred option. Cheers Mark -- You received this message because you are subscribed to the Google Gr

Re: Calling save_m2m() in UserCreationForm.save()

Hi Adam, thanks for the reply. I'll open a ticket and start work on a PR. Mark On Sunday, November 27, 2022 at 10:47:01 AM UTC Adam Johnson wrote: > Your proposal seems reasonable - if actually saving, we should save the > m2m fields too. > > I think the best next step w

Calling save_m2m() in UserCreationForm.save()

sword(self.cleaned_data["password1"]) if commit: user.save() *if hasattr(self, "save_m2m"):* *self.save_m2m()* return user I'd be happy to raise a ticket and work on a patch if this change would be useful. Thanks Mark [1] htt

Re: The blacklist / master issue

+1 on a good decision to make this change. -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-developers+unsubscr...@g

Re: timesince 'depth' parameter

+1 There are lots of subtleties for how it can behave, and I have written my own when I want specific behaviour. Other times I want something quick, and I've used timesince, and usually just put up with the fact that it's a bit longer than I want. Having that control would make it a lot more

Re: Hashing Session Keys in backends

Initial (draft) Pull Request: https://github.com/django/django/pull/12814 The pull request at the very least still needs documentation, but would be good to have a review of the implementation first. On Thursday, April 23, 2020 at 11:22:39 AM UTC+2, mark wrote: > > Hey Adam, thanks f

Re: Hashing Session Keys in backends

inimal changes to the *SessionBase* class to optimise backward compatibility. On Wednesday, April 15, 2020 at 1:41:00 AM UTC+2, Adam Johnson wrote: > > Hi Mark > > Thanks for looking into this tricky security issue. > > I'm suggesting to use the names frontend_ke

Hashing Session Keys in backends

After renewed interest because of potential database timing attacks (T31412 ) I'm looking into an existing PR (PR8736 for T21076 ) for adding the possibility of

Passing initial data to model formsets - a suggested improvement

regressions as if a user would like to limit the length of the forms they should already be doing so with the `max_num` parameter to the modelformset_factory. Othewrise, why not use the additional data in self.initial_extra? Mark -- You received this message because you are subscribed to th

Re: Using auth stuff without installing the auth app

g we want to support? Mark On Sunday, 28 August 2016 09:43:36 UTC+1, Aymeric Augustin wrote: > > On 23 Mar 2016, at 01:57, Matt > wrote: > > > I like to use the authentication machinery in Django, without explicitly > putting 'django.contrib.auth' in INSTALLED_A

Follow-up to #28307: Possible app_template improvements

at I think are good habits in the Django developer community. What do you think about this proposal? Kind regards, Mark -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group an

Re: DatabaseWrapper.needs_rollback and transaction.rollback()

I created an issue for this https://code.djangoproject.com/ticket/27504 , and created a pull request as well: https://github.com/django/django/pull/7577. -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To

Re: DatabaseWrapper.needs_rollback and transaction.rollback()

Re fixing transaction.rollback: What would be the preferred way to fix this? I haven't personally tested it (a coworker has and reports that it doesn't work), but BaseDatabaseWrapper.set_rollback requires that in_atomic_block be True when set_rollback is called, which is not the case in this ex

DatabaseWrapper.needs_rollback and transaction.rollback()

After a validationError occurs, why is the transaction considered dirty, blocking all db reads/writes? In this example: https://bitbucket.org/marky1991/django-test/raw/59c9ff89e4b12b4a831c36171139cb022735201b/test1.py , I don't really expect a TransactionManagementError at all, as the failure

Re: Withdrawing Channels from 1.10

Yes thank you Andrew for your continued work to move this conversation forward. I hope that Channels can continue to grow as an external package under the Django umbrella and bring on more contributors and improvements. Best, Mark On Tuesday, May 10, 2016 at 12:44:21 PM UTC-4, Ryan Hiebert

Re: My Take on Django Channels

Ryan, Sorry if you felt I was ignoring your reply to focus on the discussion with Andrew. You both made a lot of the same points at about the same time but I did want to touch on a couple things. On Thursday, May 5, 2016 at 4:21:59 PM UTC-4, Ryan Hiebert wrote: > > Thank you, Mar

Re: My Take on Django Channels

for arguably petty reasons. I don't want to see this work blocked because of a lack of DEP if it has the support of the core team and the larger community. I've said my piece about this work and I'm letting those past feelings go so that I can contribute more constructively to th

Re: My Take on Django Channels

ng) django.contrib.aiohttp/django.contrib.twisted/django.contrib.tornado would be the way forward for Django + websockets without a full scale rewrite of the WSGI specification. Not sure if I touched on all of your questions so please let me know if it seems like I'm skipping over something. - Mark On T

Re: My Take on Django Channels

Thank you for your comments and I have some brief replies. On Thursday, May 5, 2016 at 4:20:06 PM UTC-4, Andrew Godwin wrote: > > > > On Thu, May 5, 2016 at 12:34 PM, Mark Lavin > wrote: > > The main gains are (in my opinion): > - The same server process can serve

Re: My Take on Django Channels

Andrew, I worked very hard to edit the tone of this message and I'm sorry if you felt anything in here was a personal attack. That certainly was not my intent. My natural speaking tendency leans toward hyperbole and I think there may have been places which got away from me here. Best,

My Take on Django Channels

process and I will admit that has jaded many of my interactions with the core team. Building consensus is hard and I’m posting this to help work towards the goal of community consensus. Thanks for taking the time to read this all the way through and I welcome any feedback. Best, Mark Lavin

Re: Django Integration

" might impact performance or say that isn't a requirement to even measure, regardless of outcome, before its inclusion? - Mark On Wednesday, May 4, 2016 at 10:00:15 PM UTC-4, Russell Keith-Magee wrote: > > Hi Mark, > > On Thu, May 5, 2016 at 8:41 AM, Mark Lavin > wrot

Re: Django Integration

land. All I can do now is beg for these requirements to be optional. - Mark On Wednesday, May 4, 2016 at 6:48:03 PM UTC-4, Jacob Kaplan-Moss wrote: > > On Wed, May 4, 2016 at 2:45 PM, Marc Tamlyn > wrote: > >> Major features merged into Django have generally never been as &

Re: Django Integration

side of Django while it continues to mature. Best, Mark On Wednesday, May 4, 2016 at 3:18:03 PM UTC-4, Andrew Godwin wrote: > > > > On Wed, May 4, 2016 at 11:52 AM, Mark Lavin > wrote: > >> >> >> Given that there is no guarantee of message delivery, I don&#

Re: Django Integration

I like Markus' suggestion and I think that's in line with how Django handles other optional dependencies such as the db bindings (psycopg2, MySQLdb, etc). Those raise an ImproperlyConfigured exception when there is an import error. The memcache cache backend on the other hand raises an import e

Re: Django Integration

On Wednesday, May 4, 2016 at 12:39:02 PM UTC-4, Andrew Godwin wrote: > > > > On Wed, May 4, 2016 at 8:26 AM, Mark Lavin > wrote: > >> As noted in the PR there is at least one new setting, >> CHANNEL_SESSION_ENGINE, which is lacking documentation. >> > >

Re: Django Integration

lear why these are required if you are claiming that they aren't required to run. If these we're in the install_requires then I would withdraw the objections about them with regard to this change in Django. -Mark On Wednesday, May 4, 2016 at 10:26:22 AM UTC-4, Andrew Godwin wrote: &g

Re: Django Integration

those? Best, Mark On Tuesday, May 3, 2016 at 9:04:19 PM UTC-4, Andrew Godwin wrote: > > I'm basically slowly fixing the test system failures (mostly because I > introduced some new packages); the patch is ready to go code-wise, just > need to get it green. Let me fix the current s

Re: Channels integration plan, first draft

ing you've been working hard on and I'm not trying to be needlessly critical of your work. On Fri, Dec 18, 2015 at 10:07 AM, Andrew Godwin wrote: > > > On Fri, Dec 18, 2015 at 2:00 PM, Mark Lavin wrote: > >> Anssi criticisms are fair and I feel that some of these r

Re: Channels integration plan, first draft

Anssi criticisms are fair and I feel that some of these responses are glossing over the details. You've claimed this is the same or equivalent to a forked worker model but it isn't because there is no process management/link between the interface and worker and because you've chosen to make this ne

Re: Channels integration plan, first draft

ding to the client. That's two JSON serialization round trips which don't currently exist with no gain for existing applications. As you note later on this currently breaks non-root mounted (those using SCRIPT_NAME) applications but doesn't appear to have a plan to resolve it. Be

Tips on adding a Couchbase backend

e only supported where one of the sides is a PK). Note this only works for searches, not updates/inserts * CRUD operations * There's also views, but I'm guessing anything expressible as a view can also be expressed in terms of N1QL Can someone point me in the right direction of what to

Re: Idea/request for help: Django Developers Community Survey

the end of its support (or after). [ ] I don't bother upgrading Django, even if it becomes unsupported. Cheers, Mark. -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from

Re: Django Content Negotiation implement

It's also worth reviewing how this problem has been solved by the community before: django-piston, django-tasypie, django-rest-framework, django-nap, restless, etc to look for common patterns and solutions as well as things that haven't worked well in hindsight. Best, Mark On Mond

Re: Migrations and Reusable Apps

Support of south_migrations directory in South goes a long way to addressing this problem from my perspective so that's very good news to me. On Tuesday, June 17, 2014 1:34:02 PM UTC-4, Trey Hunner wrote: > > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > On 06/17/2014 10:05 AM, Andrew God

Re: Migrations and Reusable Apps

t sure how the transition when the app starts shipping its own migrations > will go. > > On Tuesday, June 17, 2014 9:18:57 AM UTC-4, Mark Lavin wrote: >> >> Hello, >> >> I noticed some changes over the past few days to the migrations and I was >> concerned

Migrations and Reusable Apps

like a good approach though it does highlight the backwards compatibility issues. Best, Mark -- You received this message because you are subscribed to the Google Groups "Django developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to dj

Re: DEPs: Django Enhancement Proposals

I'll be the first one to bite and submit one https://github.com/django/deps/pull/1 It needs a lot of work as noted in the PR but I'm happy to be a guinea pig for the process. Best, Mark On Monday, April 14, 2014 8:41:07 PM UTC-4, Russell Keith-Magee wrote: > > On Tue, Apr 15,

Re: Deprecating Widget Media class

possibly only in the admin) to improve the story for a third-party widget which requires some CSS/JS. Best, Mark On Tuesday, April 1, 2014 2:32:15 PM UTC-4, Tim Graham wrote: > > There's been some discussion in ticket > #22298<https://code.djangoproject.com/ticket/22298>about de

Re: Migrations in Django 1.7 make unit testing models harder

I don't see any meaningful notes about apps being required to ship migrations beginning with 1.9. I do see deprecation notes about the syncdb signals changing and the syncdb command itself is clearly deprecated. This legacy behavior is handled by sync_apps in the migrate command but there aren'

Re: Migrations in Django 1.7 make unit testing models harder

nfigs instead but it does look like it's been done. Best, Mark On Tuesday, March 25, 2014 2:14:55 PM UTC-4, Andrew Godwin wrote: > > Yes, the new behaviour is by design, in the sense that the workaround you > mentioned will be deprecated in 1.9 (along with all syncdb-related > fu

Re: #20824 - Email-based auth contrib module; some help required

used and others are skipped with the custom user is in use. You can see it in action here: https://github.com/mlavin/django-all-access I'd love to see a more general solution to this but I have a feeling anything that attempts to modify the DB tables between tests is destined to fail. Best,

Re: DisallowedHost causes 500 errors.

to a matching named logger under the django.security logging hierarchy. Along with this change, a handler400 mechanism and default view are used whenever a SuspiciousOperation reaches the WSGI handler to return an HttpResponseBadRequest. Best, Mark On Thursday, February 13, 2014 12:27:37 PM

Re: Migrations and System Checks

migration for the custom User table it could impact createsuperuser or changepassword. Those are just the commands in core/contrib. That doesn't include the numerous commands which exist in the Django eco-system. Best, Mark On Wed, Feb 12, 2014 at 6:56 PM, Andrew Godwin wrote: >

Migrations and System Checks

l implementation these checks are shown when they are clearly not needed such as when running migrate? If not, can I get some more clarity on the purpose of these system checks? Thanks, Mark -- You received this message because you are subscribed to the Google Groups "Django dev

Re: HTTP PUT request

Hey Malcolm, Is this still the case? This response was five years ago, why would Django not allow access to PUT and DELETE data? On Friday, 10 October 2008 11:09:02 UTC+11, Malcolm Tredinnick wrote: > > > On Thu, 2008-10-09 at 14:13 -0700, DaveV wrote: > > Ahh - never mind - I misread the firs

Re: Contenttypes.GenericForeignKey Docs Addition

I'm not sure if my patch is sufficiently clear (it's only two words), but I've created a patch and ticket here . -- You received this message because you are subscribed to the Google Groups "Django developers" group. To unsubscribe from this group a

Contenttypes.GenericForeignKey Docs Addition

Could it be mentioned that GenericForeignKey fields can't be accessed in forms in the docs? Without stackoverflow, I would've probably never figured this out. When you try to access it through the form, all you get is a FieldError saying that the model doesn't even have the field you're looking

Support Negative Indexing on QuerySets

In this support ticket (https://code.djangoproject.com/ticket/13089), the original closer said "This is a long-standing explicit design decision in the ORM, and so gets a wontfix...". What is the reasoning behind this? Why is negative indexing of querysets disallowed? Thanks! -- You received

Re: Recommending a Python 3-compatible MySQL connector

be able to help with any issues? Mark. -- You received this message because you are subscribed to the Google Groups "Django developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-developers+unsubscr...@googlegroups.com. To post

Re: e-mail changed to email in email validator

This was changed as part of https://code.djangoproject.com/ticket/17899 Best, Mark On Wednesday, December 19, 2012 4:23:24 PM UTC-5, Skylar Saveland wrote: > > I checked out 1.5 branch today and found a change that I can't find the > debate/announcement for: e-mail to email in &

Re: Trigger an event on add another

le/js/jquery.dj.selectable.js?at=default#cl-289 Not the prettiest solution but it works. Best, Mark On Friday, November 9, 2012 6:30:17 AM UTC-5, is_null wrote: > > Hi all, > > Is it possible to trigger an event on add-another ? > > Or is there a better solution to work around this problem

Re: #3011 - Custom User Models -- Call for final review

he easiest solution to me. Best, Mark On Friday, September 28, 2012 8:14:57 AM UTC-4, rizumu wrote: > > > It is great to see this merged, it has been a long time coming. :) > > I would like to add backwards compatibility to some apps and I'm looking > for a recomme

Re: Backporting some Python 3 support features to 1.4.x?

arger applications. Best, Mark On Thursday, September 6, 2012 2:10:18 PM UTC-4, Aymeric Augustin wrote: > > Hello, > > Several people have started porting their apps for Python 3, but they're > running into trouble when they try to support both Django 1.4 and > maste

Re: Don't assume that missing fields from POST data are equal to an empty string value.

I think Ian demonstrated exactly why this should not go in and that is not all forms are ModelForms. Imagine writing a REST API which allows for an optional format parameter for GET requests which is validated by a Django form. With the inclusion of this proposal all clients would be forced to spec

Re: Don't assume that missing fields from POST data are equal to an empty string value.

they can still be changed if they are given in the POST. That means exposing this form can allow changing a user to a superuser. Don't trust data from the client and be explicit about the fields you want to expose for the form to change. This is why the 'fields' and 'exclude&#

Re: Django/CherryPy problem with POST data

;") >>>cherrypy.quickstart() # this will start the CherryPy server on 8080 # The admin media will not be served, but this doesn't matter # Go to localhost:8080/admin/ # Try to login with your superuser, or just click the login button with blank input # Hangs --Mark -- You received

Re: Django/CherryPy problem with POST data

>Sounds like a ticket is called for. Ticket #14594 <http://code.djangoproject.com/ticket/14594> >To aid the debugging process, if you can provide a complete standalone >example (or at least a complete set of duplication instructions), that >would be most helpful. Working on

testsuite [was: four NoSQL backends you want? :)]

On Mon, Sep 27, 2010 at 08:37:08PM -0400, Alex Gaynor wrote: > > While developing my backend I basically ignored the existing tests > because it was impossible to learn anything from 700 test failures, > of which some are "expected and never will pass" (e.g. ones testing > that we generate only one

Re: four NoSQL backends you want? :)

On Tue, Sep 28, 2010 at 07:22:11AM +0800, Russell Keith-Magee wrote: > On Tue, Sep 28, 2010 at 1:51 AM, Mark Bucciarelli wrote: > > > > I guess the test suite must not cover all the basees, making it a > > necessary but not sufficient criteria for inclusion? > > >

Re: four NoSQL backends you want? :)

On Sat, Sep 25, 2010 at 10:21:06PM +0800, Russell Keith-Magee wrote: > > The number 4 wasn't actually the important bit - it was that I want > to see a range of noSQL approaches represented. I don't want to see > 4 key-value stores; I want to see a key-value store, and a document > store, and a col

Re: dev process [was: #11834: colorized debug page]

On Mon, Aug 16, 2010 at 10:31:11AM +0800, Russell Keith-Magee wrote: > On Mon, Aug 16, 2010 at 10:03 AM, Mark Bucciarelli wrote: > > > ?- random api lock (people tend towards complacency) > > I'm not entirely certain I understand this point -- or, at least, > how it wo

dev process [was: #11834: colorized debug page]

On Sat, Aug 14, 2010 at 03:03:27PM +0800, Russell Keith-Magee wrote: > > If you have suggestions on how we can improve Django's development > process and address these issues, we're happy to hear them. > You may find this interesting: http://openbsd.org/papers/asiabsdcon2009-release_eng

Re: Django, The Web Framework for perfectionists and innovative with rechargeable batteries.

On Fri, Jul 30, 2010 at 4:13 PM, Hooshyar Naraghi wrote: > > anyone who wishes to take _this_ Django and fork > it into a _new_ Dmango, can do it any time? > The devs here _extremely_ patient with whiners [1]. m [1] People with lots of ideas about how you should spend your free time, and spend

Re: Ticket #14007: Automatically discover models within a package without using the app_label Meta attribute

additional functionality. Looking at the issue from a broader perspective, I believe people expect to be able to convert Python modules into packages. This was certainly my expectation the first time I tried to factor a models module. - Mark On Wed, Jul 28, 2010 at 10:55 AM, Rajeev J Sebastian

Re: Ticket #14007: Automatically discover models within a package without using the app_label Meta attribute

Hi, The process of model discovery is not modified by this patch. Continue reading for more details. - Mark polymorphic is an interesting case, as it only defines one model and that model is abstract. Therefore polymorphic doesn't need to be in INSTALLED_APPS (and perhaps my examp

Ticket #14007: Automatically discover models within a package without using the app_label Meta attribute

y find it useful. Per the Django contributor guidelines I'm asking for guidance about whether this patch is considered non-trivial. Any feedback is appreciated. Thanks, - Mark http://code.djangoproject.com/ticket/14007 -- You received this message because you are subscribed to the Google

Re: Invalid SQL generated by objects.all()[:1]?

On Thu, Jul 15, 2010 at 5:57 PM, Ian Kelly wrote: > > Er, I'm pretty sure that MySQL does support both ORDER BY and > LIMIT/OFFSET.  At least, it is documented as supporting them. > Right you are. There are few restrictions on the type of statements in which subqueries can be used. A subquery ca

Re: Invalid SQL generated by objects.all()[:1]?

On Thu, Jul 15, 2010 at 2:18 PM, Alex Gaynor wrote: > > And yes, if what you say about the SQL spec is true, then Django will > emit semantically invalid SQL.  It's also emitting SQL that can be > perfectly understood by a lot of databases.  Despite SQL being a spec > most DBs implement it slightl

Re: Invalid SQL generated by objects.all()[:1]?

On Thu, Jul 15, 2010 at 2:04 PM, Alex Gaynor wrote: > > It may be that they aren't allowed by the spec, but the only database > (that Django includes an adapter for) that doesn't support them > (AFAIK) is MySQL. > Cool, so that adapter has a workaround? > > Further, Event.objects.all()[:1] doesn

Invalid SQL generated by objects.all()[:1]?

Hi, I've just been informed by a MonetDB developer that LIMIT and ORDER BY clauses are not allowed by the SQL spec in sub-selects. I filied a bug with them because the Django code: Event.objects.all()[:1] was failing because of invalid SQL. I don't have access to the SQL spec so I can't quo

Re: What is the correct behavior? [was: new backend: unit test ...]

On Wed, Jun 30, 2010 at 7:14 PM, Russell Keith-Magee wrote: > > It appears that MonetDB is behaving the same way as PostgreSQL. The > right approach in the test is to catch the exception and roll back the > cursor. > In 1.2 I see full_clean() and ValidationError let's me handle this in applicatio

[solved] What is the correct behavior? [was: new backend: unit test ...]

On Wed, Jun 30, 2010 at 2:19 PM, Mark Bucciarelli wrote: > > So what is the correct Django backend behavior? > I'm going with backend-dependent for pre-1.2 Django. In 1.2 full_clean() + ValidationError is to the rescue. Thanks, m -- You received this message because you are

What is the correct behavior? [was: new backend: unit test ...]

On Wed, Jun 30, 2010 at 7:56 AM, Mark Bucciarelli wrote: > On Wed, Jun 30, 2010 at 7:14 AM, Mark Bucciarelli wrote: >> >> Is this test look correct? >> > > It passes when using SQLite ... > It fails with a postgresql_pschopg2 backend. So what is the correct Django

Re: new backend: unit test for "autocommit-like" behavior

On Wed, Jun 30, 2010 at 7:14 AM, Mark Bucciarelli wrote: > > Is this test look correct? > It passes when using SQLite backend, so I think the test is good. > > Currently it fails on the get() with the error > >      current transaction is aborted >      (please ROLLBACK

new backend: unit test for "autocommit-like" behavior

t has a unique index. s = Simple(name='mark') s.save() s = Simple(name='mark') try: s.save() except OperationalError: pass # first one should be saved

Ticket #13184 (SubfieldBase and form validation). Seeking guidance

ng this, so that it can be fixed before 1.2 release. I would like to mention, that the ticket has a runnable, minimal (- ish) test case attached, that illustrates the problem, in my opinion, quite clearly. With apologies, Mark -- You received this message because you are subscribed to the Go

Re: Proposal for contrib feature (DictionaryField in models)

You're right. I forgot about JSON. I guess it can be encoded and stored as a JSON string and then decoded afterward. On Aug 11, 3:19 pm, Javier Guerra wrote: > On Tue, Aug 11, 2009 at 2:11 PM, Mark Ferrer wrote: > > I call it a DictionaryField and it takes a Python diction

Proposal for contrib feature (DictionaryField in models)

umentation standards and style guide. If it's a crap idea that only an inbred monkey with half a brain would think up, then I'll make sure to keep it away from daylight. Thanks, Mark --~--~-~--~~~---~--~~ You received this message because you are

Re: range in templates?

Not only a better place to ask...a better place to look for the answer. Thanks. --~--~-~--~~~---~--~~ 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@googleg

range in templates?

I'm new to django so I apologize if after reading through the docs and list I missed something obvious. I would like to do something like this in a template: {% for index in range(10) %} but I can't seem to find anything that will allow this. I've become used to the idea that when something that

django GSoC group

We've set up a group for participants in django's GSoC: http://groups.google.com/group/django-gsoc If you are a mentor, or potential student participant, please join the group so that we can discuss GSoC-related topics there. Regards, M

Google's Summer of Code

hat it means to be a mentor, a good place to start is here: http://code.google.com/soc/2008/faqs.html To volunteer to be a mentor, or to suggest ideas for projects, visit our "ideas" page: http://code.djangoproject.com/wiki/SummerOfCode2008 Please let me know if you have any

Re: Documentation restructuring

t Tom's suggestion to put it in a wiki. Not only would that lower the bar for user contributions but I think the overall docs quality would also benefit almost naturally from a the wiki jacket. In my expirience the automatic cross-linking al

Re: Django 1.0 features -- the definitive list

quot;roadmap"-feature of trac would then give us a nice progress-bar and could help to draw more focus onto the relevant tickets. -mark --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django deve

Re: ticket #5986, reviews welcome

> extend results of form_for_{instance,model}. > > Also, regression tests are included so all is guaranteed to work. > > Thanks, +1 from me. but i'm only an innocent bystander. ;-) -mark --~--~-~--~~~---~--~~ You received this message becau

Re: i18n missing feature ... continued (proposed solution for the upcoming sprint)

"'"s and the 'as identifier' and you end up exactly there (only using curly brackets instead of square). I honestly think we have the syntax part nailed by now. There is no way to make it any more readable without sacrifying functionality. If anyone thinks otherwise: Ple

Re: i18n missing feature ... continued (proposed solution for the upcoming sprint)

On Mon, 2007-11-19 at 11:38 +1100, Malcolm Tredinnick wrote: > > On Mon, 2007-11-19 at 00:22 +0100, Mark Green wrote: > > > > On Sun, 2007-11-18 at 02:01 -0800, alain D. wrote: > [...] > > > Your syntax is interesting but : > > > - I'm not sure

Re: i18n missing feature ... continued (proposed solution for the upcoming sprint)

e to see django going the way of most java frameworks in terms of verbosity here. Keeping template complexity down seems more important to me than saving my translators one trivial extra-step. YMMV. -mark --~--~-~--~~~---~--~~ You received this message because yo

Re: i18n missing feature ... continued (proposed solution for the upcoming sprint)

On Sun, 2007-11-18 at 11:23 -0600, Jacob Kaplan-Moss wrote: > On 11/17/07, Mark Green <[EMAIL PROTECTED]> wrote: > > {% blocktrans with value|filter as number %} > > This will have [[]]one item[[]] inside > [...] > > I stopped reading here. Anything that involv

Re: i18n missing feature ... continued (proposed solution for the upcoming sprint)

Sorry, I made a (hopefully obvious) mistake in my example, see below: On Sun, 2007-11-18 at 04:33 +0100, Mark Green wrote: > --- > > Template: > > - > {% blocktrans with value|filter as number %} > This will have [[]]one item[[]] inside > {% plural %} > This wi

Re: i18n missing feature ... continued (proposed solution for the upcoming sprint)

ber }} > items{% endblocktrans %} > > {% endinsideblocktrans %} > inside. > {% endblocktrans %} > > This way, the string to translate would be : > - "This will have %(link_items)s inside" > - "%(number)s items" I generally agree with your approach to t