Eclipse stack trace integration

[Thierry]

Any idea how to make the file names in the stack trace clickable to
open them in eclipse?

Symfony seems to do it:
http://symfony-reloaded.org/tools

Quote:
You can even click on any filename and Symfony will open your favorite
IDE at the right line (if you use a supported IDE).

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To post to this group, send email to django-develop...@googlegroups.com.
To unsubscribe from this group, send email to 
django-developers+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en.

Can't search 1.1 documentation on djangoproject.com

[Dougal Matthews]

If you head to http://docs.djangoproject.com/en/1.1/ and type in 'settings'
(for example) into the search on the right you'll notice that all the
results link to docs.djangoproject.com/en/dev/ rather than /en/1.1/.

It seems then that 'latest' under the search input is the development
version and there isn't an option for 1.1? When looking at the results the
url still contains 1.1 to add to the confusion.

This could be confusing for people that aren't closely following the new
features and changes.

Hopefully I've not missed this somewhere, I searched and couldn't find a
ticket.

Cheers,
Dougal

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To post to this group, send email to django-develop...@googlegroups.com.
To unsubscribe from this group, send email to 
django-developers+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en.

Re: dbsettings, and user configurable app settings

[Carl Meyer]

On Mar 1, 9:40 am, stuff4ash  wrote:
> I am not necesary advocating magic. But the need for a more robust (or
> lets say, any) configuration management exists for many.

"Configuration management" is a fuzzy phrase that can mean many things
to many people. I think it'd be more helpful to focus on specific
problems and possible solutions. My critique was specifically of the
suggestion you made for an automatic import of app-level settings.py,
which introduces magical behavior for (AFAICS) no gain. I've certainly
had the need for something like dbsettings or livesettings, though
I've often addressed it with a separate app/model rather than trying
to shoehorn django.conf.settings into a role it wasn't intended for. I
also agree that for projects with many reusable apps (which describes
all of mine), split settings are less headache to manage; I like
Transifex' conf-directory solution and have proposed it for Pinax.

It's not that the status quo is perfect and no improvement is
possible; just that specific suggestions with concrete use-cases are
more useful than handwavy claims about the need for some major new
subsystem whose purpose and specific features are not clear.

> I am very familiar with your setup, and its the best one in use I have
> seen. but it has several shortcomings.

So what shortcomings are relevant to you?

> one of the few times that I wished django was more plonish.

Which means what, in this case?

Carl

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To post to this group, send email to django-develop...@googlegroups.com.
To unsubscribe from this group, send email to 
django-developers+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en.

Ticket disposal

[Peter Sagerson]

Hello,

I submitted a patch[1] for 1.2 which was not accepted and almost certainly 
won't be in the future. This is perfectly fine, but it would be nice to get the 
bug closed wontfix so we have some closure (people are still adding themselves 
to the cc field). I just moved it to the 1.2 milestone with the intention that 
it would get swept up in a 1.2 cleanup, but that was apparently not the correct 
approach, as it was immediately reverted. The documentation is clear that I 
can't close it myself. As it stands, this ticket threatens to linger 
indefinitely. Can anyone advise on the correct procedure here?

Thanks,
Peter


[1] http://code.djangoproject.com/ticket/11526

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To post to this group, send email to django-develop...@googlegroups.com.
To unsubscribe from this group, send email to 
django-developers+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en.

Re: Ticket disposal

[Joseph Kocherhans]

On Mar 2, 2010, at 4:28 PM, Peter Sagerson wrote:

> Hello,
> 
> I submitted a patch[1] for 1.2 which was not accepted and almost certainly 
> won't be in the future. This is perfectly fine, but it would be nice to get 
> the bug closed wontfix so we have some closure (people are still adding 
> themselves to the cc field). I just moved it to the 1.2 milestone with the 
> intention that it would get swept up in a 1.2 cleanup, but that was 
> apparently not the correct approach, as it was immediately reverted. The 
> documentation is clear that I can't close it myself. As it stands, this 
> ticket threatens to linger indefinitely. Can anyone advise on the correct 
> procedure here?

