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 14 September 2016 at 14:13, Nick Coghlan wrote:
> On 14 September 2016 at 07:00, Glyph Lefkowitz
> wrote:
>> On Sep 13, 2016, at 12:58 PM, Matthew Brett wrote:
>>> I was reflecting on the detail of putting pip user bin directories on
>>> the user's path, and was then thinking of making a tin
On 14 September 2016 at 07:00, Glyph Lefkowitz wrote:
> On Sep 13, 2016, at 12:58 PM, Matthew Brett wrote:
>> I was reflecting on the detail of putting pip user bin directories on
>> the user's path, and was then thinking of making a tiny pip package
>> like this:
>>
>> pip install pip_user_confi
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
Gaaa, I should have stayed mum. Missed referring to the develop egg
too, as Leonardo pointed out.
Thanks.
Jim
On Tue, Sep 13, 2016 at 5:18 PM, Fred Drake wrote:
> On Tue, Sep 13, 2016 at 4:44 PM, Jim Fulton wrote:
>> You're missing:
>>
>>develop .
>>
>> to have buildout create and include
On Tue, Sep 13, 2016 at 4:44 PM, Jim Fulton wrote:
> You're missing:
>
>develop .
>
> to have buildout create and include a develop egg using the current
> directory with it's dependencies.
Ahem.
develop = .
-Fred
--
Fred L. Drake, Jr.
"A storm broke loose in my mind." --Albe
> On Sep 13, 2016, at 12:58 PM, Matthew Brett wrote:
>
> Hi,
>
> I was reflecting on the detail of putting pip user bin directories on
> the user's path, and was then thinking of making a tiny pip package
> like this:
>
> pip install pip_user_config
> python -m pip_user_config
>
> where the l
On Tue, Sep 13, 2016 at 4:07 PM, Alessandro Dentella wrote:
> Hi,
>
>
> I just migrated from buildout 1.7 to buildout 2.5. In this migration I
> stopped using a recipe that created a virtualenv as a part of
> buildout and I now use an external (basic) virtualenv to calll
> bootrap, so I can't comp
Hi Sandro,
I don't know what your previous setup did, but in your current setup, your
`buildout.cfg` is not configured to take your `setup.py` into account in
any way.
In the `eggs` setting, only `django`, `ipython` and `django-settings` are
mentioned. To take your `setup.py` into account it shou
Hi,
I just migrated from buildout 1.7 to buildout 2.5. In this migration I
stopped using a recipe that created a virtualenv as a part of
buildout and I now use an external (basic) virtualenv to calll
bootrap, so I can't compare the two configuration in a strict way.
My problem is that now it see
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
Hi,
I was reflecting on the detail of putting pip user bin directories on
the user's path, and was then thinking of making a tiny pip package
like this:
pip install pip_user_config
python -m pip_user_config
where the latter would cleverly insert the user bin directory into the
user's configurati
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
_
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 returns a Syntax
Error. I am completely new to Python so I must be
25 matches
Mail list logo
