[issue10092] calendar does not restore locale properly

Changes by Boštjan Mejak : Removed file: http://bugs.python.org/file19316/unnamed ___ Python tracker <http://bugs.python.org/issue10092> ___ ___ Python-bugs-list mailin

[issue10092] calendar does not restore locale properly

Boštjan Mejak added the comment: >>> calendar.LocaleTextCalendar(locale='fr_FR').formatmonthname(2010,10,10) is not valid because 'fr_FR' is not a valid value for the 'locale' argument What is valid is this: >>> calendar.LocaleTextCale

[issue10092] calendar does not restore locale properly

Boštjan Mejak added the comment: Yes, I know this issue is closed but I wonder how could your Python interpreter not error on >>> calendar.LocaleTextCalendar(locale='fr_FR').formatmonthname(2010,10,10) Please retry executing the above line of code in Python 2.7.1 interpreter and tell me if you

[issue10562] Change 'j' for imaginary unit into an 'i'

Boštjan Mejak added the comment: The imaginary unit 'i' should be equvivalent to the imaginary unit 'j'. The imaginary unit, however, should be used consistently in the source code. -- Added file: http://bugs.python.org/file19908/unnamed ___ Python

[issue10562] Change 'j' for imaginary unit into an 'i'

Boštjan Mejak added the comment: That is acceptable, but way to slow for the 'j' imaginary unit to become extinct. It should happen sooner. -- Added file: http://bugs.python.org/file19910/unnamed ___ Python tracker

[issue10562] Change 'j' for imaginary unit into an 'i'

Boštjan Mejak added the comment: How did you implement the letter 'j' as the imaginary unit? Can you now implement the letter 'i' to act as an imaginary unit? Is that possible? If it's possible in MATLAB, why not have both 'j' and 'i' in Python as well? -- Added file: http://bugs.pytho

[issue10562] Change 'j' for imaginary unit into an 'i'

Boštjan Mejak added the comment: "In electrical engineering and related fields, the imaginary unit is often denoted by *j* to avoid confusion with electrical current as a function of time, t

[issue10562] Change 'j' for imaginary unit into an 'i'

Boštjan Mejak added the comment: (7.8064-6j) According to PEP 8, the output in our example should be with spaces surrounding the subtraction operator, like this: >>> (1 + 2.56j) * (-1 - 3.44j) (7.8064 - 6j) -- Added file: http://bugs.python.org/file19914/unnamed _

[issue10562] Change 'j' for imaginary unit into an 'i'

Boštjan Mejak added the comment: The result of 1 + 2j cannot be further broken down, so the result stays as 1 + 2j (note the spaces!). (1+2j) (1 + 2j) Following PEP 8 in this regard is also needed. Abandon the request of adding the i unit and rather fix this spacing issue. The complex() buil

[issue10562] Change 'j' for imaginary unit into an 'i'

Boštjan Mejak added the comment: Please make the tokenizer surround spaces around operators. So the output would be like in the example below: (1 + 2j) (1 + 2j) -- Added file: http://bugs.python.org/file19925/unnamed ___ Python tracker

[issue10562] Change 'j' for imaginary unit into an 'i'

Boštjan Mejak added the comment: Indeed. There should be spaces around all the operators. Even in my posted example. -- Added file: http://bugs.python.org/file19927/unnamed ___ Python tracker

[issue10562] Change 'j' for imaginary unit into an 'i'

Boštjan Mejak added the comment: Alexander, is it possible to make an output like (1+2j) be printed as (1 + 2j). Also, why is the result put in parens? -- Added file: http://bugs.python.org/file19928/unnamed ___ Python tracker

[issue10562] Change 'j' for imaginary unit into an 'i'

Boštjan Mejak added the comment: Parens are okay then. Still, put spaces around operators. If 1 + 2j let the output be (1 + 2j)Please!!! -- Added file: http://bugs.python.org/file19929/unnamed ___ Python tracker

