Re:Pipenv: promises a lot, delivers very little
by sametmax on Friday December 07, 2018 @04:03AM
(#18626106)
Because I'm not dogmatic, I can regognize good tools, even if I disagree with the underlying political decision.
Computing is not black and white, and perfect purity is only nice in "fizz buzz".
Now to be extra fun, poetry uses a custom section ([tool.poetry]) in pyproject.toml, not really the standard itself. What does that say about this format ?
Re:Pipenv: promises a lot, delivers very little
by guggle on Thursday December 06, 2018 @08:14AM
(#18617711)
oh, nevermind... I'll stick to manual venv/pip:
ptest poetry add requests
[UnicodeDecodeError]
'ascii' codec can't decode byte 0xc3 in position 1: ordinal not in range(128)
Re:Pipenv: promises a lot, delivers very little
by sdispater on Thursday December 06, 2018 @09:03AM
(#18618084)
Author of Poetry here!
I've never seen that error before.
Which version of Python do you use?
And feel free to create an issue on the issue tracker: https://github.com/sdispater/poetry/issues
Re:Pipenv: promises a lot, delivers very little
by sametmax on Friday December 07, 2018 @04:09AM
(#18626138)
pyproject debates aside, I love your work. I think poetry is a beautiful piece of software, the source code is very easy to read and the 2/3 compat is well done (although I would not use assert to check things).
However the default in poetry seems to be pyproject.toml... I'm confused.