On 16 September 2016 at 05:38, Wes Turner wrote:
> You can install bash on windows. (GoW, Cygwin, Ming), but Docker (and, soon,
> runC OCP 1.0) is probably your best bet for maximum compatibility with most
> {python, open source} tutorials.
Wes, none of these are beginner friendly recommendations
You can install bash on windows. (GoW, Cygwin, Ming), but Docker (and,
soon, runC OCP 1.0) is probably your best bet for maximum compatibility
with most {python, open source} tutorials. Installing the code as non-root
is a good idea (e.g. with a .zip or a .tar.gz or a Python .whl wheel)
I think t
On Thu, Sep 15, 2016, at 01:53 PM, Wes Turner wrote:
> Shell commands can/could/should be clearly indicated with a '$'
> prefix:
>
> $ python -m pip install numpy
That's a common convention, but:
- It comes from POSIX platforms where the default prompt ends in $. The
default prompt in Windo
On Tuesday, September 13, 2016, Mills, Ryan
wrote:
> I just recently downloaded Python 3.5 and cannot seem to install any
> packages like Numpy, etc. I have tried all the instructions on the website
> and keep getting errors:
>
>
>
> For example, when I type “python –m pip install Numpy” it retu
Useful banking/finance Python resources:
- https://pypi.python.org/pypi/ofxparse
- https://wrdrd.com/docs/consulting/investing#quantopian
- Places that have some Python in their stack:
- JP Morgan
- Bank of America Merrill Lynch
- Quantopian
- qgrid, zipline, pyfolio, ...
On Thursday, S
On 15 September 2016 at 01:31, Paul Moore wrote:
> On 13 September 2016 at 23:55, Donald Stufft wrote:
>> Perhaps a better idea would be to add some smarts to the REPL (but not to
>> Python itself) that would detect something like:
>>
> pip install
>>
>> And print a better error message that
On Wed, Sep 14, 2016, at 04:31 PM, Paul Moore wrote:
> Of course, it doesn't solve the problem of a user who doesn't know
> what a "shell prompt" is...
Especially since the interactive Python interpreter is also a shell
prompt. The title of an IDLE window on my system is "Python 3.5.2 Shell"
;-).
On 13 September 2016 at 23:55, Donald Stufft wrote:
> Perhaps a better idea would be to add some smarts to the REPL (but not to
> Python itself) that would detect something like:
>
pip install
>
> And print a better error message that gives a better indication about what’s
> gone wrong besi
On 14 September 2016 at 22:27, Marius Gedminas wrote:
> On Tue, Sep 13, 2016 at 06:55:49PM -0400, Donald Stufft wrote:
>> >>> pip install
>>
>> And print a better error message that gives a better indication about what’s
>> gone wrong besides a SyntaxError?
>
> This way you could also make
>
>
On Tue, Sep 13, 2016 at 06:55:49PM -0400, Donald Stufft wrote:
> >>> pip install
>
> And print a better error message that gives a better indication about what’s
> gone wrong besides a SyntaxError?
This way you could also make
>>> exit
work like people expect it to work, without the ().
Mar
On 14 September 2016 at 21:43, Donald Stufft wrote:
>
>> On Sep 13, 2016, at 7:06 PM, Steve Dower wrote:
>>
>> This is exactly the argument I was expecting when I said "those who want it
>> to be perfect in every scenario"
>
> FWIW I don’t have a strong feeling on whether we should add it or not
> On Sep 13, 2016, at 7:06 PM, Steve Dower wrote:
>
> This is exactly the argument I was expecting when I said "those who want it
> to be perfect in every scenario"
FWIW I don’t have a strong feeling on whether we should add it or not. I
haven’t been a beginner in a long time and I am not ve
On 14 September 2016 at 18:02, Paul Moore wrote:
> On 13 September 2016 at 23:55, Donald Stufft wrote:
>> The 90% case works when it’s *only* pure python and there’s no
>> upgrading/downgrading involved, however you can’t control whether there are
>> going to be upgrades/downgrades or not when
On 13 September 2016 at 23:55, Donald Stufft wrote:
> The 90% case works when it’s *only* pure python and there’s no
> upgrading/downgrading involved, however you can’t control whether there are
> going to be upgrades/downgrades or not when dependencies are in play because
> of ==, >=, >, <, <=
On 14 September 2016 at 08:55, Donald Stufft wrote:
> Another problem, particularly on Windows, is going to be stuff like:
>
import someclibrary
pip.install(“thing”) # Implicitly upgrades someclibrary
>
> In this case, this would explode because Python will have the
> someclibrary.dll
On Tue, Sep 13, 2016 at 3:55 PM, Donald Stufft wrote:
> Perhaps a better idea would be to add some smarts to the REPL (but not to
> Python itself) that would detect something like:
>
pip install
>
> And print a better error message that gives a better indication about what’s
> gone wrong b
On 13Sep2016 1559, Matthew Brett wrote:
Perhaps a better idea would be to add some smarts to the REPL (but not to
Python itself) that would detect something like:
pip install
And print a better error message that gives a better indication about what’s
gone wrong besides a SyntaxError?
I w
On 13Sep2016 1555, Donald Stufft wrote:
On Sep 13, 2016, at 6:41 PM, Steve Dower wrote:
I think it's one of these things where we should suck it up and let the 90%
case work fine, then display a big fat warning if anything weird may have
happened and let users sort it out themselves.
I a
Hi,
On Tue, Sep 13, 2016 at 3:55 PM, Donald Stufft wrote:
>
>> On Sep 13, 2016, at 6:41 PM, Steve Dower wrote:
>>
>> I think it's one of these things where we should suck it up and let the 90%
>> case work fine, then display a big fat warning if anything weird may have
>> happened and let user
> On Sep 13, 2016, at 6:41 PM, Steve Dower wrote:
>
> I think it's one of these things where we should suck it up and let the 90%
> case work fine, then display a big fat warning if anything weird may have
> happened and let users sort it out themselves.
I am unsure. One of the really egregi
On 2016-09-13 23:00:25 +0100 (+0100), Paul Moore wrote:
[...]
> And things get significantly worse if we allow upgrades from the
> Python prompt rather than just installs (e.g., if you have already
> imported something from the old version and then upgrade).
[...]
If you need it, and of course onl
On 13Sep2016 1500, Paul Moore wrote:
On 13 September 2016 at 21:12, Thomas Kluyver wrote:
One thing I'd quite like to see Python grow is a standard function to
install packages from inside Python.
That's not too hard in principle - pip.main(['install', package]) is
basically all you'd need (m
On 13 September 2016 at 19:00, Paul Moore wrote:
> [...]
>
> I'm not honestly sure how big the "installing while a process is
> running" issue would be - I did a few simple experiments and couldn't
> immediately trigger weirdness, but I believe it can happen. And things
> get significantly worse
On 13 September 2016 at 21:12, Thomas Kluyver wrote:
> One thing I'd quite like to see Python grow is a standard function to
> install packages from inside Python.
That's not too hard in principle - pip.main(['install', package]) is
basically all you'd need (modulo various design details, and wra
>
> I think Ryan may have typed that command at a Python prompt rather than
>> a system command prompt. Unfortunately the distinction often isn't clear
>> in examples, because the experienced developers writing the instructions
>> are used to guessing which commands are Python and which are system
On 13Sep2016 1312, Thomas Kluyver wrote:
On Tue, Sep 13, 2016, at 08:39 PM, Steve Dower wrote:
It would help if you could post the full error output (sanitizing
paths if needed). But you may just need to upgrade pip (python -m
install -U pip).
I think Ryan may have typed that command at a Pyth
On Tue, Sep 13, 2016, at 08:39 PM, Steve Dower wrote:
> It would help if you could post the full error output (sanitizing
> paths if needed). But you may just need to upgrade pip (python -m
> install -U pip).
I think Ryan may have typed that command at a Python prompt rather than
a system command
It would help if you could post the full error output (sanitizing paths if
needed). But you may just need to upgrade pip (python -m install -U pip).
Knowing exactly where the syntax error is coming from will help us figure out
which package has the problem. There are at least three involved here
On 13 September 2016 at 15:48, Mills, Ryan
wrote:
> Do I use the Python IDLE Shell?
No, pip is a command line utility so you should go to the command prompt
and run "py -m pip install numpy" (I assume you're on Windows - on Unix
you'd need to run the appropriate python command).
Paul
_
29 matches
Mail list logo