Hey Peter. Did you ever end up making an external project for your LDAP patch? 
If you did, it would be cool to have a link to it in the ticket. I think a 
third party project is the best place for it. Feel free to close the ticket and 
point to this thread or say "because jkocherhans said so" in the comments. 
Pinging django-dev is probably the best way to handle stuff like this.

I hope you have created or do create a project for it since there is obviously 
interest. but since it can live outside of Django itself just fine, it probably 
should. Sorry I didn't reply to you message awhile back [1].

Thanks,
Joseph

[1] http://groups.google.com/group/django-developers/msg/8b354ab4e5d4724b

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To post to this group, send email to django-develop...@googlegroups.com.
To unsubscribe from this group, send email to 
django-developers+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en.

Re: Eclipse stack trace integration

[Russell Keith-Magee]

On Tue, Mar 2, 2010 at 10:00 PM, Thierry  wrote:
> Any idea how to make the file names in the stack trace clickable to
> open them in eclipse?
>
> Symfony seems to do it:
> http://symfony-reloaded.org/tools
>
> Quote:
> You can even click on any filename and Symfony will open your favorite
> IDE at the right line (if you use a supported IDE).

Django-developers is for discussing the development of Django itself.
Unless you're proposing a specific change to Django to improve IDE
integration, you should direct your question to Django-users.

Yours,
Russ Magee %-)

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To post to this group, send email to django-develop...@googlegroups.com.
To unsubscribe from this group, send email to 
django-developers+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en.

Re: Ticket disposal

[Peter Sagerson]

Thanks, Joseph.

I agree it works well as an external project. It's been on pypi for a little 
while[1] and I added the link again to the bottom of the (now closed) ticket. 
Incidentally, #2507[2] is a rather old and dusty ticket on the same subject.

Thanks,
Peter

[1] http://pypi.python.org/pypi/django-auth-ldap/
[2] http://code.djangoproject.com/ticket/2507


On Mar 2, 2010, at 2:53 PM, Joseph Kocherhans wrote:

> 
> On Mar 2, 2010, at 4:28 PM, Peter Sagerson wrote:
> 
>> Hello,
>> 
>> I submitted a patch[1] for 1.2 which was not accepted and almost certainly 
>> won't be in the future. This is perfectly fine, but it would be nice to get 
>> the bug closed wontfix so we have some closure (people are still adding 
>> themselves to the cc field). I just moved it to the 1.2 milestone with the 
>> intention that it would get swept up in a 1.2 cleanup, but that was 
>> apparently not the correct approach, as it was immediately reverted. The 
>> documentation is clear that I can't close it myself. As it stands, this 
>> ticket threatens to linger indefinitely. Can anyone advise on the correct 
>> procedure here?
> 
> Hey Peter. Did you ever end up making an external project for your LDAP 
> patch? If you did, it would be cool to have a link to it in the ticket. I 
> think a third party project is the best place for it. Feel free to close the 
> ticket and point to this thread or say "because jkocherhans said so" in the 
> comments. Pinging django-dev is probably the best way to handle stuff like 
> this.
> 
> I hope you have created or do create a project for it since there is 
> obviously interest. but since it can live outside of Django itself just fine, 
> it probably should. Sorry I didn't reply to you message awhile back [1].
> 
> Thanks,
> Joseph
> 
> [1] http://groups.google.com/group/django-developers/msg/8b354ab4e5d4724b
> 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "Django developers" group.
> To post to this group, send email to django-develop...@googlegroups.com.
> To unsubscribe from this group, send email to 
> django-developers+unsubscr...@googlegroups.com.
> For more options, visit this group at 
> http://groups.google.com/group/django-developers?hl=en.
> 

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To post to this group, send email to django-develop...@googlegroups.com.
To unsubscribe from this group, send email to 
django-developers+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en.

