[issue43094] sqlite3.create_function takes parameter named narg, not num_params

2021-02-01 Thread Nicholas Chammas
New submission from Nicholas Chammas : The doc for sqlite3.create_function shows the signature as follows: https://docs.python.org/3.9/library/sqlite3.html#sqlite3.Connection.create_function ``` create_function(name, num_params, func, *, deterministic=False) ``` But it appears

[issue20039] Missing documentation for argparse.ArgumentTypeError

2020-03-10 Thread Nicholas Chammas
Nicholas Chammas added the comment: Just a note that I also went looking for the docs for argparse.ArgumentTypeError after coming across it in this (highly viewed) post: https://stackoverflow.com/a/14117511/877069 -- nosy: +nchammas ___ Python

[issue34713] csvwriter.writerow()'s return type is undocumented

2019-03-13 Thread Nicholas Chammas
Nicholas Chammas added the comment: Nope, go ahead. -- ___ Python tracker <https://bugs.python.org/issue34713> ___ ___ Python-bugs-list mailing list Unsub

[issue34713] csvwriter.writerow()'s return type is undocumented

2018-09-17 Thread Nicholas Chammas
Nicholas Chammas added the comment: Looks like it's bytes written, not characters: ``` >>> import csv >>> with open('test.csv', 'w', newline='') as csv_file: ... csv_writer = csv.writer( ... csv_file, ... dialect='unix', ... ) ... csv_writer.wr

[issue34713] csvwriter.writerow()'s return type is undocumented

2018-09-17 Thread Nicholas Chammas
New submission from Nicholas Chammas : It _looks_ like csvwriter.writerow() returns the number of bytes (or is it characters?) written. However, there is no documentation of this: https://docs.python.org/3.7/library/csv.html#csv.csvwriter.writerow Is this behavior part of the method's

[issue22269] Resolve distutils option conflicts with priorities

2018-05-13 Thread Nicholas Chammas
Change by Nicholas Chammas <nicholas.cham...@gmail.com>: -- nosy: +nchammas ___ Python tracker <rep...@bugs.python.org> <https://bugs.python

[issue26463] asyncio-related (?) segmentation fault

2016-03-01 Thread Nicholas Chammas
Nicholas Chammas added the comment: Thanks for the tip. Enabling the fault handler reveals that the crash is happening from the Cryptography library. I'll move this issue there. Thank you. -- resolution: -> not a bug status: open -> closed Added file: http://bugs.python.org/fil

[issue26463] asyncio-related (?) segmentation fault

2016-02-29 Thread Nicholas Chammas
Changes by Nicholas Chammas <nicholas.cham...@gmail.com>: Added file: http://bugs.python.org/file42052/stacktrace.txt ___ Python tracker <rep...@bugs.python.org> <http://bugs.python

[issue26463] asyncio-related (?) segmentation fault

2016-02-29 Thread Nicholas Chammas
New submission from Nicholas Chammas: Python 3.5.1, OS X 10.11.3. I have an application that uses asyncio and Cryptography (via the AsyncSSH library). Cryptography has some parts written in C, I believe. I'm testing my application by sending a keyboard interrupt while 2 tasks are working. My

[issue8706] accept keyword arguments on most base type methods and builtins

2016-02-14 Thread Nicholas Chammas
Changes by Nicholas Chammas <nicholas.cham...@gmail.com>: -- nosy: +Nicholas Chammas ___ Python tracker <rep...@bugs.python.org> <http://bugs.pytho

[issue26334] bytes.translate() doesn't take keyword arguments; docs suggests it does

