On Mon, Jan 25, 2016 at 11:58:12PM +0100, Victor Stinner wrote:
> ...
> Oh, they are a lot of things to do! ...
Just wondering, do you also need a set of (abusive) test-cases which
check 100% conformity to the CPython semantics? I'm sure many of us
would be able to whip up some ideas of things tha
I would like to make just 1 comment regarding the question of accepting
(or not) bytes as output of `os.fspath`.
The whole point of adding `os.fspath` is to make it easier to use Path
objects. This is in an effort to gain greater adoption of pathlib in
libraries. Now, this is an excellent idea.
H
> On 12 May 2016, at 21:30, Ethan Furman wrote:
>
> If you need bytes support for your paths, there's at least one [1] that has
> that support.
So if I would need bytes support, I should submit a pull request to which replaces usage of the stdlib pathlib with another
variant, upon which the
> On 13 May 2016, at 08:07, Ethan Furman wrote:
>
> On 05/12/2016 01:59 PM, Sjoerd Job Postmus wrote:
>>> On 12 May 2016, at 21:30, Ethan Furman wrote:
>>>
>>> If you need bytes support for your paths, there's at least one [1] that has
>>
On Aug 19, 2016 6:46 PM, Chris Angelico wrote:
>
> On Sat, Aug 20, 2016 at 2:25 AM, Steve Dower wrote:
> > On 19Aug2016 0910, Chris Angelico wrote:
> >>
> >> On Sat, Aug 20, 2016 at 1:26 AM, Steve Dower
> >> wrote:
> >>>
> >>> Check any .pth files you can find. I suspect mpl_toolkits has some m
On Aug 19, 2016 11:10 PM, Chris Angelico wrote:
>
> On Sat, Aug 20, 2016 at 5:33 AM, Brett Cannon wrote:
> >> Hmmm. So the question is, what is this test testing?
> >
> >
> > It's making sure people who work on the modules that are imported during
> > startup don't accidentally add another mo