[issue10621] >>> 1 + 2j --> (1 + 2j) and not (1+2j)

New submission from Boštjan Mejak : Python interpreter should put spaces around operators in return values of complex numbers. If you give it >>> 1 + 2j it should return (1 + 2j) and not the current (1+2j) My argument is that complex numbers are written like this, with spaces su

[issue10516] Add list.clear() and list.copy()

Boštjan Mejak added the comment: This is really welcome. It makes Python even more readable. If 'a' is a list object, a[:] is not so obvious at first to a newcomer, but a.copy() is. Also, a.clear() is so perfect and understandable. I wish you could decorate Python versions prior t

[issue10621] >>> 1 + 2j --> (1 + 2j) and not (1+2j)

Boštjan Mejak added the comment: Please do the move to complex_repr if everything then works the same (i.e. nothing breaks the build) if the readability is in fact improved. Also, change the docs and fix the tests. You know the drill. P.S.: (1+2j) is worth changing to become (1 + 2j) in the fu

[issue10621] >>> 1 + 2j --> (1 + 2j) and not (1+2j)

Boštjan Mejak added the comment: Do you ever fix anything? -- Added file: http://bugs.python.org/file19940/unnamed ___ Python tracker ___Do you ever fix anything? _

[issue10516] Add list.clear() and list.copy()

Boštjan Mejak added the comment: I'm troubled with one little letter: "L.copy() -> list -- a shallow copy of L"); should be "L.copy() -> list -- shallow copy of L"); without the letter 'a', because other sentences also don't say "L.__sizeof__() -- *A* size of L in memory, in bytes"); Plea

[issue10516] Add list.clear() and list.copy()

Boštjan Mejak added the comment: Can you please help me find the definition of the copy() method of dict in the Python sources? I want to see how that method is defined and compare the definition to the one in Eli's patch. -- Added file: http://bugs.python.org/file19948/unnamed __

[issue10516] Add list.clear() and list.copy()

Boštjan Mejak added the comment: mapp_methods ? Don't you mean map_methods ? -- Added file: http://bugs.python.org/file19954/unnamed ___ Python tracker ___mapp_methods ?  

[issue10516] Add list.clear() and list.copy()

Boštjan Mejak added the comment: mapp_methods looks like a typo. you know -- mapp_...? isn't map_... correct? -- Added file: http://bugs.python.org/file19957/unnamed ___ Python tracker ___

[issue10516] Add list.clear() and list.copy()

Boštjan Mejak added the comment: Why mapp_methods, why not map_methods? Any reason for this? -- Added file: http://bugs.python.org/file19959/unnamed ___ Python tracker ___Why m

[issue44054] 2**53+1 != float(2**53+1)

Boštjan Mejak added the comment: I would compare it like this: >>> from decimal import Decimal >>> 2**53 + 1 == Decimal(2**53 + 1) True -- nosy: +PedanticHacker ___ Python tracker <https://bugs.

[issue44366] Define functions without parentheses (if no parameters given)

