Re: [Django] #14332: manage testserver and manage runserver should have similiar address:port options

[Django]

#14332: manage testserver and manage runserver should have similiar address:port
options
-+-
 Reporter:  wildfire@…   |Owner:  fheinz
 Type:  New feature  |   Status:  closed
Component:  Core (Management |  Version:  1.2
  commands)  |   Resolution:  wontfix
 Severity:  Normal   | Triage Stage:  Design
 Keywords:  runserver,   |  decision needed
  testserver |  Needs documentation:  0
Has patch:  1|  Patch needs improvement:  1
  Needs tests:  0|UI/UX:  0
Easy pickings:  0|
-+-
Changes (by aaugustin):

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


Comment:

 runserver is about 1x more used that testserver.

 I'm -1 on making changes to runserver (especially changes towards a longer
 syntax) only to provide consistency with an obscure command few developers
 use.

 I'm not very excited either by special casing the first argument to
 testserver to magically determine if it's a binding spec or a fixture
 name, such hacks backfire too often.

 Please take it to django-developers to see if there's actual demand for
 changes, the current situation doesn't seem horrific to me. testserver
 needs arguments, runserver doesn't, that's it.

-- 
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] #14332: manage testserver and manage runserver should have similiar address:port options

[Django]

#14332: manage testserver and manage runserver should have similiar address:port
options
-+-
   Reporter: |Owner:  fheinz
  wildfire@… |   Status:  reopened
   Type:  New|Component:  Core (Management
  feature|  commands)
  Milestone: | Severity:  Normal
Version:  1.2| Keywords:  runserver, testserver
 Resolution: |Has patch:  1
   Triage Stage:  Design |  Needs tests:  0
  decision needed|
Needs documentation:  0  |
Patch needs improvement:  1  |
-+-
Changes (by graham_king):

 * keywords:   => runserver, testserver
 * type:   => New feature
 * 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] #14332: manage testserver and manage runserver should have similiar address:port options

[Django]

#14332: manage testserver and manage runserver should have similiar address:port
options
-+--
  Reporter:  wildf...@progsoc.org| Owner:  fheinz
Status:  reopened| Milestone:
 Component:  django-admin.py |   Version:  1.2   
Resolution:  |  Keywords:
 Stage:  Design decision needed  | Has_patch:  1 
Needs_docs:  0   |   Needs_tests:  0 
Needs_better_patch:  1   |  
-+--
Comment (by fheinz):

 I agree that "there should be one obvious way to do it" is a Good Thing.
 What we have now is "there are two incompatible ways to do it, and you
 must choose the right one or it won't work".

 The change you propose would give us indeed one way to do it, at the price
 of breaking backwards compatibility for *both* runserver and testserver.

 I know that the current implementation doesn't work if you absolutely need
 to give a fixture a numerical name without extension, and put it first in
 the list of fixtures. That is an unlikely use case, and the --addrport
 option saves the day anyway.

 The way I see it, of the three option that are on the table right now
 (providing a homogeneous interface that breaks backwards compatibility,
 providing a homogeneous but redundant user interface without breaking
 backwards compatibility, and leaving things as they are with an redundant
 and inconsistent interface), the patch implements the least objectionable
 one.

-- 
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] #14332: manage testserver and manage runserver should have similiar address:port options

[Django]

#14332: manage testserver and manage runserver should have similiar address:port
options
-+--
  Reporter:  wildf...@progsoc.org| Owner:  fheinz
Status:  reopened| Milestone:
 Component:  django-admin.py |   Version:  1.2   
Resolution:  |  Keywords:
 Stage:  Design decision needed  | Has_patch:  1 
Needs_docs:  0   |   Needs_tests:  0 
Needs_better_patch:  1   |  
-+--
Changes (by lrekucki):

  * needs_better_patch:  0 => 1
  * stage:  Accepted => Design decision needed

Comment:

 I'm against doing it this way. I see no value for having ``--addrport``
 option for runserver. Duplicating functionality is a bad thing, imho (You
 know, "there should be one obvious way to do it", etc.). A minor backwards
 compatibility issue is that someone can have a fixture named "1000", which
 will now get interpreted as port number.

 If I was to propose something, it would be deprectating ``--addrport`` and
 runserver's positional syntax in favour of ``--host`` and ``--port``
 options. That would at least be consistent with most UNIX tools, but I'm
 generally -0 on changing anything here.