Re: Assertion Woes

[zarusoba]

Howdy FeatherDark,

I've been looking for an answer to this same error, might have found a
"solution" for you - it's worked for me anyway.

Just a quick description of how the problem came about for me - I have
two Django based web sites running under the same Apache HTTP server;
once the HTTP service was started (or restarted) whichever site was
accessed first was fine and would continue to work, but the second one
would fail immediately with the "old_mod" assertion error.

This behaviour seems to fit the theory mentioned by Karen Tracey that
the problem arises because a DLL is being loaded twice... but that
doesn't make the problem go away.

Anyway, on to the bit you really want to know - I was using the latest
pyWin32 build available from the download site (build 214 at the time
of writing), so I uninstalled that and started working backwards
through the previous releases. Luckily I didn't need to go too far -
for me build 212 made the problem go away. Looks like there may be a
bug in the newer package.

So not really a fix, as such, but... Worth a try, anyway, unless you
need the latest build for some particular reason, of course.

Cheers!

On Feb 6, 7:47 am, FeatherDark  wrote:
> So I installed pyWin32 today and all of my Django sites went POOF into
> non-happyland
>
> I was prompted to post so here's a dpaste of just 1 of the errors in
> the apache log
>
> I removed pyWin32 and all my Django woes vanished... other than I
> needed pyWin32
>
> http://dpaste.com/155209/
>
> assert sys.modules[modname] is old_mod

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To post to this group, send email to django-develop...@googlegroups.com.
To unsubscribe from this group, send email to 
django-developers+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en.

Re: Assertion Woes

[zarusoba]

...may have posted this twice...?

Anyway, long story short, try pyWin32 build #212 - worked for me.

Cheers!

On Feb 6, 7:47 am, FeatherDark  wrote:
> So I installed pyWin32 today and all of my Django sites went POOF into
> non-happyland
>
> I was prompted to post so here's a dpaste of just 1 of the errors in
> the apache log
>
> I removed pyWin32 and all my Django woes vanished... other than I
> needed pyWin32
>
> http://dpaste.com/155209/
>
> assert sys.modules[modname] isold_mod

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To post to this group, send email to django-develop...@googlegroups.com.
To unsubscribe from this group, send email to 
django-developers+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en.

Re: Assertion Woes

[zarusoba]

...may have posted this twice...?

Anyway, long story short, try pyWin32 build #212 - worked for me.

Cheers!

On Feb 6, 7:47 am, FeatherDark  wrote:
> So I installed pyWin32 today and all of my Django sites went POOF into
> non-happyland
>
> I was prompted to post so here's a dpaste of just 1 of the errors in
> the apache log
>
> I removed pyWin32 and all my Django woes vanished... other than I
> needed pyWin32
>
> http://dpaste.com/155209/
>
> assert sys.modules[modname] isold_mod

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To post to this group, send email to django-develop...@googlegroups.com.
To unsubscribe from this group, send email to 
django-developers+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en.

Re: dbsettings, and user configurable app settings

[Jared Forsyth]

I'm currently working on a solution to this which I call appsettings, and I
think it addresses many of the concerns raised here. appsettings loads your
module's settings.py in much the same way that contrib.admin loads your
admin.py, and you call appsettings.register (can be used as a decorator) to
tell appsettings that you want those settings managed.
Once registered with appsettings, you access your settings through
appsettings.settings.mymodule.xyz. e.g.

import appsettings
settings = appsettings.settings.mymodule

@ the top of some file.

appsettings uses the database to store your configuration, but it also
gracefully degrades in the absence of a database -- all settings are still
accessible, but are read-only.

Take a look at the project on github for a better example/docs:
http://github.com/jabapyth/django-appsettings

 Jared

On Tue, Mar 2, 2010 at 2:40 PM, Carl Meyer  wrote:

