On 2016-08-27 15:23, c...@zip.com.au wrote:
On 27Aug2016 09:06, Alex Kleider wrote:
On 2016-08-26 21:58, Ben Finney wrote:
Alex Kleider writes:
Am I to assume that if I have activated a virtualenv, then the
following shebang
#!/usr/bin/env python
will use the python specified in the venv/bin
On 27Aug2016 09:06, Alex Kleider wrote:
On 2016-08-26 21:58, Ben Finney wrote:
Alex Kleider writes:
Am I to assume that if I have activated a virtualenv, then the
following shebang
#!/usr/bin/env python
will use the python specified in the venv/bin/?
Yes, the purpose of that shebang is to t
On 2016-08-26 21:58, Ben Finney wrote:
Alex Kleider writes:
Am I to assume that if I have activated a virtualenv, then the
following shebang
#!/usr/bin/env python
will use the python specified in the venv/bin/?
Yes, the purpose of that shebang is to tell the OS that *whichever*
‘python’ comm
Alex Kleider writes:
> Am I to assume that if I have activated a virtualenv, then the
> following shebang
> #!/usr/bin/env python
> will use the python specified in the venv/bin/?
Yes, the purpose of that shebang is to tell the OS that *whichever*
‘python’ command is found first, is the one to u
On 2016-08-25 21:27, Ben Finney wrote:
That's exactly the wrong thing to do. Your shebang line should *not*
assume a custom location of the Python interpreter.
It's the responsibility of the operating system or virtualenv to
provide
the Python interpreter command in a standard place.
Instead
Alex Kleider writes:
> I'm still struggling with what is the best way to set up a project
> directory.
One thing to learn is that there's no one right way that is universally
applicable.
In particular, you are asking about *social* conventions here. These are
prone to change and negotiation and
I'm still struggling with what is the best way to set up a project
directory.
All the sources I've read seem to agree that one should have a top
level project directory under which one might expect to find the
following:
COPYING.txt # or LICENSE.txt
README.rst
setup.py
and if the pr
On Wed, Jan 29, 2014 at 10:45:53PM +0530, Reuben wrote:
> Hi,
>
> Do we need to follow any particular directory structure for creating any
> New projects or could we just randomly create a folder containing the
> script of interest?
Yes and no.
If all you're doing is writing a single file script
Hi,
Do we need to follow any particular directory structure for creating any
New projects or could we just randomly create a folder containing the
script of interest?
Regards,
Reuben
___
Tutor maillist - Tutor@python.org
To unsubscribe or change subsc
