Log file Viewer
Help
|
Karma
| Search:
#pypa logs for Thursday the 20th of November, 2014
(
Back to #pypa overview
) (
Back to channel listing
) (
Animate logs
)
[
00:12:40
] <
delinquentme
> ahmeni, tbh it works now ... and i have no idea why
[
00:13:06
] <
delinquentme
> some combination of pip flags, git/https protocols and tags within github
[
17:53:26
] <
tos9
> Anyone particularly have an idea what's going on here: https://github.com/pypa/pip/issues/1661
[
18:00:34
] <
tos9
> Oh the upstream ticket has a "solution".
[
18:00:51
] <
dstufft
> tos9: what version of pypy
[
18:04:51
] <
tos9
> dstufft: 2.4.0
[
18:05:00
] <
tos9
> And in fact 3.5.0b2 does actually work.
[
18:05:12
] <
tos9
> But there's no non-pre release of configparser that does apparently.
[
18:06:39
] <
dstufft
> tos9: what did they change do you know?
[
18:07:31
] <
tos9
> dstufft: I don't -- I can try to figure that out though... I started to, but I forgot that pip forks to do the install
[
18:07:45
] <
tos9
> Let's see what they did...
[
18:08:07
] <
dstufft
> something makes me think that 2.4.0 had that issue with pip
[
18:08:12
] <
dstufft
> and they issued 2.4.1 to fix it
[
18:09:05
] <
dstufft
> oh nvm
[
18:09:06
] <
dstufft
> that was 2.2
[
18:16:54
] <
tos9
> literally being foiled by not knowing how to switch mercurial branches
[
18:17:15
] <
tos9
> roundrobining between hg pull, hg branch, hg checkout
[
18:17:17
] <
tos9
> time to google.
[
18:19:39
] <
dstufft
> hg update
[
18:19:40
] <
dstufft
> I think
[
18:36:52
] <
apollo13
> git checkout *scnr*