Marco Sulla added the comment:
Well, what about the modification to VIRTUAL_ENV? I think it's little and
without harm.
--
___
Python tracker
<https://bugs.python.org/is
Marco Sulla added the comment:
> Changing VIRTUAL_ENV will break code
VIRTUAL_ENV it's the same if you don't move the venv. Moving it will be an
unofficial unsupported bonus, and if you coded bad and it doesn't work
Marco Sulla added the comment:
Well, I repeat, not with
#!/usr/bin/env python3
--
___
Python tracker
<https://bugs.python.org/issue36964>
___
___
Python-bug
Marco Sulla added the comment:
The previous post was for Laurie Opperman
"upset people with requiring everyone to update their code"
I don't know why they have to be upset. Until now they can't move the folder.
They want to move the folder? They have to change their co
Marco Sulla added the comment:
Furthermore, if you destroy an old virtual env and recreate it with the new
method, it continues to work as before, since VIRTUAL_ENV points to the same
folder. We don't force to change the code if they continues to use the virtual
environments a
Marco Sulla added the comment:
Please Mr. Cannon, can you read my last posts? I think they are not describing
a mad idea, but something reasonable.
--
nosy: +brett.cannon
___
Python tracker
<https://bugs.python.org/issue36
Marco Sulla added the comment:
> I don't like the idea of changing what VIRTUAL_ENV gets set to when I
> believe you should recreate the virtual environment as necessary and
> risk surprising people who expect VIRTUAL_ENV to function as it does
> today and has for years.
Change by Marco Sulla :
--
nosy: Marco Sulla
priority: normal
severity: normal
status: open
title: Propose to deprecate ignore_errors,
___
Python tracker
<https://bugs.python.org/issue37
New submission from Marco Sulla :
I propose to mark as deprecated the parameters `ignore_errors` and `onerror` of
`shutil.rmtree()`, and raise a warning if used.
The reason is I feel them unpythonic. For emulating `ignore_errors=True`, the
code can be written simply with a `try-except` that
New submission from Marco Sulla :
Currectly, even if two `Element`s elem1 and elem2 are different objects but the
tree is identical, elem1 == elem2 returns False. The only effective way to
compare two `Element`s is
ElementTree.tostring(elem1) == ElementTree.tostring(elem2)
Furthermore, from
New submission from Marco Sulla:
Steps to reproduce
1. create a format_bytes.py with:
"Hello {}".format(b"World")
2. launch it with
python3 -bb format_bytes.py
Result:
Traceback (most recent call last):
File "format_bytes.py", line 1, in
"Hello {}&
Marco Sulla added the comment:
I want to clarify more: I do not want to suppress the warning, I would that the
format minilanguage will convert bytes to string properly.
--
___
Python tracker
<http://bugs.python.org/issue26
Marco Sulla added the comment:
> Python 3 doesn't guess the encoding of byte strings anymore
And I agree, but I think format minilanguage could convert it by default to
utf8, and if something goes wrong raise an error (or try str()). More simple to
use and robust at the same time.
My
Marco Sulla added the comment:
> Using utf8 means guessing the encoding
Well, it's not what format() is doing now, using str()? :)
--
___
Python tracker
<http://bugs.python.org
101 - 114 of 114 matches
Mail list logo
