Re: Beta release of pip version 10

[Paul Moore]

Unfortunately there was an issue in one of the release files (the CA
Certificate bundle contained Windows line endings instead of Unix line
endings) which caused crashes on older versions of MacOS. As a result
we have just released 10.0.0b2, fixing this issue.

Anyone on older MacOS versions who have had problems with the 10.0.0b1
release should upgrade to 10.0.0b2.

Thanks,
Paul

On 31 March 2018 at 12:11, Paul Moore  wrote:
> On behalf of the PyPA, I am pleased to announce that a beta release
> 10.0.0b1 of pip has just been released for testing by the community.
> We're planning on a final release in 2 weeks' time, over the weekend
> of 14/15 April.
>
> To install pip 10.0.0.b1, you can run
>
> python -m pip install --upgrade --pre pip
>
> (obviously, you should not do this in a production environment!)
>
> We would be grateful for all testing that users could do, to ensure
> that when pip 10 is released it's as solid as we can make it.
>
> Highlights of the new release:
>
> * Python 2.6 is no longer supported - if you need pip on Python 2.6,
> you should stay on pip 9, which is the last version to support Python
> 2.6.
> * Support for PEP 518, which allows projects to specify what packages
> they require in order to build from source. (PEP 518 support is
> currently limited, with full support coming in future versions - see
> the documentation for details).
> * Significant improvements in Unicode handling for non-ASCII locales on 
> Windows.
> * A new "pip config" command.
> * The default upgrade strategy has become "only-if-needed"
> * Many bug fixes and minor improvements.
>
> In addition, the previously announced reorganisation of pip's
> internals has now taken place. Unless you are the author of code that
> imports the pip module (or a user of such code), this change will not
> affect you. If you are, please report the issue to the author of the
> affected code (refer them to
> https://mail.python.org/pipermail/distutils-sig/2017-October/031642.html
> for the details of the announcement).
>
> Please note that there is a minor issue with the NEWS file for this
> release - the new features in 10.0.0b1 are reported as being for
> "9.0.3 (2018-03-31)".
>
> If you discover any bugs while testing the new release, please report
> them at https://github.com/pypa/pip/issues.
>
> Thanks to everyone who put so much effort into the new release. Many
> of the contributions came from community members, whether in the form
> of code, participation in design discussions, or bug reports. The pip
> development team is extremely grateful to everyone in the community
> for their contributions.
>
> Thanks,
> Paul
-- 
https://mail.python.org/mailman/listinfo/python-list

Re: Beta release of pip version 10

[MRAB]

On 2018-04-01 11:26, Paul Moore wrote:

On 1 April 2018 at 04:15, Mikhail V  wrote:

MRAB writes:



> UnicodeEncodeError: 'charmap' codec can't encode character
>
> when it meets a non-ascii char.
>
> e.g. tried this:
> pip search pygame > a.txt
>
Well, _I_ didn't get an error!

One of the lines is:

kundalini (0.4)- LրVE-like PyGame API

So it's down to what system encoding (active code page) is in use.


Dunno, it gives me error regardless of active codepage,
my default is 866, i've set to 1252 or 65001, same error.

The output itself is fine - I see correct glyphs, so the error
only appears when I redirect to file.
if I try some python script e.g. "a.py":
print ("абв")

and run:
py a.py > a.txt

I get some gibberish in the file.
So it is probably a global issue. Nothing works in this life :)


