Re: Application setup like windows msi

On 2020-03-05, Michael Torrie wrote: > On 3/4/20 4:51 PM, J A wrote: >> I was wondering g if there was a way to distribute an application that took >> advantage of user input like a windows .msi does. On linux of course. > > Several installer frameworks can make interactive installers for Linux. >

Re: Application setup like windows msi

Am 05.03.20 um 02:48 schrieb Michael Torrie: On 3/4/20 4:51 PM, J A wrote: I was wondering g if there was a way to distribute an application that took advantage of user input like a windows .msi does. On linux of course. Several installer frameworks can make interactive installers for Linux. T

Re: Pip borks the #! line when installing pylint from Python sandbox

> > The directory you stated is indeed the default directory as stated here > > https://unix.stackexchange.com/questions/240037/why-did-pip-install-a-package-into-local-bin > What happens when you explicitly state the location where you want to > store the package? Have you tried it? > >>

Re: What is the correct interpreter

You might try checking windows app management aliases by just tpying app management aliases in the search bar. There you should find two different version of python. One is the python which was available earlier in windows Store and the other one is the one you have installed in your machine. Try s

Re: Pip borks the #! line when installing pylint from Python sandbox

The directory you stated is indeed the default directory as stated here https://unix.stackexchange.com/questions/240037/why-did-pip-install-a-package-into-local-bin What happens when you explicitly state the location where you want to store the package? Have you tried it? On Thu, Mar 5, 2020, 9:4

Pip borks the #! line when installing pylint from Python sandbox

I originally sent this to the code-quality list, but in retrospect (and considering the crickets), I think c.l.py would have been a better starting point. I'm working on Python from GitHub, so have a fork which I check out and keep synced with the

Re: ÿ in Unicode

moi writes: 'ÿ'.encode('utf-8') > b'\xc3\xbf' 'ÿ'.encode('utf-16-le') > b'\xff\x00' 'ÿ'.encode('utf-32-le') > b'\xff\x00\x00\x00' That all looks as expected. Is there something about the output that puzzles you? Did you have a question? -- Ben. -- https://mail.python.org/mail