2016-02-12 Thread Nicholas Chammas
Nicholas Chammas added the comment: Yep, you're right. I'm just understanding now that we have lots of methods defined in C which have signatures like this. Is there an umbrella issue, perhaps, that covers adding support for keyword-based arguments to functions defined in C, like `translate

[issue26334] bytes.translate() doesn't take keyword arguments; docs suggests it does

2016-02-10 Thread Nicholas Chammas
Nicholas Chammas added the comment: So you're saying if `bytes.translate()` accepted keyword arguments, its signature would look something like this? ``` bytes.translate(table, delete=None) ``` I guess I was under the mistaken assumption that argument names in the docs always matched keyword

[issue26334] bytes.translate() doesn't take keyword arguments; docs suggests it does

2016-02-10 Thread Nicholas Chammas
New submission from Nicholas Chammas: The docs for `bytes.translate()` [0] show the following signature: ``` bytes.translate(table[, delete]) ``` However, calling this method with keyword arguments yields: ``` >>> b''.translate(table='la table', delete=b'delete') Traceback (most re

[issue26188] Provide more helpful error message when `await` is called inside non-`async` method

2016-02-02 Thread Nicholas Chammas
Nicholas Chammas added the comment: Related discussions about providing more helpful syntax error messages: * http://bugs.python.org/issue1634034 * http://bugs.python.org/issue400734 * http://bugs.python.org/issue20608 >From the discussion on issue1634034, it looks like providing bet

[issue7850] platform.system() should be "macosx" instead of "Darwin" on OSX

2016-01-30 Thread Nicholas Chammas
Nicholas Chammas added the comment: As of Python 3.5.1 [0], it looks like 1) the `aliased` and `terse` parameters of `platform.platform()` are documented to take integers instead of booleans (contrary to what Marc-Andre requested), and 2) calling `platform.platform()` with `aliased` set

[issue26188] Provide more helpful error message when `await` is called inside non-`async` method