New submission from Boštjan Mejak : The syntax to define a class looks like this: class MyClass: pass Nice and neat. *** And the syntax to define a function looks like this: def my_function(): pass Hmmm... *** What if we could define functions (that don't have any parameters)

[issue45318] Python 3.10: cyclomatic complexity of match-case syntax

New submission from Boštjan Mejak : I am wondering about the cyclomatic complexity of using the new match-case syntax in Python 3.10, and later. What is the cyclomatic complexity difference (if any?) of a match-case code as opposed to code that uses the if-elif-else syntax? So my question is

[issue45349] configparser.ConfigParser: 2 newlines at end of file (EOF)

New submission from Boštjan Mejak : In every Python version that I've tested, writing a config.ini file (utilizing configparser.ConfigParser), the result is such that the config.ini file has 2 newlines at the end of the file. The problem is that source code editors like Sublime Text, or

[issue40004] String comparison with dotted numerical values wrong

New submission from Boštjan Mejak : I stumbled upon a possible bug in the Python interpreter while doing some Python version comparisons. Look at this: "3.10.2" < "3.8.2" True # This is not true as a version number comparison Now look at this: "3.10.2" <

[issue40004] String comparison with dotted numerical values wrong

Boštjan Mejak added the comment: What is then the most Pythonic way of comparing two version numbers? -- ___ Python tracker <https://bugs.python.org/issue40

[issue43255] Ceil division with /// operator

New submission from Boštjan Mejak : I hope I'm not too late for a Python 3.10 feature request. I love the fact that Python 3.x does floor division with the // operator. We, however, don't have a ceil division operator, besides importing the math module and using its math.ceil() fun

[issue43255] Ceil division with /// operator

Boštjan Mejak added the comment: The spaceship operator is kinda cool! :) Well, I was hoping to avoid importing the math module just to have ceil division capabilities. Anyway, my need for ceiling is that I am coding a chess GUI where I have a table with 2 columns and I create a new row

[issue43255] Ceil division with /// operator

Boštjan Mejak added the comment: My hat off to you, Mr. Peters! Your suggestion (len(moves) + 1) // 2 works perfectly and is much more elegant than --0-- len(moves) // 2. :) Mr. Stinner, in what way would int.bit_count() be beneficial to me

[issue43255] Ceil division with /// operator

Boštjan Mejak added the comment: Mr. Stinner, I really don't understand what are you hinting at. -- ___ Python tracker <https://bugs.python.org/is

[issue41286] Built-in platform module does not offer to check for processor instructions

New submission from Boštjan Mejak : The platform module does not offer to check whether a processor supports the POPCNT or BMI/BMI2 processor instructions. Am I missing something or is it actually missing this feature? -- components: Library (Lib) messages: 373563 nosy: PedanticHacker

[issue41286] Built-in platform module does not offer to check for processor instructions

Boštjan Mejak added the comment: This feature is needed for a chess GUI application because the Stockfish chess engine is offered in different builds: a build that supports the POPCNT processor instruction and a build that doesn't, a build that supports the BMI/BMI2 processor instructio

[issue41286] Built-in platform module does not offer to check for processor instructions

Boštjan Mejak added the comment: Unfortunately, I don't know C, only Python. -- ___ Python tracker <https://bugs.python.org/issue41286> ___ ___ Python-bugs-l

[issue41286] Built-in platform module does not offer to check for processor instructions

Boštjan Mejak added the comment: Thanks for letting me know about py-cpuinfo. It is a very good tool. It solves my problem. This Python issue can now be closed as "Won't fix". -- ___ Python tracker <https://bugs.pyt

[issue42271] Remove the error and the zipfile.ZipFile.BadZipfile aliases

New submission from Boštjan Mejak : Remove the long-forgotten aliases 'error' and 'BadZipfile' in 'zipfile.ZipFile' class which are just pre-3.2 compatibility names. Python 3.10 should finally remove these aliases. -- components: Library (Lib) message

[issue13695] "type specific" to "type-specific"

Boštjan Mejak added the comment: There's also one more typo in the doc for cmp_to_key() function. Fix the first sentence "Transform an old-style comparison function to a key-function." to "Transform an old-style comparison function to a key function." (note the remo

[issue13695] "type specific" to "type-specific"

Boštjan Mejak added the comment: Found one little bug again in http://docs.python.org/library/stdtypes.html#sequence-types-str-unicode-list-tuple-bytearray-buffer-xrange Look at the table with the fields Operation, Result, Notes, and fix the fifth record of the Result field from "i&#x

[issue13695] "type specific" to "type-specific"

Boštjan Mejak added the comment: I guess you're reffering to the "i'th" --> "i-th" thing. I found numerous occasions on the Internet that say like "n-th element blah blah blah", not "n'th element..." So I gues

[issue13695] "type specific" to "type-specific"

