- User Since
- Jul 16 2017, 3:10 PM (125 w, 4 d)
On Windows, you can set a registry key to one or more *.ini files or directories that get read in, so it seems slightly handy to know the order in which files are processed. I know I've used that mechanism on various systems to find directories in which to stash things too.
Wed, Dec 11
Tue, Dec 10
Sat, Dec 7
Fri, Dec 6
Wed, Dec 4
Tue, Dec 3
I don't think this is correct, because open is imported from pycompat at the top of the file, and that will sysstr() the mode. But this does seem confusing- see D7517.
Mon, Dec 2
Windows is happy with this test
Sun, Dec 1
Sat, Nov 30
Tue, Nov 26
Mon, Nov 25
Sun, Nov 24
Sat, Nov 23
Adjusting this to stay out of the review queue. While most of the files only had a handful of errors (and a few could be removed from the blacklist), the few added had a bunch of errors. I didn't see any obvious fixes, and ran out of time Friday to individually suppress them.
I only have a superficial understanding about how templates work, but I assume that there's no global pre-resolution step where a single query could be done and the results stuffed into the context or something, is there?
I'm not sure if there are plans to vendor *.pyi files. Maybe that could be used to backfill platform specific modules instead of doing this. But for now is seems better to get the error count and blacklist length reduced.
Fri, Nov 22
I'm not sure why, but this version seems to also show obsolete revisions. I've got a bunch of x and * nodes in hg-committed right now. I didn't see that before, although that was on a different clone that I don't have access to now.
I like it.
Thu, Nov 21
To continue using Python 2, set the PYTHON variable. e.g.
make install PYTHON=python2.7 or
make install PYTHON=py.exe -2.