Boštjan Mejak added the comment:
No, Larry, this is not a new feature. The feature, as it stands, is broken in
Python 3.4, so we need to fix it.
--
___
Python tracker
<http://bugs.python.org/issue8
Boštjan Mejak added the comment:
Sure, let's have a broken feature in Python 3.4, who cares.
--
___
Python tracker
<http://bugs.python.org/issue8232>
___
___
Boštjan Mejak added the comment:
I understand. I know that Python 3.4 is way past feature freeze.
But if we document the new stuff in the documentation, saying "Added to Python
3.4.4", people would know about and be able to use the new stuff. And we won't
break people's c
Boštjan Mejak added the comment:
I understand. But then webbrowser.get("chrome") won't ever work in Python 3.4.
Is there no other way to fix this bug in Python 3.4 without adding the new
feature?
--
___
Python tracker
<http
Boštjan Mejak added the comment:
Steve, I know. But it's a hassle for a newcomer to fix Python first before
he/she uses it. I'm not a newcomer, but even I don't know how to fix
webbrowser.py, more specifically the webbrowser.get() method, to be able to
use it.
Mayb
Boštjan Mejak added the comment:
Ah, interesting! But which webbrowser module would Python import if I have one
webbrowser.py in my interpreter's directory and one webbrowser.py in the
directory of my application?
--
___
Python tracker
Boštjan Mejak added the comment:
No need to answer. Python used the webbrowser module that was located in the
directory of my application and not the one from the interpreter's directory.
That's great!
--
___
Python trac
Changes by Boštjan Mejak :
--
versions: +Python 3.5
___
Python tracker
<http://bugs.python.org/issue23780>
___
___
Python-bugs-list mailing list
Unsubscribe:
201 - 208 of 208 matches
Mail list logo
