brettcannon

7 ms·

1.
by brettcannon 4y ago
There's a couple of reasons for the current situation in terms of the plethora of tools. One, Python and its packaging story is old (remember, Python predates Linux). That has given folks plenty of time to either come up with their own
2.
by brettcannon 6y ago
It was on purpose because TOML has not reached 1.0 yet and breaking people using a module in the stdlib for parsing TOML because TOML itself changed would be an absolute mess. Plus not a single packaging project said it was an issue to eith
3.
by brettcannon 6y ago
I'm not sure how old you are, but if you don't know the name "Borland" you might not realize how novel it is to have a compiler on every major OS. While Python's age means it has been around to see a lot of changes
4.
by brettcannon 6y ago
I think something people are forgetting when comparing Python's packaging system to other languages and runtimes is how old Python and its ecosystem is. For instance, Python's public release predates Linux's public release(Fe
5.
by brettcannon 6y ago
The specific restriction from my understanding is that a US non-profit that accepts money for a specific thing must spend every penny of that money only on that thing. So if the PSF was given $1,000,000 to solve a specific problem and w
6.
by brettcannon 6y ago
There's a rough list at https://wiki.python.org/psf/Fundable%20Packaging%20Improveme... . There's no official roadmap as getting a group of volunteers to agree to a list of priorities would be near impossible.
7.
by brettcannon 6y ago
> First of all, as an aside, thank you for all the work you do on Python! Welcome! > is Don still there? Yep, working on the data science features of the extension. > on Talk Python I remember specifically Michael and some others t
8.
by brettcannon 6y ago
Do note that Python the language is developed by a separate group as Python the packaging ecosystem. So even when Guido was a BDFL he completely stayed out of the packaging situation. And there is a packaging BDFL, but there's a severe
9.
by brettcannon 6y ago
People would love to see that happen, but it requires time and effort from people to build such a solution. Some people are trying, e.g. https://pyoxidizer.readthedocs.io/ and https://briefcase.readthedocs.io&#x2
10.
by brettcannon 6y ago
It's all about capacity, not will. The PyPA as a whole knows what is lacking, but when you're all just a bunch of volunteers it's hard to tackle massive projects that take potentially years to complete and then even longer to
11.
by brettcannon 6y ago
> I can't see a world where the Python Software Foundation can't get support for this, I think they have the contacts at the big companies to get it funded. You might be surprised at how hard it is to get money donated for this
12.
by brettcannon 6y ago
I personally don't think that comic is fair to hold against pip or the packaging ecosystem. I did a separate post on deconstructing it at https://snarky.ca/deconstructing-xkcd-com-1987/ .
13.
by brettcannon 7y ago
Raymond came up with the idea, PyPy implemented it, and then INADA Naoki implemented it for CPython.
14.
by brettcannon 7y ago
Poetry tries to help you manage your whole project while flit is just for building your library (and optionally uploading; you can always use twine to do the upload). It's all-in-one versus one-job-one-tool.
15.
by brettcannon 7y ago
If you use a grepping tool like ripgrep it will automatically ignore everything in your `.gitignore`, so at least for that specific case you're covered.
16.
by brettcannon 7y ago
Please file issues as you find regressions at https://github.com/microsoft/python-language-server as the team is working diligently to fix such issues.
17.
by brettcannon 7y ago
The language server team has been working hard to fix the high CPU and memory leaks as recently as this week. Please do try it out on occasion to see if your issue has been resolved as the team is working hard to improve it.
18.
by brettcannon 8y ago
What specifically are you looking for in terms of pipenv? We actually supported pipenv environments before PyCharm, so if you have specific needs please open an issue at https://github.com/microsoft/vscode-python/i
19.
by brettcannon 8y ago
If you specifically want Python support for e.g. coverage.py, then please open an issue at https://github.com/microsoft/vscode-python/issues .
20.
by brettcannon 8y ago
Please file a bug at https://github.com/microsoft/vscode-python/issues
21.
by brettcannon 8y ago
GitHub is planning to keep Atom going: https://www.reddit.com/r/AMA/comments/8pc8mf/im_nat_friedman...
22.
by brettcannon 8y ago
The key thing to know is that the Microsoft Python Language Server -- long, official name I know, hence why we just call it MPLS internally ;) -- comes from our Python workload for Visual Studio. It was an extremely tough call to make becau
23.
by brettcannon 8y ago
The language server currently only supports 64-bit Linux, so if you have that on your Pi then it should be faster.
24.
by brettcannon 8y ago
If you look under the Visual Studio 2017 instructions it mentions where to copy those files into the extension so they will get used.
25.
by brettcannon 8y ago
The protocol itself is open source: https://github.com/Microsoft/language-server-protocol . I'm sure the folks in charge of it would be happy to talk to PyCharm if they wanted to contribute.
26.
by brettcannon 8y ago
The community edition is free, the professional edition is not: https://www.jetbrains.com/pycharm/features/editions_comparis...
27.
by brettcannon 8y ago
He fought for it because he thought it was the right call. The role of a BDFL is to make those kinds of calls for the benefit of the language and community. It's really tough to fight the "tyranny of the majority" and go with
28.
by brettcannon 8y ago
28 if you want the exact number. :) Guido started developing Python in December 1989 and went public with it on Usenet in February 1991 (Unicode 1.0 was standardized in October later that year to give perspective of how far back that was in
29.
by brettcannon 8y ago
We are acutely aware of why Guido is retiring sooner than any of us expected; it has actually been discussed already on the mailing list as to what went wrong with the PEP 572 discussion and how we could potentially fix it. So there's
30.
by brettcannon 9y ago
Please realize that the concept of virtual environments in Python predate things like npm, so there are lessons that were learned later on that no one knew about. Also realize that the things you list all layer on top of each other so you&#

More ›