Boštjan Mejak added the comment: Well, actually, it's the only correct way to write it (i-th). This is a simple orthographical error that was made. Ezio, please fix those two additional typos. And Georg, stop being such a wise-ass. -- ___ P

[issue13695] "type specific" to "type-specific"

Boštjan Mejak added the comment: Shut up, Georg! Ezio, please fix this two additional typos to close this bug report for good. -- ___ Python tracker <http://bugs.python.org/issue13

[issue13811] In str.format an incorrect alignment option doesn't make fill char and onself absent

Boštjan Mejak added the comment: Please fix the error message to "invalid format specifier" -- nosy: +Retro ___ Python tracker <http://bugs.python.o

[issue13695] "type specific" to "type-specific"

Changes by Boštjan Mejak : -- nosy: -georg.brandl resolution: remind -> ___ Python tracker <http://bugs.python.org/issue13695> ___ ___ Python-bugs-list mai

[issue13695] "type specific" to "type-specific"

Boštjan Mejak added the comment: I am closing this issue report and opening another issue report with the two new doc typos that were not reported here before the commit of Ezio Melotti. -- nosy: -docs@python, ezio.melotti, python-dev, rhettinger resolution: -> fixed status: o

[issue13816] Two typos in the docs

New submission from Boštjan Mejak : There's a typo in the docs for cmp_to_key() function. Fix the first sentence "Transform an old-style comparison function to a key-function." to "Transform an old-style comparison function to a key function." (delete the hyphen

[issue13816] Two typos in the docs

Boštjan Mejak added the comment: I am deeply and truly sorry. Can we now fix this? -- ___ Python tracker <http://bugs.python.org/issue13816> ___ ___ Python-bug

[issue13816] Two typos in the docs

Boštjan Mejak added the comment: Terry, I agree with you on having *i*th instead of *i*-th. The fact that "i" is written in italics eliminates the need of a hyphen. Justin, can I ask you to make a new patch which fixes "key-function" to "key function" and *i*

[issue13816] Two typos in the docs

Boštjan Mejak added the comment: Yeah, I guess I was kind of rude. Sorry about that. I think my proposal is acceptable. What do you think? -- ___ Python tracker <http://bugs.python.org/issue13

[issue13816] Two typos in the docs

Boštjan Mejak added the comment: I fixed Justin's patch. Anyone cares to incorporate it? -- Added file: http://bugs.python.org/file24293/fixed patch final.diff ___ Python tracker <http://bugs.python.org/is

[issue13816] Two typos in the docs

Boštjan Mejak added the comment: Georg, thanks for the tip. Is there any difference in reST between *i*\ th and *i*\th ? -- ___ Python tracker <http://bugs.python.org/issue13

[issue13816] Two typos in the docs

Boštjan Mejak added the comment: I hope the patch is now good. What do you think? -- Added file: http://bugs.python.org/file24296/done deal.diff ___ Python tracker <http://bugs.python.org/issue13

[issue13816] Two typos in the docs

Boštjan Mejak added the comment: Ah, darn it! My last patch is a total garbage. But then an interesting thing happened: I wanted to delete my last patch set, but I got a "ProgrammingError at /review/13816/patchset/4039/delete schema "datetime" does not exist" and got

[issue13816] Two typos in the docs

Changes by Boštjan Mejak : Removed file: http://bugs.python.org/file24296/done deal.diff ___ Python tracker <http://bugs.python.org/issue13816> ___ ___ Python-bugs-list m

[issue13816] Two typos in the docs

Changes by Boštjan Mejak : Removed file: http://bugs.python.org/file24293/fixed patch final.diff ___ Python tracker <http://bugs.python.org/issue13816> ___ ___ Python-bug

[issue13816] Two typos in the docs

Boštjan Mejak added the comment: I wasn't able to remove the patch via "Delete Patch Set" but I did it by clicking on the Unlink button. So the "Delete Patch Set" option has a bug. -- ___ Python tracker <http:

[issue13816] Two typos in the docs