That actually sounds more like a redirection issue. Redirecting in the
cmd shell uses the OEM codepage, I believe, and Python outputs to a
pipe using the ANSI codepage, IIRC (I'd have to check to be certain).


Yep, it's fine until redirected.
--
https://mail.python.org/mailman/listinfo/python-list

Re: Beta release of pip version 10

[Paul Moore]

On 1 April 2018 at 03:16, MRAB  wrote:
> On 2018-04-01 02:50, Mikhail V wrote:
>>
>> Steven D'Aprano writes:
>>

 PS: was looking forward to PIP improvements on Windows, on 9.0.3 still
 some issues. E.g. trying to redirect output from 'pip search ... >
 a.txt' gives a wall of errors. it's on Windows 10.
>>>
>>>
>>>
>>>
>>> Don't be shy, tell us what those errors are.
>>
>>
>>
>> You meant - don't be lazy to figure out how to reproduce it.
>>
>> UnicodeEncodeError: 'charmap' codec can't encode character
>>
>> when it meets a non-ascii char.
>>
>> e.g. tried this:
>> pip search pygame > a.txt
>>
> Well, _I_ didn't get an error!
>
> One of the lines is:
>
> kundalini (0.4)- LրVE-like PyGame API
>
> So it's down to what system encoding (active code page) is in use.

As noted in the announcement, please feel free to report the issue. We
fixed a lot of encoding errors for pip 10, but it's quite possible
that we missed this as no-one reported it. We'll need clear
instructions on how to reproduce it, as it doesn't fail for me
(Windows 10, pip 10.0.0b1, Python 3.6, Powershell shell):

>py -m pip search kundalini
kundalini (0.4)  - LÖVE-like PyGame API

Paul
-- 
https://mail.python.org/mailman/listinfo/python-list

Re: Beta release of pip version 10

[Paul Moore]

On 1 April 2018 at 04:15, Mikhail V  wrote:
> MRAB writes:
>
>
>> > UnicodeEncodeError: 'charmap' codec can't encode character
>> >
>> > when it meets a non-ascii char.
>> >
>> > e.g. tried this:
>> > pip search pygame > a.txt
>> >
>> Well, _I_ didn't get an error!
>>
>> One of the lines is:
>>
>> kundalini (0.4)- LրVE-like PyGame API
>>
>> So it's down to what system encoding (active code page) is in use.
>
> Dunno, it gives me error regardless of active codepage,
> my default is 866, i've set to 1252 or 65001, same error.
>
> The output itself is fine - I see correct glyphs, so the error
> only appears when I redirect to file.
> if I try some python script e.g. "a.py":
> print ("абв")
>
> and run:
> py a.py > a.txt
>
> I get some gibberish in the file.
> So it is probably a global issue. Nothing works in this life :)

That actually sounds more like a redirection issue. Redirecting in the
cmd shell uses the OEM codepage, I believe, and Python outputs to a
pipe using the ANSI codepage, IIRC (I'd have to check to be certain).

Paul
-- 
https://mail.python.org/mailman/listinfo/python-list

Beta release of pip version 10

[Mikhail V]

MRAB writes:


> > UnicodeEncodeError: 'charmap' codec can't encode character
> >
> > when it meets a non-ascii char.
> >
> > e.g. tried this:
> > pip search pygame > a.txt
> >
> Well, _I_ didn't get an error!
>
> One of the lines is:
>
> kundalini (0.4)- LրVE-like PyGame API
>
> So it's down to what system encoding (active code page) is in use.

Dunno, it gives me error regardless of active codepage,
my default is 866, i've set to 1252 or 65001, same error.

The output itself is fine - I see correct glyphs, so the error
only appears when I redirect to file.
if I try some python script e.g. "a.py":
print ("абв")

and run:
py a.py > a.txt

I get some gibberish in the file.
So it is probably a global issue. Nothing works in this life :)
-- 
https://mail.python.org/mailman/listinfo/python-list

Re: Beta release of pip version 10

[MRAB]

On 2018-04-01 02:50, Mikhail V wrote:

Steven D'Aprano writes:



PS: was looking forward to PIP improvements on Windows, on 9.0.3 still
some issues. E.g. trying to redirect output from 'pip search ... >
a.txt' gives a wall of errors. it's on Windows 10.




Don't be shy, tell us what those errors are.



You meant - don't be lazy to figure out how to reproduce it.

UnicodeEncodeError: 'charmap' codec can't encode character

when it meets a non-ascii char.

e.g. tried this:
pip search pygame > a.txt