> On Mar 1, 9:40 am, stuff4ash  wrote:
> > I am not necesary advocating magic. But the need for a more robust (or
> > lets say, any) configuration management exists for many.
>
> "Configuration management" is a fuzzy phrase that can mean many things
> to many people. I think it'd be more helpful to focus on specific
> problems and possible solutions. My critique was specifically of the
> suggestion you made for an automatic import of app-level settings.py,
> which introduces magical behavior for (AFAICS) no gain. I've certainly
> had the need for something like dbsettings or livesettings, though
> I've often addressed it with a separate app/model rather than trying
> to shoehorn django.conf.settings into a role it wasn't intended for. I
> also agree that for projects with many reusable apps (which describes
> all of mine), split settings are less headache to manage; I like
> Transifex' conf-directory solution and have proposed it for Pinax.
>
> It's not that the status quo is perfect and no improvement is
> possible; just that specific suggestions with concrete use-cases are
> more useful than handwavy claims about the need for some major new
> subsystem whose purpose and specific features are not clear.
>
> > I am very familiar with your setup, and its the best one in use I have
> > seen. but it has several shortcomings.
>
> So what shortcomings are relevant to you?
>
> > one of the few times that I wished django was more plonish.
>
> Which means what, in this case?
>
> Carl
>
> --
> You received this message because you are subscribed to the Google Groups
> "Django developers" group.
> To post to this group, send email to django-develop...@googlegroups.com.
> To unsubscribe from this group, send email to
> django-developers+unsubscr...@googlegroups.com
> .
> For more options, visit this group at
> http://groups.google.com/group/django-developers?hl=en.
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To post to this group, send email to django-develop...@googlegroups.com.
To unsubscribe from this group, send email to 
django-developers+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en.

jQuery with Django

[Oshadha]

Hia fellas,

I'm kind of new to Django and I'm trying to add some client side
validation to my pre-built user registration form.So I need from the
scratch tutorials (I searched through the net but couldn't fine any
good tutorials), if you guys know any good tutorials please post those
here.

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-develop...@googlegroups.com.
To unsubscribe from this group, send email to 
django-developers+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en.

Re: jQuery with Django

[Karen Tracey]

Please send questions about using Django to django-users.  This list is for
discussions about developing Django itself.

Karen

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To post to this group, send email to django-develop...@googlegroups.com.
To unsubscribe from this group, send email to 
django-developers+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en.

2 small tickets

[Jared Forsyth]

I found some bugs, wrote come patches, submitted some tickets. =) Is that
all that's needed?
The two patches I wrote are *very* small, one is only one char diff...
I guess I just want to know
a) have I done all that's required/suggested, and
b) if so, what's the expected turnaround time for very small bugs w/ a patch
attached?
for reference, the tickets: http://code.djangoproject.com/ticket/12974,
http://code.djangoproject.com/ticket/12972

thanks,
Jared

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To post to this group, send email to django-develop...@googlegroups.com.
To unsubscribe from this group, send email to 
django-developers+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en.

Re: 2 small tickets

[Gert Van Gool]

I believe you still need test cases for both tickets.

-- Gert

Mobile: +32 498725202
Web: http://gert.selentic.net



On Wed, Mar 3, 2010 at 08:41, Jared Forsyth  wrote:
> I found some bugs, wrote come patches, submitted some tickets. =) Is that
> all that's needed?
> The two patches I wrote are very small, one is only one char diff...
> I guess I just want to know
> a) have I done all that's required/suggested, and
> b) if so, what's the expected turnaround time for very small bugs w/ a patch
> attached?
> for reference, the
> tickets: http://code.djangoproject.com/ticket/12974, http://code.djangoproject.com/ticket/12972
> thanks,
> Jared
>
> --
> You received this message because you are subscribed to the Google Groups
> "Django developers" group.
> To post to this group, send email to django-develop...@googlegroups.com.
> To unsubscribe from this group, send email to
> django-developers+unsubscr...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/django-developers?hl=en.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To post to this group, send email to django-develop...@googlegroups.com.
To unsubscribe from this group, send email to 
django-developers+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en.