Re: [Django] #12231: The project path is incorrectly build, it wipe the namespace

[Django]

#12231: The project path is incorrectly build, it wipe the namespace
--+--
 Reporter:  mleduc|Owner:  nobody
 Type:  Bug   |   Status:  closed
Component:  Core (Other)  |  Version:  master
 Severity:  Normal|   Resolution:  worksforme
 Keywords:  package   | Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  1
Easy pickings:  0 |UI/UX:  0
--+--
Changes (by claudep):

 * status:  new => closed
 * resolution:   => worksforme


Comment:

 Most of this code is now obsolete. Reopen with current code references if
 still valid.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [Django] #12231: The project path is incorrectly build, it wipe the namespace

[Django]

#12231: The project path is incorrectly build, it wipe the namespace
+
   Reporter:  mleduc|Owner:  nobody
   Type:  Bug   |   Status:  new
  Milestone:|Component:  Core (Other)
Version:  SVN   | Severity:  Normal
 Resolution:| Keywords:  package
   Triage Stage:  Accepted  |Has patch:  1
Needs documentation:  0 |  Needs tests:  0
Patch needs improvement:  1 |
+
Changes (by mattmcc):

 * type:   => Bug
 * severity:   => Normal


-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

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

Re: [Django] #12231: The project path is incorrectly build, it wipe the namespace

[Django]

#12231: The project path is incorrectly build, it wipe the namespace
-+--
  Reporter:  mleduc  | Owner:  nobody 
Status:  new | Milestone: 
 Component:  Core framework  |   Version:  SVN
Resolution:  |  Keywords:  package
 Stage:  Accepted| Has_patch:  1  
Needs_docs:  0   |   Needs_tests:  0  
Needs_better_patch:  1   |  
-+--
Changes (by ubernostrum):

  * milestone:  1.2 =>

Comment:

 1.2 is feature-frozen, moving this feature request off the milestone.

 (and egg support is most definitely a feature request)

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

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

Re: [Django] #12231: The project path is incorrectly build, it wipe the namespace

[Django]

#12231: The project path is incorrectly build, it wipe the namespace
-+--
  Reporter:  mleduc  | Owner:  nobody 
Status:  new | Milestone:  1.2
 Component:  Core framework  |   Version:  SVN
Resolution:  |  Keywords:  package
 Stage:  Accepted| Has_patch:  1  
Needs_docs:  0   |   Needs_tests:  0  
Needs_better_patch:  1   |  
-+--
Changes (by russellm):

  * needs_better_patch:  0 => 1
  * stage:  Unreviewed => Accepted

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

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

Re: [Django] #12231: The project path is incorrectly build, it wipe the namespace

[Django]

#12231: The project path is incorrectly build, it wipe the namespace
-+--
  Reporter:  mleduc  | Owner:  nobody 
Status:  new | Milestone:  1.2
 Component:  Core framework  |   Version:  SVN
Resolution:  |  Keywords:  package
 Stage:  Unreviewed  | Has_patch:  1  
Needs_docs:  0   |   Needs_tests:  0  
Needs_better_patch:  0   |  
-+--
Changes (by Alex):

  * needs_better_patch:  => 0
  * needs_tests:  => 0
  * needs_docs:  => 0

Old description:

> If by example your django is in an egg like
>
> my.site.project
>
> If you call the django core execution manager with:
>
> mod = __import__('my.site.project')
> django.core.management.execute_manager(mod)
>
> Your project will not be found cause the django core is declaring the
> main DJANGO_SETTINGS_MODULE with:
>
> django.core.management.__init__:
> ...
> project_directory, settings_filename = os.path.split(p)
> if project_directory == os.curdir or not project_directory:
>project_directory = os.getcwd()
> project_name = os.path.basename(project_directory)
> ...
> os.environ['DJANGO_SETTINGS_MODULE = '%s.%s' % (project_name,
> settings_name)
> ...
>
> The project_name variable represent only the first level of the project
> egg. It could not work with a multilevel package and we now have to use
> the variable 'original_settings_path' which is just optional.
>
> The solution maybe to use the special __package__ variable of the
> settings_mod module.
>
> I attach a patch with this ticket whick correct this problem.

New description:

 If by example your django is in an egg like
 {{{
 my.site.project
 }}}
 If you call the django core execution manager with:
 {{{
 mod = __import__('my.site.project')
 django.core.management.execute_manager(mod)
 }}}
 Your project will not be found cause the django core is declaring the main
 DJANGO_SETTINGS_MODULE with:

 django.core.management.__init__:
 {{{
 ...
 project_directory, settings_filename = os.path.split(p)
 if project_directory == os.curdir or not project_directory:
project_directory = os.getcwd()
 project_name = os.path.basename(project_directory)
 ...
 os.environ['DJANGO_SETTINGS_MODULE = '%s.%s' % (project_name,
 settings_name)
 ...
 }}}
 The project_name variable represent only the first level of the project
 egg. It could not work with a multilevel package and we now have to use
 the variable 'original_settings_path' which is just optional.

 The solution maybe to use the special __package__ variable of the
 settings_mod module.

 I attach a patch with this ticket whick correct this problem.

Comment:

 Please use preview.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

--

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

[Django] #12231: The project path is incorrectly build, it wipe the namespace

[Django]

#12231: The project path is incorrectly build, it wipe the namespace
+---
 Reporter:  mleduc  |   Owner:  nobody
   Status:  new |   Milestone:  1.2   
Component:  Core framework  | Version:  SVN   
 Keywords:  package |   Stage:  Unreviewed
Has_patch:  1   |  
+---
 If by example your django is in an egg like

 my.site.project

 If you call the django core execution manager with:

 mod = __import__('my.site.project')
 django.core.management.execute_manager(mod)

 Your project will not be found cause the django core is declaring the main
 DJANGO_SETTINGS_MODULE with:

 django.core.management.__init__:
 ...
 project_directory, settings_filename = os.path.split(p)
 if project_directory == os.curdir or not project_directory:
project_directory = os.getcwd()
 project_name = os.path.basename(project_directory)
 ...
 os.environ['DJANGO_SETTINGS_MODULE = '%s.%s' % (project_name,
 settings_name)
 ...

 The project_name variable represent only the first level of the project
 egg. It could not work with a multilevel package and we now have to use
 the variable 'original_settings_path' which is just optional.

 The solution maybe to use the special __package__ variable of the
 settings_mod module.

 I attach a patch with this ticket whick correct this problem.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

--

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