Hi Ramiro, On Tuesday, July 11, 2017 at 10:55:38 PM UTC+2, Ramiro Morales wrote: > > - I run django-admin.py startproject and I get an error message stating > django-admin.py isn't a known command >
FWIW django-admin.py shouldn't be used any more nowadays -- my latest changes should install django-admin.exe (https://github.com/django/django/blob/d7881d2020a7337ed128eeef811ef1c1e549b481/setup.py#L48). That said, yes it is a problem that the location of those commands is probably not on any executable path in windows. For fairness' sake, the same applies for `pip install --user` on linux -- although not that much of a problem since most users just use sudo to install 🙈. - I run django-admin.py startproject as directed and a text editor window > opens containing Python code (source code of django-admin.py). > LMAO *scnr*, does the same actually apply if the exe variant is used? I am asking because the tutorial clearly mentions django-admin (https://docs.djangoproject.com/en/1.11/intro/tutorial01/#creating-a-project) without the .py suffix. > - I run python django-admn.py startproject and I get an error message > stating Python isn't a known command > See above, if django-admin is used instead of django-admin.py there should be no problems > django-admin.py startproject foo > That seems already to be the case (minus the .py which is no longer needed). manage.py might still be a problem though. > - It forces users to type in "Unixisms" like `./manage.py` or `mkdir > ~/.virtualenvs` > +1, there are certainly still unix variants of commands there which should be changed to something accommodating for all platforms. - Is incompatible with venv (another useful tool, also new in Python 3.3 as > part of the standard library) and forces the document to divert Windows > users so they install and use virtualenv, putting them in the strange > situation of having to do that because then they can activate the virtual > env by using the Unix shell-specific `source` builtin instead of using > native scripts activate.bat or activate.ps1 > I think (tm) this is not the same for django-admin.exe which afaik supports venvs (in the sense that it will choose the venv python over the default installed python -- do not ask me how and I might also be wrong here). > Another change proposed by the PR is the addition of a custom Sphinx > directive that modifies the UI of CLI example text boxes so they can show a > native prompt and native command line input as it should actually be typed > by the user either on Unix-based shells or the Windows command prompt > through a tabbed interface. > + 0/1 -- I'll happily merge but I do not care enough about windows to push it forward. Cheers, Florian -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/0745ff1e-b76c-44e1-a4b0-f4bcf52fbd21%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
