blob: 7f492ed7222dd3375a7d475c2565d7ff1032cd52 (
plain) (
blame)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
|
+++
date = Date(2020, 6, 15)
tags = ["gsoc", "pip"]
+++
# Second Check-In
Hi everyone and may the odds ever in your favor, especially during this
tough time!
## What did I do last week?
Not as much I wished, apparently (-:
* Finalizing {{pip 8411 "the refactoring patch"}}
of `operations.prepare.prepare_linked_requirement`
* {{pip 8423 "Nitpicking some logging calls"}}. This (as well as the next one)
was to fill up the time my brain not being as productive as I want it to XD
* {{pip 8423 "Beginning to migrate"}} from `%`- to `{}`-style logging.
The amount of tests failing due to this was way beyond my imagination,
but I got functional tests for `pip install` and unit tests passing now!
* {{pip 8442 "Mocking up a working partial wheel download during
dependency resolution"}} for [the new resolver].
## Did I get stuck anywhere?
Yes, of course! {{pip 8320 "Parallel maps"}} are still stalling
as well as other small PRs listed above. The failure related to
`logging` are still making me pulling my hair out and the proof of
concept for partial wheel downloading is too ugly even for a PoC.
I imagine that I will have a lot of clean up to do this week (yay!).
## What is coming up next?
I'm trying get the multi-{threading,processing} facilities merged ASAP
to start rolling it out in practice. The first thing popping out of my
head is to get back {{pip 7962 "the multi-threaded"}} `pip list -o`.
The other experimental improvement (this phrase does not sound right!)
I would like to get done is the partial wheel download. It would be
really nice if I can get both included as `unstable-feature`'s
in {{pip 7628#issuecomment-636319539 "the upcoming beta release of pip 20.2"}}.
[the new resolver]: https://www.ei8fdb.org/test-pips-alpha-resolver-and-help-us-document-dependency-conflicts
|