Boštjan Mejak added the comment: Georg, I object to your comment about *i*th needing to be *i*\ th because currently in the source code we have it written as *i*'th which, by your logic, would need to be written as *i*\ 'th which is not so and is compiled/displayed/whatever perfe

[issue13816] Two typos in the docs

Boštjan Mejak added the comment: This stupid HG is so cryptic. SVN was so easy, now I can't even create a patch. Can you just fix those two typos as "key function" and "*i*th" please? Thank you. -- ___ Python tracker

[issue10580] Installer sentence in bold

Boštjan Mejak added the comment: Is this fixed or what? -- nosy: +jwehnes type: -> enhancement ___ Python tracker <http://bugs.python.org/issue10580> ___ _

[issue10580] Installer sentence in bold

Boštjan Mejak added the comment: Can you please fix this? -- ___ Python tracker <http://bugs.python.org/issue10580> ___ ___ Python-bugs-list mailing list Unsub

[issue13852] Doc fixes with patch

New submission from Boštjan Mejak : I have collected a small amount of documentation fixes in my patch. Please review it and apply it. No pressure. ;) -- assignee: docs@python components: Documentation files: changes.diff keywords: patch messages: 151900 nosy: Retro, docs@python

[issue13852] Doc fixes with patch

Changes by Boštjan Mejak : -- nosy: +ezio.melotti ___ Python tracker <http://bugs.python.org/issue13852> ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue13852] Doc fixes with patch

Changes by Boštjan Mejak : -- nosy: +terry.reedy ___ Python tracker <http://bugs.python.org/issue13852> ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue13868] Add hyphen doc fix

New submission from Boštjan Mejak : When you have time, incorporate this patch. Thanks. -- assignee: docs@python components: Documentation files: smallfix.diff keywords: patch messages: 151985 nosy: Retro, docs@python priority: normal severity: normal status: open title: Add hyphen doc

[issue10580] Installer sentence in bold

Boštjan Mejak added the comment: After more than a year the patch is finally made. Can someone please applies this patch and closes this issue report? Thanks. -- keywords: +patch versions: +Python 3.3 Added file: http://bugs.python.org/file24329/issue10580.diff

[issue13868] Add hyphen doc fix

Boštjan Mejak added the comment: If "floating point" in a sentence is in a role of an adjective, then it must be written as "floating-point" (with a hyphen), otherwise not. Example: "The number 3.5 is a floating-point number." Please consult some English orth

[issue13868] Add hyphen doc fix