2016-01-23 Thread Nicholas Chammas
New submission from Nicholas Chammas: Here is the user interaction: ```python $ python3 Python 3.5.1 (default, Dec 7 2015, 21:59:10) [GCC 4.2.1 Compatible Apple LLVM 7.0.0 (clang-700.1.76)] on darwin Type "help", "copyright", "credits" or "license&qu

[issue26035] traceback.print_tb() takes `tb`, not `traceback` as a keyword argument

2016-01-06 Thread Nicholas Chammas
New submission from Nicholas Chammas: Here is traceback.print_tb()'s signature [0]: ``` def print_tb(tb, limit=None, file=None): ``` However, its documentation reads [1]: ``` .. function:: print_tb(traceback, limit=None, file=None) ``` Did the keyword argument change recently

[issue25768] compileall functions do not document or test return values

2015-12-20 Thread Nicholas Chammas
Nicholas Chammas added the comment: Alright, sounds good to me. Thank you for guiding me through the process! -- ___ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/i

[issue25768] compileall functions do not document or test return values

2015-12-19 Thread Nicholas Chammas
Nicholas Chammas added the comment: Ah, I see. The setup/teardown stuff runs for each test. So this is what I did: * Added a method to add a "bad" source file to the source directory. It gets cleaned up with the existing teardown method. * Used test_importlib to temporarily mutat

[issue25768] compileall functions do not document or test return values

2015-12-09 Thread Nicholas Chammas
Nicholas Chammas added the comment: I've added the tests as we discussed. A couple of comments: * I found it difficult to reuse the existing setUp() code so had to essentially repeat a bunch of very similar code to create "bad" files. Let me know if you think there is a better

[issue24931] _asdict breaks when inheriting from a namedtuple

2015-12-08 Thread Nicholas Chammas
Nicholas Chammas added the comment: I know. I came across this issue after upgrading to the 3.5.1 release and seeing that vars(namedtuple) didn't work anymore. I looked through the changelog [0] for an explanation of why that might be and couldn't find one, so I posted that question on Stack

[issue24931] _asdict breaks when inheriting from a namedtuple

2015-12-08 Thread Nicholas Chammas
Nicholas Chammas added the comment: Should this change be called out in the 3.5.1 release docs? It makes some code that works on 3.5.0 break in 3.5.1. See: http://stackoverflow.com/q/34166469/877069 -- nosy: +Nicholas Chammas ___ Python tracker

[issue25768] compileall functions do not document or test return values

2015-12-05 Thread Nicholas Chammas
Nicholas Chammas added the comment: Absolutely. I'll add a "bad source file" to `setUp()` [0] and check return values as part of the existing checks in `test_compile_files()` [1]. Does that sound like a good plan to you? Also, I noticed that `compile_path()` has no tests. Sho

[issue25768] compileall functions do not document return values

2015-12-01 Thread Nicholas Chammas
Nicholas Chammas added the comment: OK, here's a patch. I reviewed the doc style guide [0] but I'm not 100% sure if I'm using the appropriate tense. There are also a couple of lines that go a bit over 80 characters, but the file already had a few of those. Am happy to make any adjustments

[issue25768] compileall functions do not document return values

2015-12-01 Thread Nicholas Chammas
Nicholas Chammas added the comment: And I just signed the contributor agreement. (Some banner showed up when I attached the patch to this issue asking me to do so.) -- ___ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/i

[issue25768] compileall functions do not document return values

2015-12-01 Thread Nicholas Chammas
Nicholas Chammas added the comment: :thumbsup: Take your time. -- ___ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue25768> ___ ___ Pyth

[issue25775] Bug tracker emails go to spam

2015-12-01 Thread Nicholas Chammas
New submission from Nicholas Chammas: Not sure where to report this. Is there a component for the bug tracker itself? Anyway, Gmail sends emails from this bug tracker to spam and flags each one with the following message: > Why is this message in Spam? It is in violation of Googl

[issue25768] compileall functions do not document return values

2015-12-01 Thread Nicholas Chammas
Nicholas Chammas added the comment: Oh derp. It appears this is dup of issue24386. Apologies. -- status: open -> closed ___ Python tracker <rep...@bugs.python.org> <http://bugs.python.or

[issue25768] compileall functions do not document return values

2015-12-01 Thread Nicholas Chammas
Nicholas Chammas added the comment: Whoops, wrong issue. Reopening. -- status: closed -> open ___ Python tracker <rep...@bugs.python.org> <http://bugs.python.or

[issue25775] Bug tracker emails go to spam

2015-12-01 Thread Nicholas Chammas
Nicholas Chammas added the comment: Oh derp. It appears this is dup of issue24386. Apologies. -- status: open -> closed ___ Python tracker <rep...@bugs.python.org> <http://bugs.python.or

[issue25768] compileall functions do not document return values

2015-12-01 Thread Nicholas Chammas
Nicholas Chammas added the comment: Exciting! I'm on it. -- ___ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue25768> ___ ___ Pyth

[issue25768] compileall functions do not document return values

2015-11-29 Thread Nicholas Chammas
New submission from Nicholas Chammas: I'm using the public functions of Python's built-in compileall module. https://docs.python.org/3/library/compileall.html#public-functions There doesn't appear to be documentation of what each of these functions returns. I figured out, for example

[issue25284] Spec for BaseEventLoop.run_in_executor(executor, callback, *args) is outdated in documentation

2015-09-30 Thread Nicholas Chammas
Changes by Nicholas Chammas <nicholas.cham...@gmail.com>: -- nosy: +Nicholas Chammas ___ Python tracker <rep...@bugs.python.org> <http://bugs.python

Re: Did the 3.4.4 docs get published early?

2015-06-11 Thread Nicholas Chammas
. Nick On Wed, Jun 10, 2015 at 2:25 PM Nicholas Chammas nicholas.cham...@gmail.com wrote: Also, just replacing the version number in the URL works for the python 3 series (use 3.X even for python 3.0), even farther back than the drop down menu allows. This does not help in this case: https

Did the 3.4.4 docs get published early?

2015-06-10 Thread Nicholas Chammas
For example, here is a New in version 3.4.4 method: https://docs.python.org/3/library/asyncio-task.html#asyncio.ensure_future However, the latest release appears to be 3.4.3: https://www.python.org/downloads/ Is this normal, or did the 3.4.4 docs somehow get published early by mistake? Nick

Re: Did the 3.4.4 docs get published early?

2015-06-10 Thread Nicholas Chammas
(like the one I linked to) are introduced in maintenance versions, it’s probably hard to separate them out into separate branches. Nick ​ On Wed, Jun 10, 2015 at 10:11 AM Nicholas Chammas nicholas.cham...@gmail.com wrote: For example, here is a New in version 3.4.4 method: https

[issue21423] concurrent.futures.ThreadPoolExecutor/ProcessPoolExecutor should accept an initializer argument

2015-03-20 Thread Nicholas Chammas
Changes by Nicholas Chammas nicholas.cham...@gmail.com: -- nosy: +Nicholas Chammas ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue21423