Re: ANN: Please welcome Django's new release manager!

On 1/19/07, Jacob Kaplan-Moss <[EMAIL PROTECTED]> wrote: > > Howdy folks -- > > Please join me in welcoming James Bennett as Django's release manager! > Indeed! Welcome as release manager, James! Cheers, deryck --~--~-~--~~~---~--~~ You received this message bec

Patches to apply for 0.95.1

In preparation for releasing Django 0.95.1 I've created a "0.95-bugfixes" branch and applied several post-0.95 fixes to it: * The fix for the compile-messages problem is in. * The fix for the LazyUser bug is in. * The patch which disables flup tracebacks under FastCGI is in. I think that covers

Re: Some thoughts on our security policy as we head towards 1.0

On 1/19/07, Michael Radziej <[EMAIL PROTECTED]> wrote: > Hmmm, isn't that just a more explicit definition approach 2? If you find > it easier, create a bugfix branch with the major release, but this > doesn't matter much for the users. I'd say do it as it pleases the > committers. I like having a

Re: ANN: Please welcome Django's new release manager!

On 1/19/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > Excellent, the bugfixes branch should clear up a number of issues (e.g. > [1]) That's already been patched, and I'm rolling 0.95.1 right now :) -- "May the forces of evil become confused on the way to your house." -- George Carlin --

Re: ANN: Please welcome Django's new release manager!

Excellent, the bugfixes branch should clear up a number of issues (e.g. [1]), there aren't many people better for the job than J.B. Congratulations! -- Simon G. [1] http://groups.google.com/group/django-users/browse_thread/thread/f1e342fe89a7eff2 --~--~-~--~~~---~-

Re: Patch to update django.utils.simplejson from 1.3 to 1.5

> Jacob is working to get re-open available again. Thank you, and thank you Jacob :-) -- Lawrence http://www.oluyede.org/blog http://www.neropercaso.it --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django devel

Re: Apache 1.3 and mod_python 2.x support

I uploaded changed version. As I noted in the comment, issue with the slash at the end of url is resolved. -- Sanel Zukan --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this

Re: Patch to update django.utils.simplejson from 1.3 to 1.5

On 1/19/07, Lawrence Oluyede <[EMAIL PROTECTED]> wrote: How can I reopen this ticket? http://code.djangoproject.com/ticket/3320 It's "ready for checkin" but "closed: invalid" also. It was closed with reason but now it has been fixed Jacob is working to get re-open available again. --~--~--

Re: Patch to update django.utils.simplejson from 1.3 to 1.5

How can I reopen this ticket? http://code.djangoproject.com/ticket/3320 It's "ready for checkin" but "closed: invalid" also. It was closed with reason but now it has been fixed -- Lawrence http://www.oluyede.org/blog http://www.neropercaso.it --~--~-~--~~~---~--~--

Re: ANN: Please welcome Django's new release manager!

Welcome James as RM!!! On 1/19/07, Jacob Kaplan-Moss <[EMAIL PROTECTED]> wrote: [...] --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developer

Re: triage policy: anonymous or self-reviews

On 1/19/07, Michael Radziej <[EMAIL PROTECTED]> wrote: what's our policy about anonymously changing the review state or about doing this for your own tickets? Do we want a peer review system such that really somebody else should check the ticket, or is it alright if you put it in the right categ

ANN: Please welcome Django's new release manager!

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

Re: database connection object handling and threading fastcgi

Michael Radziej wrote: can anyone tell me right away how the database handling works with the threading fastcgi server? I suspect that there's one global connection object, and then in each thread separate cursor objects created from the global connection, which is not going to work with mysql.

Re: triage policy: anonymous or self-reviews

On 1/19/07, Michael Radziej <[EMAIL PROTECTED]> wrote: Hi, what's our policy about anonymously changing the review state or about doing this for your own tickets? Do we want a peer review system such that really somebody else should check the ticket, or is it alright if you put it in the right

triage policy: anonymous or self-reviews

Hi, what's our policy about anonymously changing the review state or about doing this for your own tickets? Do we want a peer review system such that really somebody else should check the ticket, or is it alright if you put it in the right category by yourself? Michael --~--~-~--~~