Well, _I_ didn't get an error!

One of the lines is:

kundalini (0.4)- LրVE-like PyGame API

So it's down to what system encoding (active code page) is in use.
--
https://mail.python.org/mailman/listinfo/python-list

Beta release of pip version 10

[Mikhail V]

Steven D'Aprano writes:

>>
>> PS: was looking forward to PIP improvements on Windows, on 9.0.3 still
>> some issues. E.g. trying to redirect output from 'pip search ... >
>> a.txt' gives a wall of errors. it's on Windows 10.
>
>
>
> Don't be shy, tell us what those errors are.


You meant - don't be lazy to figure out how to reproduce it.

UnicodeEncodeError: 'charmap' codec can't encode character

when it meets a non-ascii char.

e.g. tried this:
pip search pygame > a.txt
-- 
https://mail.python.org/mailman/listinfo/python-list

Re: Beta release of pip version 10

[Steven D'Aprano]

On Sun, 01 Apr 2018 03:17:51 +0300, Mikhail V wrote:

> PS: was looking forward to PIP improvements on Windows, on 9.0.3 still
> some issues. E.g. trying to redirect output from 'pip search ... >
> a.txt' gives a wall of errors. it's on Windows 10.


Don't be shy, tell us what those errors are.


-- 
Steve

-- 
https://mail.python.org/mailman/listinfo/python-list

Beta release of pip version 10

[Mikhail V]

Paul Moore writes :

If you discover any bugs while testing the new release, please report
> them at https://github.com/pypa/pip/issues.


Link not working (on pipermail archive -- remove the period on the end)
https://github.com/pypa/pip/issues

PS: was looking forward to PIP improvements on Windows,
on 9.0.3 still some issues. E.g. trying to redirect output
from 'pip search ... > a.txt' gives a wall of errors.
it's on Windows 10.

(logging to file is needed because there is no advanced
search, so need some filtering to restrict the output to
packages only, since it searches in description too and
that may be a lng list of packages).



Mikhail
-- 
https://mail.python.org/mailman/listinfo/python-list

Beta release of pip version 10

[Paul Moore]

On behalf of the PyPA, I am pleased to announce that a beta release
10.0.0b1 of pip has just been released for testing by the community.
We're planning on a final release in 2 weeks' time, over the weekend
of 14/15 April.

To install pip 10.0.0.b1, you can run

python -m pip install --upgrade --pre pip

(obviously, you should not do this in a production environment!)

We would be grateful for all testing that users could do, to ensure
that when pip 10 is released it's as solid as we can make it.

Highlights of the new release:

* Python 2.6 is no longer supported - if you need pip on Python 2.6,
you should stay on pip 9, which is the last version to support Python
2.6.
* Support for PEP 518, which allows projects to specify what packages
they require in order to build from source. (PEP 518 support is
currently limited, with full support coming in future versions - see
the documentation for details).
* Significant improvements in Unicode handling for non-ASCII locales on Windows.
* A new "pip config" command.
* The default upgrade strategy has become "only-if-needed"
* Many bug fixes and minor improvements.

In addition, the previously announced reorganisation of pip's
internals has now taken place. Unless you are the author of code that
imports the pip module (or a user of such code), this change will not
affect you. If you are, please report the issue to the author of the
affected code (refer them to
https://mail.python.org/pipermail/distutils-sig/2017-October/031642.html
for the details of the announcement).

Please note that there is a minor issue with the NEWS file for this
release - the new features in 10.0.0b1 are reported as being for
"9.0.3 (2018-03-31)".

If you discover any bugs while testing the new release, please report
them at https://github.com/pypa/pip/issues.

Thanks to everyone who put so much effort into the new release. Many
of the contributions came from community members, whether in the form
of code, participation in design discussions, or bug reports. The pip
development team is extremely grateful to everyone in the community
for their contributions.

Thanks,
Paul
-- 
https://mail.python.org/mailman/listinfo/python-list