Re: [Django] #30003: Manage.py entry point

[Django]

#30003: Manage.py entry point
-+-
 Reporter:  James Pic|Owner:  nobody
 Type:   |   Status:  closed
  Cleanup/optimization   |
Component:  Core (Management |  Version:  2.1
  commands)  |
 Severity:  Normal   |   Resolution:  fixed
 Keywords:   | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Tim Graham ):

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


Comment:

 In [changeset:"9453bc77f4968dc3a8167eadbf9775953812" 9453bc7]:
 {{{
 #!CommitTicketReference repository=""
 revision="9453bc77f4968dc3a8167eadbf9775953812"
 Fixed #30003 -- Added usable entry point in default manage.py.
 }}}

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/062.e0a0218c1cdb6421ae59bda4125c02c3%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #30003: Manage.py entry point

[Django]

#30003: Manage.py entry point
-+-
 Reporter:  James Pic|Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  Core (Management |  Version:  2.1
  commands)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Carlton Gibson):

 * stage:  Accepted => Ready for checkin


-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/062.d0ccd3bf4b205c85bb2f98806d3c9b7c%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #30003: Manage.py entry point

[Django]

#30003: Manage.py entry point
-+-
 Reporter:  James Pic|Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  Core (Management |  Version:  2.1
  commands)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:  Accepted
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Carlton Gibson):

 * stage:  Unreviewed => Accepted


Comment:

 I'm going to Accept this pending any objections in review.

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/062.4fa91ea497a8f3ae1bc1b70f9da8d49b%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #30003: Manage.py entry point

[Django]

#30003: Manage.py entry point
-+-
 Reporter:  James Pic|Owner:  nobody
 Type:   |   Status:  new
  Cleanup/optimization   |
Component:  Core (Management |  Version:  2.1
  commands)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:
 |  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Carlton Gibson):

 * type:  New feature => Cleanup/optimization


Comment:

 Hi James,

 You basically mean you want to reference `yourproject.manage:main` in your
 own `setup.py` — is that correct?

 I would say, "just use a custom project template" but the patch itself is
 small/unobjectionable.

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/062.4b38cdc6f3a7204784f0bc6a0f781a20%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #30003: Manage.py entry point

[Django]

#30003: Manage.py entry point
-+-
 Reporter:  James Pic|Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Core (Management |  Version:  2.1
  commands)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:
 |  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Description changed by James Pic:

Old description:

> Currently, manage.py-tpl executes in an
> {{{
> if __name__ == '__main__':
> }}}
>  block.
>
> While this might work when declaring manage.py as script in setup.py, a
> popular convention is to use the entry_point feature of setup.py.
>
> To add support for entry_point in manage.py-tpl we only need to move the
> code from the if block into a new function ie. main() and call in it in
> the if-block.
>
> Then, manage.py-tlp will also work as entry_point with
> yourproject.manage:main and using manage.py as script will also still
> work.
>
> This removes a manual effort every time a project is used by a follower
> of the entry_point convention, without causing any issue for regular
> users.

New description:

 Currently, manage.py-tpl executes in an
 {{{
 if __name__ == '__main__':
 }}}
  block.

 While this might work when declaring manage.py as script in setup.py, a
 popular convention is to use the console_scripts entry_point in setup.py
 to define commands.

 For manage.py-tpl to support console_scripts entry_point we only need to
 move the code from the if block into a new function ie. main(), then call
 main() it in the if-block.

 Then, manage.py-tlp will also work as console_scripts entry_point with
 yourproject.manage:main, and using manage.py as script will also still
 work.

 This removes a manual effort every time a project defines a
 console_scripts entry_point for the management CLI, without having to set
 DJANGO_SETTINGS_MODULE.

--

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/062.18ebc486d82297b18fc6b5745b2fc83c%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #30003: Manage.py entry point

[Django]

#30003: Manage.py entry point
-+-
 Reporter:  James Pic|Owner:  nobody
 Type:  New feature  |   Status:  new
Component:  Core (Management |  Version:  2.1
  commands)  |
 Severity:  Normal   |   Resolution:
 Keywords:   | Triage Stage:
 |  Unreviewed
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by James Pic):

 * cc: James Pic (added)
 * has_patch:  0 => 1
 * type:  Uncategorized => New feature


Old description:

> Currently, manage.py-tpl executes in an
> {{{
> if __name__ == '__main__':
> }}}
>  block.
>
> While this might work when declaring manage.py as script in setup.py, a
> popular convention is to use the entry_point feature of setup.py.
>
> To add support for entry_point in manage.py-tpl we only need to move the
> code from the if block into a new function ie. main() and call in it in
> the if-block.
>
> Then, manage.py-tlp will also work as entry_point with
> yourproject.manage:main and using manage.py as script will also still
> work.

New description:

 Currently, manage.py-tpl executes in an
 {{{
 if __name__ == '__main__':
 }}}
  block.

 While this might work when declaring manage.py as script in setup.py, a
 popular convention is to use the entry_point feature of setup.py.

 To add support for entry_point in manage.py-tpl we only need to move the
 code from the if block into a new function ie. main() and call in it in
 the if-block.

 Then, manage.py-tlp will also work as entry_point with
 yourproject.manage:main and using manage.py as script will also still
 work.

 This removes a manual effort every time a project is used by a follower of
 the entry_point convention, without causing any issue for regular users.

--

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/062.98611c24fefc25fe3599d940dd7e58b5%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.