Re: Some thoughts on our security policy as we head towards 1.0

Hi, James Bennett wrote. 1. When a security fix is released without a new Django release accompanying it, update the current release tarball listed on the download page. Upside: the official release tarball will always have the latest security fixes applied. Downside: the release tarball won't

database connection object handling and threading fastcgi

Hi, can anyone tell me right away how the database handling works with the threading fastcgi server? I suspect that there's one global connection object, and then in each thread separate cursor objects created from the global connection, which is not going to work with mysql. (This is about tick

Re: Absolute URL's in documentation

Trying to upload diff: akismet spam error (too many links) Trying to upload tar of the same: TypeError: PgQuoteString() argument 1 must be string without null bytes, not str On Jan 20, 8:32 am, Jacob Kaplan-Moss <[EMAIL PROTECTED]> wrote: On 1/19/07 1:01 PM, SmileyChris wrote: > Done, but can

Re: Absolute URL's in documentation

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

Re: Django BoF at PyCon 2007

There are now two Open Space sessions planned: * Django BoF : An informal gathering for anyone who's interested in Django. Meet and greet and general mingling. * Django application showcase : A presentation

Re: Absolute URL's in documentation

Done, but can't submit it. On Jan 20, 6:27 am, "Adrian Holovaty" <[EMAIL PROTECTED]> wrote: On 1/18/07, telenieko <[EMAIL PROTECTED]> wrote: > I was writting a document for Django's documentation (#3325) and just > noticed that links between documents of the documentation are absolute, is > th

Re: specifying newforms-admin options

From a puritanical point of view, I would like to see the admin options separated from the fields. It could also allow for more flexibility. I think a ModelAdmin class in the same file but separate from the Model class would be easiest to manage, if that were possible. Assuming the default use

Re: Absolute URL's in documentation

On 1/18/07, telenieko <[EMAIL PROTECTED]> wrote: I was writting a document for Django's documentation (#3325) and just noticed that links between documents of the documentation are absolute, is this intentional ? If one would like to run his/her own mirror at home converting the .txt to .html he

Re: Absolute URL's in documentation

On 1/18/07, telenieko <[EMAIL PROTECTED]> wrote: I was writting a document for Django's documentation (#3325) and just noticed that links between documents of the documentation are absolute, is this intentional ? If one would like to run his/her own mirror at home converting the .txt to .html he

Re: Apache 1.3 and mod_python 2.x support

On 1/18/07, Sanel Zukan <[EMAIL PROTECTED]> wrote: I reworked Manuzhai's patch located at http://code.djangoproject.com/ticket/376 so it can fit to the current 0.95 version. I would like to ask trac's admins to reopen that item, since I can't find reopen box (probably I will need to log in :))

Re: specifying newforms-admin options

On 1/18/07, oggie rob <[EMAIL PROTECTED]> wrote: In the newforms-admin wiki there is mention of a "cleaner way to specify admin options". Has this been discussed yet? If so, my apologies. I've kind of been out of the loop for a while. If not, can we start? Sure, now is as good a time as any!

Re: Disable field creation in forms for hidden model fields (#3247)

simonbun wrote: If editable=False is specified in the model, then I personally would expect it not to show up in the form_from_model form either. On the other hand, I'm not so sure that the need to differentiate the editable option between the admin contrib and plain form_from_model is so gener

Re: {% url %}

It might be wiser to wait for (a decision on) the root view solution. Url reversing is more complex than the current setup allows. For example predefined values in the routing setup are llowed, the reverse url tag should be able to access these (think about setting https=1, then https url would b

specifying newforms-admin options

Hi all, In the newforms-admin wiki there is mention of a "cleaner way to specify admin options". Has this been discussed yet? If so, my apologies. I've kind of been out of the loop for a while. If not, can we start? -rob --~--~-~--~~~---~--~~ You received this m

Re: Using Capistrano to Deploy/Maintain Django Applications

I would be all for that approach, as my needs are pretty simple. Please keep me informed of your progress, I'd love to try it out. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post

Great Free Surprise

*Media Mall Toolbar : Advanced 1-click System to the Following Items :* *- 200 Live TV Channels - FM Radio With alot of Radio Stations and You Can Add More. - Live WebCams around The World - Tools and Essentials as : Online Spyware Scanners,Online Virus Scanners and Online Firewall S

Re: {% url %}

I would prefer the root view solution. Url reversing is more complex than the current setup allows. For example predefined values in the routing setup are allowed, the reverse url tag should be able to access these (think about setting https=1, then https url would be generated (-1:http url, 0:

Re: Ticket+Patch+doc exists, whats next?

I can think of two things: * It's missing tests * The triage team is now going ticket by ticket getting things ok, so they, maybe, go over your ticket in a near future and look at it ;) Cheers, Marc PS: +1 for the patch :P On 1/19/07, Wolfram Kriesing <[EMAIL PROTECTED]> wrote: http://co

Re: Ticket+Patch+doc exists, whats next?

Hi Wolfram, Wolfram Kriesing: http://code.djangoproject.com/ticket/3163 what do i need to do next to get this in or rejected? Thanks! Contrib docs say that new features are best introduced on this mailing list ;-) The ticket itself will eventually be reviewed on its on during ticket triage,

Ticket+Patch+doc exists, whats next?

http://code.djangoproject.com/ticket/3163 what do i need to do next to get this in or rejected? -- thx Wolfram --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send

Re: Some thoughts on our security policy as we head towards 1.0

On 1/19/07, James Bennett <[EMAIL PROTECTED]> wrote: And that's a lot to think about and discuss, so I'll stop there for now, but if anybody's got other concerns/ideas about the security policy, I think we should get them out in the open and discuss them; this is already really important stuff t

Re: Some thoughts on our security policy as we head towards 1.0

On 1/19/07, James Bennett <[EMAIL PROTECTED]> wrote: Down the road, it might also be useful to have some sort of designated liasion from the dev team to third-party package maintainers, both so they'd have someone they know they can contact on the Django team, and so we'd have someone who knows

Re: Some thoughts on our security policy as we head towards 1.0

On 1/19/07, James Bennett <[EMAIL PROTECTED]> wrote: 1. When a security fix is released without a new Django release accompanying it, update the current release tarball listed on the download page. Upside: the official release tarball will always have the latest security fixes applied. Downside

Re: {% url %}

I've marked it as Accepted, I think all it's lacking is a brief bit of documentation (an example and explanation), and then it's just up for the core devs to say yay/nay. --Simon --~--~-~--~~~---~--~~ You received this message because you are subscribed to the G

Re: {% url %}

simonbun wrote: However, this solution doesn't take generic views into account, and those are pretty hard to give up. In fact I have some ideas how to make it but it requires some more thinking from my side... Anyway I'm a bit reluctant to add it to this ticket because as of now it's very

Re: {% url %}

This would be a very good solution to the duplication of urls in urlconf and other places throughout the code. Also, it would provide a way to link to certain views, wich is useful, for instance to specify a form action url. However, this solution doesn't take generic views into account, and tho

i18n: Courtesy threatments

I firstly sent that to the i18n group but for some reason it doesn't show up on the google group (neither did a message I sent yesterday) so I'm forwarding it do -developers just in case the i18n group is screwed (which is the case if those of you are subscribed there have not received this!), so

Re: Disable field creation in forms for hidden model fields (#3247)

I think its a good idea. If editable=False is specified in the model, then I personally would expect it not to show up in the form_from_model form either. On the other hand, I'm not so sure that the need to differentiate the editable option between the admin contrib and plain form_from_model is

Re: Some thoughts on our security policy as we head towards 1.0

James Bennett wrote: * Any time a security fix is issued, it gets applied to the relevant "bugfixes" branch, then a new minor release packaged from it. So the first security fix in 0.96 would be applied to 0.96-bugfixes, and 0.96.1 would immediately be packaged and released from that. +1, A ne

Re: Trac error uploading attachment

Jacob Kaplan-Moss: Yeah, I'm getting that too. I'll try to fix it if I can figure out what's up. Seems that the python database module tries to apply character recoding from unicode to a binary stream. Michael -- noris network AG - Deutschherrnstraße 15-19 - D-90429 Nürnberg - Tel +49-911-9