Boštjan Mejak added the comment: I know that there are a lot of non-hyphenated occurences of "floating point" in Python docs, so I just want to raise awareness about those occurences. Can you fix all occurences of "floating point" (when in a role of an adjective

[issue13868] Add hyphen doc fix

Boštjan Mejak added the comment: For the time being I don't find any other "floating point" occurences in Python docs. I found one and made a patch for it. Please apply the patch. Thanks. -- ___ Python tracker <http://bugs.pyt

[issue10580] Installer sentence in bold

Boštjan Mejak added the comment: Please apply this patch. -- ___ Python tracker <http://bugs.python.org/issue10580> ___ ___ Python-bugs-list mailing list Unsub

[issue13868] Add hyphen doc fix

Boštjan Mejak added the comment: What's the purpose of this tracker if the author of an issue report has to beg for something to be fixed, despite the fact that (s)he even made a patch ? -- ___ Python tracker <http://bugs.py

[issue10580] Minor grammar change in Python’s MSI installer

Boštjan Mejak added the comment: Rather apply the patch, not change the title. -- ___ Python tracker <http://bugs.python.org/issue10580> ___ ___ Python-bug

[issue10580] Minor grammar change in Python’s MSI installer

Boštjan Mejak added the comment: Apply this patch. It is not necessary to change the title of this issue report, it is of most importance that this patch gets applied already after more than a year. Come on people, move your butts on this

[issue13868] Add hyphen doc fix

Boštjan Mejak added the comment: Seriously, how old are you two clowns? -- ___ Python tracker <http://bugs.python.org/issue13868> ___ ___ Python-bugs-list mailin

[issue13868] Add hyphen doc fix

Boštjan Mejak added the comment: Kiss my ball sac! -- ___ Python tracker <http://bugs.python.org/issue13868> ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue13919] kiss my ball sac

Changes by Boštjan Mejak : -- assignee: docs@python components: Documentation nosy: Retro, docs@python priority: normal severity: normal status: open title: kiss my ball sac type: enhancement versions: Python 2.7 ___ Python tracker <h

[issue13920] intern() doc wrong spelling

Changes by Boštjan Mejak : -- hgrepos: -110 ___ Python tracker <http://bugs.python.org/issue13920> ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue13920] intern() doc wrong spelling

New submission from Boštjan Mejak : http://docs.python.org/library/functions.html#intern Visit the upper link andewsqEz80olp -- assignee: docs@python components: Documentation hgrepos: 110 messages: 152435 nosy: Retro, docs@python priority: normal severity: normal status: open title

[issue13920] intern() doc wrong spelling

Boštjan Mejak added the comment: http://docs.python.org/library/functions.html#intern Visit the upper link and fix 2 words that say "compare" to "comparison". Hint: "blah blah blah pointer compare ... string compare ..." --

[issue13920] intern() doc wrong spelling

Changes by Boštjan Mejak : -- type: -> enhancement ___ Python tracker <http://bugs.python.org/issue13920> ___ ___ Python-bugs-list mailing list Unsubscri

[issue37295] Possible optimizations for math.comb()

Boštjan Mejak added the comment: Performance improvements is what a beta build exists for in the first place. -- nosy: +PedanticHacker ___ Python tracker <https://bugs.python.org/issue37

[issue35309] Typo in urllib.request warning: cpath → capath

Boštjan Mejak added the comment: Created a PR based on this issue. See: https://github.com/python/cpython/pull/10699 -- nosy: +PedanticHacker ___ Python tracker <https://bugs.python.org/issue35

[issue35309] Typo in urllib.request warning: cpath → capath

Change by Boštjan Mejak : -- keywords: +patch pull_requests: +9952 stage: -> patch review ___ Python tracker <https://bugs.python.org/issue35309> ___ ___ Py

[issue24452] Make webbrowser support Chrome on Mac OS X

Boštjan Mejak added the comment: I have Windows 10, 64-bit, and Python 3.6.1, 64-bit, and the code still does not work! >>> import webbrowser >>> webbrowser.get("chrome") Traceback (most recent call last): File "", line 1, in File "C:\Program F

[issue8232] webbrowser.open incomplete on Windows

Boštjan Mejak added the comment: I have Windows 10, 64-bit, and Python 3.6.1, 64-bit, and the code still does not work! >>> import webbrowser >>> webbrowser.get("chrome") Traceback (most recent call last): File "", line 1, in File "C:\Program F

[issue18350] Python 3 unittest framework broken?

New submission from Boštjan Mejak: I fired up the test suite runtests.py of wxPython Phoenix and I get this: File "C:\Program Files\Python 3.3.2\lib\unittest\runner.py", line 63, in addSuccess self.stream.write('.') TypeError: 'str' does not support the buf

[issue18350] Python 3 unittest framework broken?

Boštjan Mejak added the comment: So how exactly can this critical line of code (that you posted) be fixed to make running wxPython Phoenix tests work? -- ___ Python tracker <http://bugs.python.org/issue18

[issue18350] Python 3 unittest framework broken?

Boštjan Mejak added the comment: By "output stream should be a text file", have you ment the line should be self.stream = unittest.runner._WriteInDecorator(StringIO()) Can you provide me a little hint so that I can make a patch for the wxPy

[issue20975] Python 3.4 build info wrong in code snippet

New submission from Boštjan Mejak: Notice the wrong build info of Python 3.4 interpreter in the first code snippet at http://docs.python.org/3/tutorial/interpreter.html#interactive-mode. I know this snippet is just an example to show what does executing the command python3.4 do, but still

[issue20975] Python 3.4 build info wrong in code snippet

Boštjan Mejak added the comment: I would change only the date and time. There was no Python 3.4 back in 2012 so at least change the year. Well, my recommendation is this: Python 3.4.0 (v3.4.0:04f714765c13, Mar 16 2014, 19:25:23) [MSC v.1600 64 bit (AMD64)] on win32 Type "help",

[issue20942] _frozen_importlib should not have a __file__ attribute

Boštjan Mejak added the comment: I would say go for it. I don't think anyone's code would break. Anyway, if people see that something in the new version of Python breaks their code, they down-grade; otherwise they read the changelog and fix their code accordingly. So no wo

[issue20942] _frozen_importlib should not have a __file__ attribute

Boštjan Mejak added the comment: This patch can easily be incorporated into Python 3.4.1. It doesn't break backwards compatibility. -- nosy: +Zvezdoslovec versions: +Python 3.4 ___ Python tracker <http://bugs.python.org/is

[issue20942] _frozen_importlib should not have a __file__ attribute

Boštjan Mejak added the comment: I'm setting Python 3.4 to also be affected by this issue. Thank you, Brett, for making the patch. I hope this gets commited soon. -- versions: +Python 3.4 ___ Python tracker <http://bugs.python.org/is

[issue20942] _frozen_importlib should not have a __file__ attribute

Boštjan Mejak added the comment: Haven't we forget something in the patch for the docs? + .. versionchanged:: 3.5 + The ``__file__`` attribute is no longer set on the module. Where's 3.4 mentioned? Should we add the mention? Like... + .. versioncha

[issue20942] _frozen_importlib should not have a __file__ attribute

Boštjan Mejak added the comment: No one interested in fixing this anymore, despite the patch and all? -- ___ Python tracker <http://bugs.python.org/issue20

[issue21174] A typo in the docs for "exception GeneratorExit"

New submission from Boštjan Mejak: The docs for the exception GeneratorExit starts like this: Raise when a generator‘s close() method is called. The sentece should start with the first word "Raise" to say "Raised". You can find this particular doc sentence

[issue29647] Python 3.6.0

New submission from Boštjan Mejak: I managed to create an app that crashes the latest stable version of Python, that is 3.6.0 at the time of this writing. My application is written in Python using wxPython Phoenix 3rd-party GUI library/toolkit. I am running Windows 10 Home 64-bit version OS

[issue24453] A typo of doubled "the" words in the doc (easy fix)

New submission from Boštjan Mejak: https://docs.python.org/3.4/library/webbrowser.html#module-webbrowser Visit the link and read the first sentence of the 3rd paragraph. You'll notice that there are two "the" words by the end of that sentence. That's obviously a typo. Ple

[issue24452] Make webbrowser support Chrome on Mac OS X

Boštjan Mejak added the comment: I must add that it doesn't work on Windows 7, Python 3.4.3, either. I do have chrome.exe on the %PATH% and executing 'chrome' in Windows Command Prompt opens up the Chrome browser nicely, but it doesn't work so nicely by doing this

[issue8232] webbrowser.open incomplete on Windows

Boštjan Mejak added the comment: I agree with Arfrever Frehtes Taifersar Arahesis (oh my god, you have the longest name, dude!) to rename the class WinFireFox() to WinFirefox(). Okay, so since the branch '3.5' already got its patch webbrowserfix6 applied -- are you, Brandon Milam,

[issue8232] webbrowser.open incomplete on Windows

Boštjan Mejak added the comment: Now that this bug is completely fixed, can you backport this to the '3.4' branch, so that we'll be able to use webbrowser. get() in Python 3.4.4 when it becomes available? -- ___ Python

<    1   2   3   >