-- 
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] #14332: manage testserver and manage runserver should have similiar address:port options

[Django]

#14332: manage testserver and manage runserver should have similiar address:port
options
---+
  Reporter:  wildf...@progsoc.org  | Owner:  fheinz
Status:  reopened  | Milestone:
 Component:  django-admin.py   |   Version:  1.2   
Resolution:|  Keywords:
 Stage:  Accepted  | Has_patch:  1 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Changes (by ramiro):

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

Comment:

 Reopening. The ''fixed'' status is set when a commit lands in the code
 repository.

-- 
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] #14332: manage testserver and manage runserver should have similiar address:port options

[Django]

#14332: manage testserver and manage runserver should have similiar address:port
options
---+
  Reporter:  wildf...@progsoc.org  | Owner:  fheinz
Status:  closed| Milestone:
 Component:  django-admin.py   |   Version:  1.2   
Resolution:  fixed |  Keywords:
 Stage:  Accepted  | Has_patch:  1 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Changes (by fheinz):

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

Comment:

 14332

-- 
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] #14332: manage testserver and manage runserver should have similiar address:port options

[Django]

#14332: manage testserver and manage runserver should have similiar address:port
options
---+
  Reporter:  wildf...@progsoc.org  | Owner:  fheinz
Status:  assigned  | Milestone:
 Component:  django-admin.py   |   Version:  1.2   
Resolution:|  Keywords:
 Stage:  Accepted  | Has_patch:  1 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Changes (by fheinz):

  * status:  new => assigned
  * has_patch:  0 => 1
  * stage:  Unreviewed => Accepted

Comment:

 The attached patch implements and documents the requested feature. For
 backwards compatibility, both runserver and testserver now accept both
 ways of specifying the IP address.

-- 
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] #14332: manage testserver and manage runserver should have similiar address:port options

[Django]

#14332: manage testserver and manage runserver should have similiar address:port
options
---+
  Reporter:  wildf...@progsoc.org  | Owner:  fheinz
Status:  new   | Milestone:
 Component:  django-admin.py   |   Version:  1.2   
Resolution:|  Keywords:
 Stage:  Unreviewed| Has_patch:  0 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Changes (by fheinz):

  * owner:  nobody => fheinz

-- 
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] #14332: manage testserver and manage runserver should have similiar address:port options

[Django]

#14332: manage testserver and manage runserver should have similiar address:port
options
---+
  Reporter:  wildf...@progsoc.org  | Owner:  nobody
Status:  new   | Milestone:
 Component:  django-admin.py   |   Version:  1.2   
Resolution:|  Keywords:
 Stage:  Unreviewed| Has_patch:  0 
Needs_docs:  0 |   Needs_tests:  0 
Needs_better_patch:  0 |  
---+
Changes (by gabrielhurley):

  * needs_better_patch:  => 0
  * component:  Uncategorized => django-admin.py
  * needs_tests:  => 0
  * needs_docs:  => 0

-- 
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.

[Django] #14332: manage testserver and manage runserver should have similiar address:port options

[Django]

#14332: manage testserver and manage runserver should have similiar address:port
options
--+-
 Reporter:  wildf...@progsoc.org  |   Owner:  nobody
   Status:  new   |   Milestone:
Component:  Uncategorized | Version:  1.2   
 Keywords:|   Stage:  Unreviewed
Has_patch:  0 |  
--+-
 Hi,

 $ ./manage.py runserver -h
 Usage: ./manage.py runserver [options] [optional port number, or
 ipaddr:port]

 Starts a lightweight Web server for development.

 [...]

 $ ./manage.py testserver -h
 Usage: ./manage.py testserver [options] [fixture ...]


 In order to get the testserver to listen on a particular port, you need to
 specify the --addrport option.

 It would be useful if that option was also understood by the normal
 runserver command. Or if testserver interpreted a bare port number as the
 runserver command does.

-- 
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.