From report at bugs.python.org Sat Aug 1 10:14:56 2015 From: report at bugs.python.org (Ivan Levkivskyi) Date: Sat, 01 Aug 2015 08:14:56 +0000 Subject: [docs] [issue24129] Incorrect (misleading) statement in the execution model documentation In-Reply-To: <1430859119.42.0.185221847455.issue24129@psf.upfronthosting.co.za> Message-ID: <1438416896.36.0.951176442512.issue24129@psf.upfronthosting.co.za> Ivan Levkivskyi added the comment: I am sorry but I still don't get how things are organized here, so pinging this up. What is the next step? Should I wait for another review? ---------- _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Sat Aug 1 10:18:53 2015 From: report at bugs.python.org (Martin Panter) Date: Sat, 01 Aug 2015 08:18:53 +0000 Subject: [docs] [issue24692] types.coroutines() idempotence documentation In-Reply-To: <1437650502.32.0.0288592289227.issue24692@psf.upfronthosting.co.za> Message-ID: <1438417132.9.0.0165772024062.issue24692@psf.upfronthosting.co.za> Martin Panter added the comment: I think you are right that it would be typically used as a decorator. Patch v2 changes it to be defined as a decorator. Not sure what the second part of your comment is referring to. The existing text about lack of __await__() maybe? You still have to have something (such as ?asyncio?) drive the top-level coroutine. So that is a third thing users have to do with them. Passing a coroutine to ?await? does not magically make it go, it just becomes a subordinate of the outer coroutine. ---------- Added file: http://bugs.python.org/file40092/coro-idempotent.v2.patch _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Sat Aug 1 11:48:31 2015 From: report at bugs.python.org (karl) Date: Sat, 01 Aug 2015 09:48:31 +0000 Subject: [docs] [issue24772] Smaller viewport shifts the "expand left menu" character into the text Message-ID: <1438422511.74.0.548589592521.issue24772@psf.upfronthosting.co.za> New submission from karl: Adding the following to basic.css: ```css dl { margin-bottom: 15px; word-wrap: break-word; } ``` will solve the issue. See https://github.com/webcompat/web-bugs/issues/1479 ---------- assignee: docs at python components: Documentation messages: 247803 nosy: docs at python, karlcow priority: normal severity: normal status: open title: Smaller viewport shifts the "expand left menu" character into the text _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Sat Aug 1 12:46:41 2015 From: report at bugs.python.org (Serhiy Storchaka) Date: Sat, 01 Aug 2015 10:46:41 +0000 Subject: [docs] [issue24772] Smaller viewport shifts the "expand left menu" character into the text In-Reply-To: <1438422511.74.0.548589592521.issue24772@psf.upfronthosting.co.za> Message-ID: <1438426001.3.0.343098163957.issue24772@psf.upfronthosting.co.za> Changes by Serhiy Storchaka : ---------- nosy: +georg.brandl _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Sun Aug 2 16:17:55 2015 From: report at bugs.python.org (Guido van Rossum) Date: Sun, 02 Aug 2015 14:17:55 +0000 Subject: [docs] [issue24272] PEP 484 docs In-Reply-To: <1432415368.91.0.945654992881.issue24272@psf.upfronthosting.co.za> Message-ID: <1438525075.29.0.527161329958.issue24272@psf.upfronthosting.co.za> Guido van Rossum added the comment: This should probably be committed before RC1 -- it's better than nothing! ---------- priority: normal -> release blocker _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Sun Aug 2 16:37:53 2015 From: report at bugs.python.org (Ivan Levkivskyi) Date: Sun, 02 Aug 2015 14:37:53 +0000 Subject: [docs] [issue24272] PEP 484 docs In-Reply-To: <1432415368.91.0.945654992881.issue24272@psf.upfronthosting.co.za> Message-ID: <1438526273.49.0.938294531862.issue24272@psf.upfronthosting.co.za> Ivan Levkivskyi added the comment: Is anyone working on this right now? If not, I could implement the comments by Guido to the latest patch by Daniel. ---------- _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Sun Aug 2 17:00:37 2015 From: report at bugs.python.org (Daniel Andrade Groppe) Date: Sun, 02 Aug 2015 15:00:37 +0000 Subject: [docs] [issue24272] PEP 484 docs In-Reply-To: <1432415368.91.0.945654992881.issue24272@psf.upfronthosting.co.za> Message-ID: <1438527637.76.0.0773478045161.issue24272@psf.upfronthosting.co.za> Daniel Andrade Groppe added the comment: I dropped the ball here. The last message from the review system was misclassified by Gmail as spam... Sorry about that. I can take a look at this tonight but if anyone can address the comments earlier, go for it. ---------- _______________________________________ Python tracker _______________________________________ From levkivskyi at gmail.com Sun Aug 2 22:57:25 2015 From: levkivskyi at gmail.com (levkivskyi at gmail.com) Date: Sun, 02 Aug 2015 20:57:25 -0000 Subject: [docs] PEP 484 docs (issue 24272) Message-ID: <20150802205725.31954.50497@psf.upfronthosting.co.za> http://bugs.python.org/review/24272/diff/14930/Doc/library/typing.rst File Doc/library/typing.rst (right): http://bugs.python.org/review/24272/diff/14930/Doc/library/typing.rst#newcode31 Doc/library/typing.rst:31: Url = str On 2015/06/03 02:28:22, gvanrossum wrote: > Maybe use a more complex example, e.g. > > Vector = List[float] > > ? (It's okay if that's a forward reference to syntax that hasn't been explained > yet.) Done. http://bugs.python.org/review/24272/diff/14930/Doc/library/typing.rst#newcode33 Doc/library/typing.rst:33: Callable On 2015/06/03 02:28:23, gvanrossum wrote: > Can you also document the special form Callable[..., ]? Here "..." is a > literal ellipsis, and the meaning is "don't type-check the args" (it's described > in the PEP). Done. http://bugs.python.org/review/24272/diff/14930/Doc/library/typing.rst#newcode59 Doc/library/typing.rst:59: from typing import Mapping, Set On 2015/06/03 02:28:23, gvanrossum wrote: > Unfortunately we renamed the ABC Set to AbstractSet, and Set refers to (the > generic variant of) the concrete type 'set'. Maybe change the example to use > Sequence, which is an ABC? (To clarify, the example with Set[Employee] works, > but it isn't using an ABC.) Done. http://bugs.python.org/review/24272/diff/14930/Doc/library/typing.rst#newcode80 Doc/library/typing.rst:80: A user-defined class can be defined as a generic. On 2015/06/03 02:28:23, gvanrossum wrote: > "a generic" -> either "generic" or "a generic class". Done. http://bugs.python.org/review/24272/diff/14930/Doc/library/typing.rst#newcode84 Doc/library/typing.rst:84: from typing import TypeVar, Generic On 2015/06/03 02:28:23, gvanrossum wrote: > The example should also include "from logging import Logger". Done. http://bugs.python.org/review/24272/diff/14930/Doc/library/typing.rst#newcode103 Doc/library/typing.rst:103: self.logger.info('{}: {}'.format(self.name message)) On 2015/06/03 02:28:23, gvanrossum wrote: > Missing comma after self.name. Done. http://bugs.python.org/review/24272/diff/14930/Doc/library/typing.rst#newcode118 Doc/library/typing.rst:118: be constrained:: On 2015/06/03 02:28:23, gvanrossum wrote: > The mention of "constrained" here dangles a bit -- there's no example > immediately following of a constrained type variable. (I think it's different > in the PEP.) Done. http://bugs.python.org/review/24272/diff/14930/Doc/library/typing.rst#newcode166 Doc/library/typing.rst:166: When the type of a value is object, the type checker will reject almost all On 2015/06/03 02:28:23, gvanrossum wrote: > I'd use `object`. Done. http://bugs.python.org/review/24272/diff/14930/Doc/library/typing.rst#newcode173 Doc/library/typing.rst:173: Version and platform checking On 2015/06/03 02:28:23, gvanrossum wrote: > Drop this section. Done. http://bugs.python.org/review/24272/diff/14930/Doc/library/typing.rst#newcode196 Doc/library/typing.rst:196: def foo(x: AnyStr, y: AnyStr = ...) -> AnyStr: ... On 2015/06/03 02:28:23, gvanrossum wrote: > There is no definition of AnyStr, so this dangles a bit. Done. http://bugs.python.org/review/24272/diff/14930/Doc/library/typing.rst#newcode204 Doc/library/typing.rst:204: .. class:: Any(Final, metaclass=AnyMeta, _root=True) On 2015/06/03 02:28:23, gvanrossum wrote: > Don't mention the base classes. This also applies below. Done. http://bugs.python.org/review/24272/diff/14930/Doc/library/typing.rst#newcode208 Doc/library/typing.rst:208: * Any object is an instance of Any. On 2015/06/03 02:28:23, gvanrossum wrote: > I'd use `Any` for all places where the word "Any" refers to the special object > `Any`. Done. http://bugs.python.org/review/24272/diff/14930/Doc/library/typing.rst#newcode229 Doc/library/typing.rst:229: '''Return a list containing n references to x.''' On 2015/06/03 02:28:23, gvanrossum wrote: > I strongly prefer """ for docstrings. Done. http://bugs.python.org/review/24272/diff/14930/Doc/library/typing.rst#newcode237 Doc/library/typing.rst:237: of (str, str) -> str and (bytes, bytes) -> bytes. Also note On 2015/06/03 02:28:23, gvanrossum wrote: > You're slacking on the backticks here. :-) Done. http://bugs.python.org/review/24272/diff/14930/Doc/library/typing.rst#newcode242 Doc/library/typing.rst:242: issubclass(C, T) is true for any class C, and issubclass(str, A) On 2015/06/03 02:28:23, gvanrossum wrote: > Actually, issubclass() involving type variables or other special objects will > probably start failing too in one of the next betas. Perhaps it's better to say > something like "you shouldn't use these". Done. http://bugs.python.org/review/24272/diff/14930/Doc/library/typing.rst#newcode250 Doc/library/typing.rst:250: Type variables can be introspected. e.g.:: On 2015/06/03 02:28:23, gvanrossum wrote: > I prefer not to document this for now. Done. http://bugs.python.org/review/24272/diff/14930/Doc/library/typing.rst#newcode258 Doc/library/typing.rst:258: .. class:: Union(Final, metaclass=UnionMeta, _root=True) On 2015/06/03 02:28:23, gvanrossum wrote: > Again, please don't list the base classes. (Same for every class below). I removed base classes, except for a few at the end, where they could be helpful, (like Generic[T_co], etc). http://bugs.python.org/review/24272/diff/14930/Doc/library/typing.rst#newcode266 Doc/library/typing.rst:266: * None as an argument is a special case and is replaced by On 2015/06/03 02:28:23, gvanrossum wrote: > This is not unique to union -- this applies everywhere. So probably move it up > ahead. Done. http://bugs.python.org/review/24272/diff/14930/Doc/library/typing.rst#newcode285 Doc/library/typing.rst:285: * When two arguments have a subclass relationship, the least On 2015/06/03 02:28:23, gvanrossum wrote: > We're on thin ice with this bullet. I'd like to drop it. (The PEP doesn't say > this.) Done. http://bugs.python.org/review/24272/diff/14930/Doc/library/typing.rst#newcode294 Doc/library/typing.rst:294: * Corollary: if Any is present it is the sole survivor, e.g.:: On 2015/06/03 02:28:23, gvanrossum wrote: > I'd remove "Corollary:" -- this is just another rule. Done. http://bugs.python.org/review/24272/diff/14930/Doc/library/typing.rst#newcode298 Doc/library/typing.rst:298: * Similar for object:: On 2015/06/03 02:28:23, gvanrossum wrote: > I'd drop this too. Done. http://bugs.python.org/review/24272/diff/14930/Doc/library/typing.rst#newcode302 Doc/library/typing.rst:302: * To cut a tie: `Union[object, Any] == Union[Any, object] == Any`. On 2015/06/03 02:28:23, gvanrossum wrote: > Drop this too. Done. http://bugs.python.org/review/24272/diff/14930/Doc/library/typing.rst#newcode318 Doc/library/typing.rst:318: Tuple type; Tuple[X, Y] is the cross-product type of X and Y. On 2015/06/03 02:28:23, gvanrossum wrote: > I'd drop the "cross-product" concept -- it's very type-theoretic. I'd just say > this is the type of a tuple of two items with the first item of type X and the > second of type Y. Done. http://bugs.python.org/review/24272/diff/14930/Doc/library/typing.rst#newcode324 Doc/library/typing.rst:324: To specify a variable-length tuple of homogeneous type, use `Sequence[T]`. On 2015/06/03 02:28:23, gvanrossum wrote: > The PEP actually also supports Tuple[t, ...]. (And I'd use a lowercase t because > it doesn't have to be a type variable. Maybe use Tuple[int, ...] as an example. Done. http://bugs.python.org/review/24272/diff/14930/Doc/library/typing.rst#newcode335 Doc/library/typing.rst:335: such function types are rarely used as callback types. On 2015/06/03 02:28:23, gvanrossum wrote: > But do add Callable[..., t] as a way to spell callable of any args returning t. > > Also note that plain Callable is equivalent to Callable[..., Any]. Done. http://bugs.python.org/review/24272/diff/14930/Doc/library/typing.rst#newcode337 Doc/library/typing.rst:337: .. class:: Generic(metaclass=GenericMeta) On 2015/06/03 02:28:23, gvanrossum wrote: > This looks (mostly?) redundant with the earlier discussion of Generic. I think it is OK to keep this section, although it is a bit redundant, indeed. http://bugs.python.org/review/24272/diff/14930/Doc/library/typing.rst#newcode352 Doc/library/typing.rst:352: def lookup_name(mapping: Mapping, key: KT, default: VT) -> VT: On 2015/06/03 02:28:23, gvanrossum wrote: > Actually we changed our mind about this and you must write Mapping[KT, VT] here > (essentially making this the same as the next example). Done. http://bugs.python.org/review/24272/diff/14930/Doc/library/typing.rst#newcode445 Doc/library/typing.rst:445: .. function:: get_type_hints(obj, globalns=None, localns=None) On 2015/06/03 02:28:23, gvanrossum wrote: > I prefer not to document globalns/localns at this time. Done. http://bugs.python.org/review/24272/diff/14930/Doc/library/typing.rst#newcode453 Doc/library/typing.rst:453: .. warning:: On 2015/06/03 02:28:23, gvanrossum wrote: > Just drop this warning. Done. http://bugs.python.org/review/24272/diff/14930/Doc/library/typing.rst#newcode469 Doc/library/typing.rst:469: .. function:: overload(func) On 2015/06/03 02:28:23, gvanrossum wrote: > Consider leaving this out. Done. http://bugs.python.org/review/24272/ From report at bugs.python.org Sun Aug 2 22:59:04 2015 From: report at bugs.python.org (Ivan Levkivskyi) Date: Sun, 02 Aug 2015 20:59:04 +0000 Subject: [docs] [issue24272] PEP 484 docs In-Reply-To: <1432415368.91.0.945654992881.issue24272@psf.upfronthosting.co.za> Message-ID: <1438549144.37.0.445317966184.issue24272@psf.upfronthosting.co.za> Ivan Levkivskyi added the comment: New version of the patch by Daniel, latest comments by Guido are taken into account. ---------- Added file: http://bugs.python.org/file40108/typing_doc_v3.patch _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Mon Aug 3 11:44:49 2015 From: report at bugs.python.org (Mark Shannon) Date: Mon, 03 Aug 2015 09:44:49 +0000 Subject: [docs] [issue24272] PEP 484 docs In-Reply-To: <1432415368.91.0.945654992881.issue24272@psf.upfronthosting.co.za> Message-ID: <1438595089.26.0.1896873912.issue24272@psf.upfronthosting.co.za> Changes by Mark Shannon : ---------- nosy: +Mark.Shannon _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Mon Aug 3 13:44:43 2015 From: report at bugs.python.org (=?utf-8?q?Alex_Gr=C3=B6nholm?=) Date: Mon, 03 Aug 2015 11:44:43 +0000 Subject: [docs] [issue24785] Document asyncio.futures.wrap_future() Message-ID: <1438602283.27.0.137322848878.issue24785@psf.upfronthosting.co.za> New submission from Alex Gr?nholm: Since Python 3.5 will not support awaiting for concurrent.futures.Futures natively, one has to use the asyncio.futures.wrap_future() function in coroutines like this: async def foo(): await wrap_future(executor.submit(...)) The wrap_future() function is, however, not mentioned in the asyncio documentation. It should be, in order for the standard library to provide the above crutch until proper support arrives in 3.6. ---------- assignee: docs at python components: Documentation messages: 247924 nosy: alex.gronholm, docs at python priority: normal severity: normal status: open title: Document asyncio.futures.wrap_future() type: enhancement versions: Python 3.5 _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Mon Aug 3 14:04:02 2015 From: report at bugs.python.org (Berker Peksag) Date: Mon, 03 Aug 2015 12:04:02 +0000 Subject: [docs] [issue24785] Document asyncio.futures.wrap_future() In-Reply-To: <1438602283.27.0.137322848878.issue24785@psf.upfronthosting.co.za> Message-ID: <1438603442.88.0.235969192647.issue24785@psf.upfronthosting.co.za> Berker Peksag added the comment: This is a duplicate of issue 24755. ---------- nosy: +berker.peksag resolution: -> duplicate stage: -> resolved status: open -> closed superseder: -> asyncio.wrap_future undocumented _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Mon Aug 3 14:31:27 2015 From: report at bugs.python.org (Yury Selivanov) Date: Mon, 03 Aug 2015 12:31:27 +0000 Subject: [docs] [issue24785] Document asyncio.futures.wrap_future() In-Reply-To: <1438602283.27.0.137322848878.issue24785@psf.upfronthosting.co.za> Message-ID: <1438605087.59.0.52228142297.issue24785@psf.upfronthosting.co.za> Changes by Yury Selivanov : ---------- nosy: +yselivanov _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Mon Aug 3 14:31:40 2015 From: report at bugs.python.org (Yury Selivanov) Date: Mon, 03 Aug 2015 12:31:40 +0000 Subject: [docs] [issue24755] asyncio.wrap_future undocumented In-Reply-To: <1438250618.09.0.00442439827356.issue24755@psf.upfronthosting.co.za> Message-ID: <1438605100.02.0.745540587772.issue24755@psf.upfronthosting.co.za> Changes by Yury Selivanov : ---------- nosy: +yselivanov _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Mon Aug 3 15:14:59 2015 From: report at bugs.python.org (=?utf-8?q?Alex_Gr=C3=B6nholm?=) Date: Mon, 03 Aug 2015 13:14:59 +0000 Subject: [docs] [issue24755] asyncio.wrap_future undocumented In-Reply-To: <1438250618.09.0.00442439827356.issue24755@psf.upfronthosting.co.za> Message-ID: <1438607699.39.0.502482226509.issue24755@psf.upfronthosting.co.za> Changes by Alex Gr?nholm : ---------- nosy: +alex.gronholm _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Mon Aug 3 19:03:08 2015 From: report at bugs.python.org (R. David Murray) Date: Mon, 03 Aug 2015 17:03:08 +0000 Subject: [docs] [issue24129] Incorrect (misleading) statement in the execution model documentation In-Reply-To: <1430859119.42.0.185221847455.issue24129@psf.upfronthosting.co.za> Message-ID: <1438621388.49.0.129090972248.issue24129@psf.upfronthosting.co.za> R. David Murray added the comment: Your ping after a month is very appropriate. It looks like yes, this is waiting for another review. Based on the fact that the previous patches were reviewed by core devs and you have responded, I'm moving it to 'commit review', but I haven't looked at the patch myself. ---------- stage: -> commit review versions: +Python 3.6 _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Mon Aug 3 19:31:42 2015 From: report at bugs.python.org (paul j3) Date: Mon, 03 Aug 2015 17:31:42 +0000 Subject: [docs] [issue24647] Document argparse.REMAINDER as being equal to "..." In-Reply-To: <1437079645.1.0.921184801927.issue24647@psf.upfronthosting.co.za> Message-ID: <1438623102.25.0.1987081501.issue24647@psf.upfronthosting.co.za> paul j3 added the comment: Also, argparse.PARSER is '+...' '? * +' have closely matched analogs in regex patterns. '...' and '+...' do not. So Python users will have an intuitive idea of what "nargs='*'" means. "nargs='...'" is not so obvious. As a general rule, the document does not expose the values of module constants. ---------- nosy: +paul.j3 _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Mon Aug 3 22:31:26 2015 From: report at bugs.python.org (Guido van Rossum) Date: Mon, 03 Aug 2015 20:31:26 +0000 Subject: [docs] [issue24272] PEP 484 docs In-Reply-To: <1432415368.91.0.945654992881.issue24272@psf.upfronthosting.co.za> Message-ID: <1438633886.64.0.162160610591.issue24272@psf.upfronthosting.co.za> Guido van Rossum added the comment: Thank you Ivan! I am going to commit this, it's much better than the two lines we had before. :-) There's still a lot of work left to do -- towards the end there are many classes without description. Maybe you and Daniel can divide up the work for those? We can always iterate (even during the release candidates and even after the 3.5.0 release). ---------- _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Mon Aug 3 23:00:31 2015 From: report at bugs.python.org (Robert Collins) Date: Mon, 03 Aug 2015 21:00:31 +0000 Subject: [docs] [issue23725] update tempfile docs to say that TemporaryFile is secure In-Reply-To: <1426878892.3.0.689958999466.issue23725@psf.upfronthosting.co.za> Message-ID: <1438635631.3.0.482335121591.issue23725@psf.upfronthosting.co.za> Changes by Robert Collins : ---------- versions: +Python 3.6 _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Mon Aug 3 23:11:07 2015 From: report at bugs.python.org (Robert Collins) Date: Mon, 03 Aug 2015 21:11:07 +0000 Subject: [docs] [issue23725] update tempfile docs to say that TemporaryFile is secure In-Reply-To: <1426878892.3.0.689958999466.issue23725@psf.upfronthosting.co.za> Message-ID: <1438636267.34.0.976267685185.issue23725@psf.upfronthosting.co.za> Robert Collins added the comment: I'm not 100% sure that tempfile.tempdir should be deprecated. Its much less convenient to control global behaviour with that. I agree that mktemp should be. I've updated the patch though. ---------- nosy: +rbcollins Added file: http://bugs.python.org/file40120/issue-23725.patch _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Tue Aug 4 00:11:54 2015 From: report at bugs.python.org (R. David Murray) Date: Mon, 03 Aug 2015 22:11:54 +0000 Subject: [docs] [issue23725] update tempfile docs to say that TemporaryFile is secure In-Reply-To: <1426878892.3.0.689958999466.issue23725@psf.upfronthosting.co.za> Message-ID: <1438639914.48.0.63156180462.issue23725@psf.upfronthosting.co.za> R. David Murray added the comment: Well, something is wrong, because if we are deprecating :data:`tmpdir` we shouldn't be cross referencing it from the non-deprecated docs. The explanation of how the default value is calculated should be moved up to gettmpdir. My understanding is that now that all functions accept a 'dir' parameter, the tmpdir global was deprecated because global state is bad, and if an application really wants to affect the global state it can use the one of the environment variables that are checked, which is more flexible. ---------- _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Tue Aug 4 00:17:44 2015 From: report at bugs.python.org (Robert Collins) Date: Mon, 03 Aug 2015 22:17:44 +0000 Subject: [docs] [issue23725] update tempfile docs to say that TemporaryFile is secure In-Reply-To: <1426878892.3.0.689958999466.issue23725@psf.upfronthosting.co.za> Message-ID: <1438640264.33.0.463421670436.issue23725@psf.upfronthosting.co.za> Robert Collins added the comment: I can't find any reference to a discussion to deprecate tempdir outside of this issue. Nothing on python-dev/python-ideas/peps. I can see that there's an argument that it should be deprecated, but AFAICT the idea to do so originated here. I'd like to see wider discussion though (because I don't think it makes sense to deprecate it) - its no more or less global than environment variables, its already here as a feature, and its not going to save us code maintenance or bugs if we do deprecate it - and if we are deprecating it, we should be issueing a PendingDeprecation warning at minimum. How about we change the patch to not deprecate it, and either open a new ticket, or let folk that want to deprecate it raise that on the list? ---------- _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Tue Aug 4 00:28:07 2015 From: report at bugs.python.org (=?utf-8?b?SmVzw7pzIENlYSBBdmnDs24=?=) Date: Mon, 03 Aug 2015 22:28:07 +0000 Subject: [docs] [issue24786] Changes in the devguide repository are not published online in HTML Message-ID: <1438640887.59.0.275627512221.issue24786@psf.upfronthosting.co.za> New submission from Jes?s Cea Avi?n: I change content and configuration in the devguide repository and I don't see the changes available in HTML in even after some days. ---------- assignee: docs at python components: Documentation messages: 247961 nosy: docs at python, jcea priority: normal severity: normal status: open title: Changes in the devguide repository are not published online in HTML _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Tue Aug 4 00:35:23 2015 From: report at bugs.python.org (=?utf-8?q?Zbyszek_J=C4=99drzejewski-Szmek?=) Date: Mon, 03 Aug 2015 22:35:23 +0000 Subject: [docs] [issue23725] update tempfile docs to say that TemporaryFile is secure In-Reply-To: <1426878892.3.0.689958999466.issue23725@psf.upfronthosting.co.za> Message-ID: <1438641322.94.0.598719265133.issue23725@psf.upfronthosting.co.za> Zbyszek J?drzejewski-Szmek added the comment: I don't think tempdir should be removed. I just think it should not be used. So what about moving the description of tempdir to the end, as it was in the last patch, but calling the section "Other functions and variables". ---------- _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Tue Aug 4 02:20:26 2015 From: report at bugs.python.org (Robert Collins) Date: Tue, 04 Aug 2015 00:20:26 +0000 Subject: [docs] [issue23725] update tempfile docs to say that TemporaryFile is secure In-Reply-To: <1426878892.3.0.689958999466.issue23725@psf.upfronthosting.co.za> Message-ID: <1438647626.1.0.753782839054.issue23725@psf.upfronthosting.co.za> Robert Collins added the comment: mktemp is clearly insecure. I'd just move the tmpdir up above the Deprecation section start ---------- _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Tue Aug 4 02:25:52 2015 From: report at bugs.python.org (Peter Lovett) Date: Tue, 04 Aug 2015 00:25:52 +0000 Subject: [docs] [issue24021] Add docstring to urllib.urlretrieve In-Reply-To: <1429673026.41.0.442066158913.issue24021@psf.upfronthosting.co.za> Message-ID: <1438647951.99.0.314830431793.issue24021@psf.upfronthosting.co.za> Peter Lovett added the comment: Updated patch to 3.6 urlretrieve now has a decent docstring; this patch just adds a docstring to urlcleanup. ---------- nosy: +PeterLovett versions: +Python 3.6 -Python 2.7 Added file: http://bugs.python.org/file40121/issue-24021.patch _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Tue Aug 4 02:48:22 2015 From: report at bugs.python.org (=?utf-8?q?Zbyszek_J=C4=99drzejewski-Szmek?=) Date: Tue, 04 Aug 2015 00:48:22 +0000 Subject: [docs] [issue23725] update tempfile docs to say that TemporaryFile is secure In-Reply-To: <1426878892.3.0.689958999466.issue23725@psf.upfronthosting.co.za> Message-ID: <1438649301.54.0.0593042714252.issue23725@psf.upfronthosting.co.za> Zbyszek J?drzejewski-Szmek added the comment: Updated version (based on issue-23725.patch from rbcollins): - move tempdir description at the end of the main section, before Examples - do not add my name second time in ACKS ---------- Added file: http://bugs.python.org/file40122/issue-23725.patch _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Tue Aug 4 02:53:41 2015 From: report at bugs.python.org (Roundup Robot) Date: Tue, 04 Aug 2015 00:53:41 +0000 Subject: [docs] [issue24021] Add docstring to urllib.urlretrieve In-Reply-To: <1429673026.41.0.442066158913.issue24021@psf.upfronthosting.co.za> Message-ID: <20150804005338.17717.45829@psf.io> Roundup Robot added the comment: New changeset 659f5adc2354 by Robert Collins in branch '3.4': Issue #24021: docstring for urllib.urlcleanup. https://hg.python.org/cpython/rev/659f5adc2354 New changeset 6fd69aeb8a3b by Robert Collins in branch '3.5': Issue #24021: docstring for urllib.urlcleanup. https://hg.python.org/cpython/rev/6fd69aeb8a3b New changeset 43ed41cdd3c2 by Robert Collins in branch 'default': Issue #24021: docstring for urllib.urlcleanup. https://hg.python.org/cpython/rev/43ed41cdd3c2 ---------- nosy: +python-dev _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Tue Aug 4 02:54:21 2015 From: report at bugs.python.org (Robert Collins) Date: Tue, 04 Aug 2015 00:54:21 +0000 Subject: [docs] [issue24021] Add docstring to urllib.urlretrieve In-Reply-To: <1429673026.41.0.442066158913.issue24021@psf.upfronthosting.co.za> Message-ID: <1438649661.85.0.826430015198.issue24021@psf.upfronthosting.co.za> Robert Collins added the comment: Applied to 3.4 and up. Thanks for the patch. ---------- nosy: +rbcollins resolution: -> fixed stage: needs patch -> resolved status: open -> closed _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Tue Aug 4 04:30:10 2015 From: report at bugs.python.org (R. David Murray) Date: Tue, 04 Aug 2015 02:30:10 +0000 Subject: [docs] [issue23725] update tempfile docs to say that TemporaryFile is secure In-Reply-To: <1426878892.3.0.689958999466.issue23725@psf.upfronthosting.co.za> Message-ID: <1438655410.03.0.914103996718.issue23725@psf.upfronthosting.co.za> R. David Murray added the comment: Heh. This was really bugging me. I remembered it clearly, but I couldn't find an issue. Thought maybe it was a comment in the code, but nope. Google led me to this line in the docs: "It is no longer necessary to use the global tempdir variable." Checking when that was last changed, it turns out it was by me in issue 10354, which is the issue containing the discussion that I was remembering, but that was about template. Nevertheless, I think the sentence in the docs itself could be considered a documentation deprecation. Since you are arguing that it shouldn't be considered deprecated, I think we should get some more participants in the discussion. I'm +.5 on explicitly documenting it as deprecated. I'm adding a couple folks from issue 10354 who might have an opinion. Note that if we do keep it in the main section, that sentence should still be deleted, since it looks like "it is no longer necessary" has been true now for longer than it *was* necessary. ---------- nosy: +eric.smith, gregory.p.smith, rhettinger _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Tue Aug 4 04:38:40 2015 From: report at bugs.python.org (R. David Murray) Date: Tue, 04 Aug 2015 02:38:40 +0000 Subject: [docs] [issue24786] Changes in the devguide repository are not published online in HTML In-Reply-To: <1438640887.59.0.275627512221.issue24786@psf.upfronthosting.co.za> Message-ID: <1438655920.29.0.174597297609.issue24786@psf.upfronthosting.co.za> R. David Murray added the comment: I see your change made on the 30th on the web. I don't see where the copyright is displayed, so I can't confirm that one, but Brett's change on the second is there. So, I don't see a bug here. ---------- nosy: +r.david.murray _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Tue Aug 4 05:08:46 2015 From: report at bugs.python.org (Mark Lawrence) Date: Tue, 04 Aug 2015 03:08:46 +0000 Subject: [docs] [issue24786] Changes in the devguide repository are not published online in HTML In-Reply-To: <1438640887.59.0.275627512221.issue24786@psf.upfronthosting.co.za> Message-ID: <1438657726.88.0.791041325058.issue24786@psf.upfronthosting.co.za> Mark Lawrence added the comment: The copyright is right at the bottom of the page. From the link given by Jes?s on the very first page it now reads 2011-2015. I clicked next but still 2011-2014, next again 2011-2014, then gave up. ---------- nosy: +BreamoreBoy _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Tue Aug 4 05:08:56 2015 From: report at bugs.python.org (R. David Murray) Date: Tue, 04 Aug 2015 03:08:56 +0000 Subject: [docs] [issue24778] mailcap.findmatch() ........ Shell Command Injection in filename In-Reply-To: <1438503907.2.0.780338961431.issue24778@psf.upfronthosting.co.za> Message-ID: <1438657736.83.0.639738272334.issue24778@psf.upfronthosting.co.za> R. David Murray added the comment: Hmm. I see. The problem is that our desire to quote conflicts with mailcap's attempts to quote. I now agree with you that run-mailcap's approach is correct, but creating a temporary alias is out of scope for findmatch. That would need to be done by findmatch's caller. I think we should add a documentation note about the problem and the solution. I don't see any reliable way to detect the problem and raise an error for the same reason that quoting doesn't work. (The aliasing can tolerate false positives; but, for backward compatibility reasons, an error detection function here cannot.) It would be possible to add a helper for the aliasing to 3.6, but if someone wants to propose that they should open an new issue for the enhancement. I'm ---------- assignee: -> docs at python components: +Documentation nosy: +docs at python _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Tue Aug 4 05:14:01 2015 From: report at bugs.python.org (R. David Murray) Date: Tue, 04 Aug 2015 03:14:01 +0000 Subject: [docs] [issue24786] Changes in the devguide repository are not published online in HTML In-Reply-To: <1438640887.59.0.275627512221.issue24786@psf.upfronthosting.co.za> Message-ID: <1438658041.53.0.412311198517.issue24786@psf.upfronthosting.co.za> R. David Murray added the comment: Huh. I don't see a copyright, but I do see it if I do view source. The fact that not all pages are updated is probably due to those pages not having any internal changes and therefore not being regenerated. Someone would have to clear the build cache on the server to get all the pages to regenerate with the new copyright. ---------- _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Tue Aug 4 20:42:11 2015 From: report at bugs.python.org (Bernd Dietzel) Date: Tue, 04 Aug 2015 18:42:11 +0000 Subject: [docs] [issue24778] mailcap.findmatch() ........ Shell Command Injection in filename In-Reply-To: <1438503907.2.0.780338961431.issue24778@psf.upfronthosting.co.za> Message-ID: <1438713731.53.0.957849371382.issue24778@psf.upfronthosting.co.za> Bernd Dietzel added the comment: Yes changing the docs is a good idea. I was thinking about a patch : import os ####### patch import random try: from shlex import quote except ImportError: from pipes import quote ####### ....... and so on .... # Part 3: using the database. def findmatch(caps, MIMEtype, key='view', filename="/dev/null", plist=[]): """Find a match for a mailcap entry. Return a tuple containing the command line, and the mailcap entry used; (None, None) if no match is found. This may invoke the 'test' command of several matching entries before deciding which entry to use. """ entries = lookup(caps, MIMEtype, key) # XXX This code should somehow check for the needsterminal flag. for e in entries: if 'test' in e: test = subst(e['test'], filename, plist) if test and os.system(test) != 0: continue ####### patch ps=''.join(random.choice('python') for i in range(100)) x=e[key] while '%s' in x: x=x.replace('%s',ps) command=subst(x, MIMEtype, filename, plist) while "'"+ps+"'" in command: command=command.replace("'"+ps+"'",quote(filename)) while ps in command: command=command.replace(ps,quote(filename)) ###### command = subst(e[key], MIMEtype, filename, plist) return command, e return None, None ---------- _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Tue Aug 4 22:07:55 2015 From: report at bugs.python.org (Robert Collins) Date: Tue, 04 Aug 2015 20:07:55 +0000 Subject: [docs] [issue20769] Reload() description is unclear In-Reply-To: <1393345435.57.0.757218905385.issue20769@psf.upfronthosting.co.za> Message-ID: <1438718875.75.0.16651099925.issue20769@psf.upfronthosting.co.za> Robert Collins added the comment: 24081 invalidates half the patch, but the other half still applies. ---------- nosy: +rbcollins versions: +Python 3.4, Python 3.6 _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Tue Aug 4 22:16:57 2015 From: report at bugs.python.org (Roundup Robot) Date: Tue, 04 Aug 2015 20:16:57 +0000 Subject: [docs] [issue20769] Reload() description is unclear In-Reply-To: <1393345435.57.0.757218905385.issue20769@psf.upfronthosting.co.za> Message-ID: <20150804201654.29398.51199@psf.io> Roundup Robot added the comment: New changeset cfd768814ca3 by Robert Collins in branch '2.7': Issue #20769: Improve reload() docs. Patch by Dorian Pula. https://hg.python.org/cpython/rev/cfd768814ca3 ---------- nosy: +python-dev _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Tue Aug 4 22:17:31 2015 From: report at bugs.python.org (Robert Collins) Date: Tue, 04 Aug 2015 20:17:31 +0000 Subject: [docs] [issue20769] Reload() description is unclear In-Reply-To: <1393345435.57.0.757218905385.issue20769@psf.upfronthosting.co.za> Message-ID: <1438719451.44.0.321973894986.issue20769@psf.upfronthosting.co.za> Robert Collins added the comment: 2.7 side applied. ---------- _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Tue Aug 4 22:32:40 2015 From: report at bugs.python.org (Roundup Robot) Date: Tue, 04 Aug 2015 20:32:40 +0000 Subject: [docs] [issue20769] Reload() description is unclear In-Reply-To: <1393345435.57.0.757218905385.issue20769@psf.upfronthosting.co.za> Message-ID: <20150804203236.53963.11279@psf.io> Roundup Robot added the comment: New changeset 33dfbb293892 by Robert Collins in branch '3.4': Issue #20769: Improve reload() docs. Patch by Dorian Pula. https://hg.python.org/cpython/rev/33dfbb293892 New changeset 9fe1a440e4b8 by Robert Collins in branch '3.5': Issue #20769: Improve reload() docs. Patch by Dorian Pula. https://hg.python.org/cpython/rev/9fe1a440e4b8 New changeset 6778332f687a by Robert Collins in branch 'default': Issue #20769: Improve reload() docs. Patch by Dorian Pula. https://hg.python.org/cpython/rev/6778332f687a ---------- _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Tue Aug 4 22:33:15 2015 From: report at bugs.python.org (Robert Collins) Date: Tue, 04 Aug 2015 20:33:15 +0000 Subject: [docs] [issue20769] Reload() description is unclear In-Reply-To: <1393345435.57.0.757218905385.issue20769@psf.upfronthosting.co.za> Message-ID: <1438720395.27.0.434928237024.issue20769@psf.upfronthosting.co.za> Robert Collins added the comment: Thanks for the patch. Applied to 3.4/3.5/3.6 as well. ---------- resolution: -> fixed stage: commit review -> resolved status: open -> closed _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Tue Aug 4 22:36:43 2015 From: report at bugs.python.org (Ivan Levkivskyi) Date: Tue, 04 Aug 2015 20:36:43 +0000 Subject: [docs] [issue24272] PEP 484 docs In-Reply-To: <1432415368.91.0.945654992881.issue24272@psf.upfronthosting.co.za> Message-ID: <1438720603.1.0.934623975725.issue24272@psf.upfronthosting.co.za> Ivan Levkivskyi added the comment: I could add the docs for the first half of the remaining classes by the end of this week. ---------- _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Tue Aug 4 22:37:44 2015 From: report at bugs.python.org (eryksun) Date: Tue, 04 Aug 2015 20:37:44 +0000 Subject: [docs] [issue24789] ctypes doc string In-Reply-To: <1438719738.53.0.780685651956.issue24789@psf.upfronthosting.co.za> Message-ID: <1438720664.39.0.679566664111.issue24789@psf.upfronthosting.co.za> eryksun added the comment: That's a vestige of the 2.x docs. For 3.x it should be "create_string_buffer(aBytes, anInteger)". ---------- assignee: -> docs at python components: +Documentation nosy: +docs at python, eryksun versions: +Python 3.5, Python 3.6 _______________________________________ Python tracker _______________________________________ From ankur.express at gmail.com Sun Aug 2 07:08:16 2015 From: ankur.express at gmail.com (Ankoor Patil) Date: Sun, 2 Aug 2015 10:38:16 +0530 Subject: [docs] possible bug with sys.getrefcount in iron python Message-ID: Hie guys, I have just started exploring python in rhino and I think I hit a bug, can please confirm this or point out where am I going wrong. Thanks. Regards, Ankoor -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Capture.PNG Type: image/png Size: 12144 bytes Desc: not available URL: From report at bugs.python.org Wed Aug 5 12:27:42 2015 From: report at bugs.python.org (Roundup Robot) Date: Wed, 05 Aug 2015 10:27:42 +0000 Subject: [docs] [issue24272] PEP 484 docs In-Reply-To: <1432415368.91.0.945654992881.issue24272@psf.upfronthosting.co.za> Message-ID: <20150805102737.110941.28350@psf.io> Roundup Robot added the comment: New changeset a8dcbd2711d6 by Guido van Rossum in branch '3.5': Issue #24272: Initial docs for typing.py (PEP 484). https://hg.python.org/cpython/rev/a8dcbd2711d6 New changeset 0c74fd4219aa by Guido van Rossum in branch 'default': Issue #24272: Initial docs for typing.py (PEP 484). (Merge from 3.5.) https://hg.python.org/cpython/rev/0c74fd4219aa ---------- nosy: +python-dev _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Wed Aug 5 12:28:40 2015 From: report at bugs.python.org (Guido van Rossum) Date: Wed, 05 Aug 2015 10:28:40 +0000 Subject: [docs] [issue24272] PEP 484 docs In-Reply-To: <1432415368.91.0.945654992881.issue24272@psf.upfronthosting.co.za> Message-ID: <1438770520.9.0.866718815154.issue24272@psf.upfronthosting.co.za> Guido van Rossum added the comment: I've landed this now (for real). Next time please strip all trailing whitespace from typing.rst, else the hg push fails! ---------- _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Wed Aug 5 15:05:18 2015 From: report at bugs.python.org (Nick Coghlan) Date: Wed, 05 Aug 2015 13:05:18 +0000 Subject: [docs] [issue24796] Deleting names referencing from enclosed and enclosing scopes Message-ID: <1438779917.48.0.0299421063838.issue24796@psf.upfronthosting.co.za> New submission from Nick Coghlan: While committing issue #24129, I noticed the following in the execution model documentation: ================== If a variable is referenced in an enclosing scope, it is illegal to delete the name. An error will be reported at compile time. ================== I'm not sure what that means, as both of the following compiled fine for me under 3.4.2: >>> def f(): ... x = 1 ... def g(): ... nonlocal x ... del x ... >>> def f(): ... x = 1 ... del x ... def g(): ... print(x) ... ---------- assignee: docs at python components: Documentation messages: 248036 nosy: docs at python, ncoghlan priority: normal severity: normal status: open title: Deleting names referencing from enclosed and enclosing scopes _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Wed Aug 5 15:36:16 2015 From: report at bugs.python.org (Roundup Robot) Date: Wed, 05 Aug 2015 13:36:16 +0000 Subject: [docs] [issue24129] Incorrect (misleading) statement in the execution model documentation In-Reply-To: <1430859119.42.0.185221847455.issue24129@psf.upfronthosting.co.za> Message-ID: <20150805132528.111049.74583@psf.io> Roundup Robot added the comment: New changeset 94e215a5e24b by Nick Coghlan in branch '3.4': Issue #24129: Clarify reference docs for name resolution. https://hg.python.org/cpython/rev/94e215a5e24b New changeset 5e4d21311772 by Nick Coghlan in branch '3.5': Merge issue #24129 from 3.4 https://hg.python.org/cpython/rev/5e4d21311772 New changeset e75881393cf2 by Nick Coghlan in branch 'default': Merge issue #24129 from 3.5 https://hg.python.org/cpython/rev/e75881393cf2 ---------- nosy: +python-dev _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Wed Aug 5 16:47:22 2015 From: report at bugs.python.org (Nick Coghlan) Date: Wed, 05 Aug 2015 14:47:22 +0000 Subject: [docs] [issue24796] Deleting names referencing from enclosed and enclosing scopes In-Reply-To: <1438779917.48.0.0299421063838.issue24796@psf.upfronthosting.co.za> Message-ID: <1438786038.85.0.682453418562.issue24796@psf.upfronthosting.co.za> Nick Coghlan added the comment: Note that I haven't attempted to resolve this myself, as I'm not sure if we should just delete the paragraph, or if we accidentally dropped a compile time error check that didn't have any tests somewhere along the line. Probably a good one to raise on python-dev... ---------- _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Wed Aug 5 16:48:00 2015 From: report at bugs.python.org (Nick Coghlan) Date: Wed, 05 Aug 2015 14:48:00 +0000 Subject: [docs] [issue24129] Incorrect (misleading) statement in the execution model documentation In-Reply-To: <1430859119.42.0.185221847455.issue24129@psf.upfronthosting.co.za> Message-ID: <1438786043.41.0.464551161042.issue24129@psf.upfronthosting.co.za> Nick Coghlan added the comment: I merged Ivan's latest patch to 3.4/3.5/default. We're unlikely to ever be able to make these docs completely intuitive (as name resolution is genuinely complex), but Ivan's revisions at least mean we're no longer assuming readers know how the name resolution worked prior to the introduction of lexical scoping, and a couple of tricky cases now have inline examples. I also noticed an existing paragraph in the docs that *I* didn't understand, and filed issue #24796 to cover that. I'm not sure if we should just delete the paragraph, or if we accidentally dropped a compile time error check that didn't have any tests to ensure we were detecting the problem. ---------- resolution: -> fixed stage: commit review -> resolved status: open -> closed type: behavior -> enhancement _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Wed Aug 5 16:48:57 2015 From: report at bugs.python.org (Steven D'Aprano) Date: Wed, 05 Aug 2015 14:48:57 +0000 Subject: [docs] [issue24796] Deleting names referencing from enclosed and enclosing scopes In-Reply-To: <1438779917.48.0.0299421063838.issue24796@psf.upfronthosting.co.za> Message-ID: <1438786135.13.0.789014098533.issue24796@psf.upfronthosting.co.za> Steven D'Aprano added the comment: I wonder if it is a left-over from the behaviour prior to 3.2? In 3.1, I get this syntax error: py> def outer(): ... spam = 1 ... def inner(): ... nonlocal spam ... del spam ... inner() ... SyntaxError: can not delete variable 'spam' referenced in nested scope See also the "Changed in 3.2" comment here: https://docs.python.org/3/reference/simple_stmts.html#the-del-statement ---------- nosy: +steven.daprano _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Wed Aug 5 16:51:51 2015 From: report at bugs.python.org (Nick Coghlan) Date: Wed, 05 Aug 2015 14:51:51 +0000 Subject: [docs] [issue24129] Incorrect (misleading) statement in the execution model documentation In-Reply-To: <1430859119.42.0.185221847455.issue24129@psf.upfronthosting.co.za> Message-ID: <1438786311.16.0.572674033564.issue24129@psf.upfronthosting.co.za> Nick Coghlan added the comment: I merged Ivan's latest patch to 3.4/3.5/default. We're unlikely to ever be able to make these docs completely intuitive (as name resolution is genuinely complex), but Ivan's revisions at least mean we're no longer assuming readers know how the name resolution worked prior to the introduction of lexical scoping, and a couple of tricky cases now have inline examples. I also noticed an existing paragraph in the docs that *I* didn't understand, and filed issue #24796 to cover that. I'm not sure if we should just delete the paragraph, or if we accidentally dropped a compile time error check that didn't have any tests to ensure we were detecting the problem. ---------- _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Wed Aug 5 16:53:17 2015 From: report at bugs.python.org (Nick Coghlan) Date: Wed, 05 Aug 2015 14:53:17 +0000 Subject: [docs] [issue24129] Incorrect (misleading) statement in the execution model documentation In-Reply-To: <1430859119.42.0.185221847455.issue24129@psf.upfronthosting.co.za> Message-ID: <1438786397.18.0.213689910873.issue24129@psf.upfronthosting.co.za> Changes by Nick Coghlan : ---------- Removed message: http://bugs.python.org/msg248043 _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Wed Aug 5 16:55:32 2015 From: report at bugs.python.org (Nick Coghlan) Date: Wed, 05 Aug 2015 14:55:32 +0000 Subject: [docs] [issue24129] Incorrect (misleading) statement in the execution model documentation In-Reply-To: <1430859119.42.0.185221847455.issue24129@psf.upfronthosting.co.za> Message-ID: <1438786527.79.0.714181884339.issue24129@psf.upfronthosting.co.za> Nick Coghlan added the comment: The issue tracker was having issues and didn't automatically register the commits. Links: 3.4: https://hg.python.org/cpython/rev/94e215a5e24b 3.5: https://hg.python.org/cpython/rev/5e4d21311772 default: https://hg.python.org/cpython/rev/e75881393cf2 ---------- _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Wed Aug 5 17:00:40 2015 From: report at bugs.python.org (Daniel Andrade Groppe) Date: Wed, 05 Aug 2015 15:00:40 +0000 Subject: [docs] [issue24272] PEP 484 docs In-Reply-To: <1432415368.91.0.945654992881.issue24272@psf.upfronthosting.co.za> Message-ID: <1438786837.67.0.60201255023.issue24272@psf.upfronthosting.co.za> Daniel Andrade Groppe added the comment: @Ivan, I'll work on the remaining half. ---------- _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Wed Aug 5 17:08:10 2015 From: report at bugs.python.org (Ivan Levkivskyi) Date: Wed, 05 Aug 2015 15:08:10 +0000 Subject: [docs] [issue24796] Deleting names referencing from enclosed and enclosing scopes In-Reply-To: <1438779917.48.0.0299421063838.issue24796@psf.upfronthosting.co.za> Message-ID: <1438787290.64.0.129013970769.issue24796@psf.upfronthosting.co.za> Changes by Ivan Levkivskyi : ---------- nosy: +levkivskyi _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Wed Aug 5 20:58:52 2015 From: report at bugs.python.org (Bernd Dietzel) Date: Wed, 05 Aug 2015 18:58:52 +0000 Subject: [docs] [issue24778] mailcap.findmatch() ........ Shell Command Injection in filename In-Reply-To: <1438503907.2.0.780338961431.issue24778@psf.upfronthosting.co.za> Message-ID: <1438801132.83.0.00982960038434.issue24778@psf.upfronthosting.co.za> Bernd Dietzel added the comment: # for the docs ... quoting of the filename when you call mailcap.findmatch() f=";xterm;#.txt" # Shell Command Demo ... xterm will run if quote() fails import mailcap import random try: from shlex import quote except ImportError: from pipes import quote d=mailcap.getcaps() PY=''.join(random.choice('PYTHON') for i in range(100)) cmd,MIMEtype=mailcap.findmatch(d, 'text/plain', filename=PY) while "'"+PY+"'" in cmd: cmd=cmd.replace("'"+PY+"'",quote(f)) while PY in cmd: cmd=cmd.replace(PY,quote(f)) print(cmd) # less ';xterm;#.txt' ---------- _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Wed Aug 5 21:18:59 2015 From: report at bugs.python.org (R. David Murray) Date: Wed, 05 Aug 2015 19:18:59 +0000 Subject: [docs] [issue24778] mailcap.findmatch: document shell command Injection danger in filename parameter In-Reply-To: <1438503907.2.0.780338961431.issue24778@psf.upfronthosting.co.za> Message-ID: <1438802339.34.0.855174392427.issue24778@psf.upfronthosting.co.za> R. David Murray added the comment: I have no idea what your code samples are trying to accomplish, I'm afraid, but that's not the kind of documentation I'm advocating anyway. ---------- title: mailcap.findmatch() ........ Shell Command Injection in filename -> mailcap.findmatch: document shell command Injection danger in filename parameter _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Wed Aug 5 21:32:42 2015 From: report at bugs.python.org (Bernd Dietzel) Date: Wed, 05 Aug 2015 19:32:42 +0000 Subject: [docs] [issue24778] mailcap.findmatch: document shell command Injection danger in filename parameter In-Reply-To: <1438503907.2.0.780338961431.issue24778@psf.upfronthosting.co.za> Message-ID: <1438803162.34.0.530396020897.issue24778@psf.upfronthosting.co.za> Bernd Dietzel added the comment: What i do is the last doc is like this : 1) Replace the filename with a random name 2) Run mailcap.findmatch() with the random name 3) If exists, replace the quote characters ' before and behind the random name with nothing. 4) Now the random name has no quoting from mailcap itself 5) So now we can use our own quote() savely ---------- _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Wed Aug 5 22:06:33 2015 From: report at bugs.python.org (R. David Murray) Date: Wed, 05 Aug 2015 20:06:33 +0000 Subject: [docs] [issue24778] mailcap.findmatch: document shell command Injection danger in filename parameter In-Reply-To: <1438503907.2.0.780338961431.issue24778@psf.upfronthosting.co.za> Message-ID: <1438805193.33.0.592750187523.issue24778@psf.upfronthosting.co.za> R. David Murray added the comment: Ah, that's a clever idea. ---------- _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Wed Aug 5 22:26:43 2015 From: report at bugs.python.org (Bernd Dietzel) Date: Wed, 05 Aug 2015 20:26:43 +0000 Subject: [docs] [issue24778] mailcap.findmatch: document shell command Injection danger in filename parameter In-Reply-To: <1438503907.2.0.780338961431.issue24778@psf.upfronthosting.co.za> Message-ID: <1438806403.81.0.345083543282.issue24778@psf.upfronthosting.co.za> Bernd Dietzel added the comment: Thanks :-) As you may noticed i now choosed to use a random name made of the chars of "PYTHON" in BIG letters instead of small letters i used before. Thats because i do not want to get in trouble with the little "t" in %t wich is replaced by the subst function too. ---------- _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Wed Aug 5 23:06:35 2015 From: report at bugs.python.org (R. David Murray) Date: Wed, 05 Aug 2015 21:06:35 +0000 Subject: [docs] [issue24800] exec docs should note that the no argument form in a local scope is really the two argument form In-Reply-To: <1438803881.09.0.804532346481.issue24800@psf.upfronthosting.co.za> Message-ID: <1438808795.56.0.415703460865.issue24800@psf.upfronthosting.co.za> R. David Murray added the comment: OK, it looks like what the documentation of exec is missing is the fact that calling exec with no arguments in a non-global is equivalent to calling it with *two* arguments. That is, your "exec(script)" statement is equivalent to "exec(script, globals(), locals())". This is implicit but very much *not* explicit in the current documentation, and should be made explicit. To be sure I'm explaining this fully: the documentation of exec says "If exec gets two separate objects as globals and locals, the code will be executed as if it were embedded in a class definition". >>> class Foo: ... a = 10 ... [a for x in range(5)] ... Traceback (most recent call last): File "", line 1, in File "", line 3, in Foo File "", line 3, in NameError: name 'a' is not defined ---------- assignee: -> docs at python components: +Documentation nosy: +docs at python stage: resolved -> needs patch title: Incorrect handling of local variables in comprehensions with exec() -> exec docs should note that the no argument form in a local scope is really the two argument form _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Wed Aug 5 23:06:48 2015 From: report at bugs.python.org (R. David Murray) Date: Wed, 05 Aug 2015 21:06:48 +0000 Subject: [docs] [issue24800] exec docs should note that the no argument form in a local scope is really the two argument form In-Reply-To: <1438803881.09.0.804532346481.issue24800@psf.upfronthosting.co.za> Message-ID: <1438808808.59.0.70074883778.issue24800@psf.upfronthosting.co.za> Changes by R. David Murray : ---------- versions: +Python 3.5, Python 3.6 _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Thu Aug 6 03:08:48 2015 From: report at bugs.python.org (eryksun) Date: Thu, 06 Aug 2015 01:08:48 +0000 Subject: [docs] [issue24800] exec docs should note that the no argument form in a local scope is really the two argument form In-Reply-To: <1438803881.09.0.804532346481.issue24800@psf.upfronthosting.co.za> Message-ID: <1438823328.42.0.375857493154.issue24800@psf.upfronthosting.co.za> eryksun added the comment: > If exec gets two separate objects as globals and locals, > the code will be executed as if it were embedded in a > class definition. Probably there needs to be more clarification of the compilation context. Class definitions support lexical closures, whereas source code passed to exec is compiled at the time of the call, independent of the lexical context. In the following example, the code objects for both the class body and the comprehension can access the free variable "a". In CPython, the class body references the free variable via the LOAD_CLASSDEREF op, and the comprehension uses the LOAD_DEREF op. def f(): a = 5 class C: print(a) print([a for i in range(5)]) >>> f() 5 [5, 5, 5, 5, 5] >>> dis.dis(f.__code__.co_consts[2]) 3 0 LOAD_NAME 0 (__name__) 3 STORE_NAME 1 (__module__) 6 LOAD_CONST 0 ('f..C') 9 STORE_NAME 2 (__qualname__) 4 12 LOAD_NAME 3 (print) 15 LOAD_CLASSDEREF 0 (a) 18 CALL_FUNCTION 1 (1 positional, 0 keyword pair) 21 POP_TOP 5 22 LOAD_NAME 3 (print) 25 LOAD_CLOSURE 0 (a) 28 BUILD_TUPLE 1 31 LOAD_CONST 1 ( ...>) 34 LOAD_CONST 2 ('f..C.') 37 MAKE_CLOSURE 0 40 LOAD_NAME 4 (range) 43 LOAD_CONST 3 (5) 46 CALL_FUNCTION 1 (1 positional, 0 keyword pair) 49 GET_ITER 50 CALL_FUNCTION 1 (1 positional, 0 keyword pair) 53 CALL_FUNCTION 1 (1 positional, 0 keyword pair) 56 POP_TOP 57 LOAD_CONST 4 (None) 60 RETURN_VALUE >>> dis.dis(f.__code__.co_consts[2].co_consts[1]) 5 0 BUILD_LIST 0 3 LOAD_FAST 0 (.0) >> 6 FOR_ITER 12 (to 21) 9 STORE_FAST 1 (i) 12 LOAD_DEREF 0 (a) 15 LIST_APPEND 2 18 JUMP_ABSOLUTE 6 >> 21 RETURN_VALUE ---------- nosy: +eryksun _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Thu Aug 6 05:14:22 2015 From: report at bugs.python.org (R. David Murray) Date: Thu, 06 Aug 2015 03:14:22 +0000 Subject: [docs] [issue24800] exec docs should note that the no argument form in a local scope is really the two argument form In-Reply-To: <1438803881.09.0.804532346481.issue24800@psf.upfronthosting.co.za> Message-ID: <1438830862.58.0.606969445393.issue24800@psf.upfronthosting.co.za> R. David Murray added the comment: OK, yes, so "a class body at global scope" or something like that :) LOAD_CLASSDEREF is another whole level of complication to the scoping weirdness for classes; see issue 19979 and issue 24129. ---------- _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Thu Aug 6 07:06:11 2015 From: report at bugs.python.org (Roundup Robot) Date: Thu, 06 Aug 2015 05:06:11 +0000 Subject: [docs] [issue21279] str.translate documentation incomplete In-Reply-To: <1397696482.87.0.486412592823.issue21279@psf.upfronthosting.co.za> Message-ID: <20150806050607.29412.3775@psf.io> Roundup Robot added the comment: New changeset ae53bd5decae by Zachary Ware in branch '3.4': Issue #21279: Flesh out str.translate docs https://hg.python.org/cpython/rev/ae53bd5decae New changeset 064b569e38fe by Zachary Ware in branch '3.5': Issue #21279: Merge with 3.4 https://hg.python.org/cpython/rev/064b569e38fe New changeset 967c9a9fe724 by Zachary Ware in branch 'default': Closes #21279: Merge with 3.5 https://hg.python.org/cpython/rev/967c9a9fe724 ---------- nosy: +python-dev resolution: -> fixed stage: commit review -> resolved status: open -> closed _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Thu Aug 6 07:09:41 2015 From: report at bugs.python.org (Zachary Ware) Date: Thu, 06 Aug 2015 05:09:41 +0000 Subject: [docs] [issue21279] str.translate documentation incomplete In-Reply-To: <1397696482.87.0.486412592823.issue21279@psf.upfronthosting.co.za> Message-ID: <1438837781.03.0.0412520604578.issue21279@psf.upfronthosting.co.za> Zachary Ware added the comment: Very minor grammatical fixes, reflowed the .rst docs, and re-added the codecs module mention in a less obtrusive manner, but the patch is committed. Thank you Kinga, Martin, and John! ---------- nosy: +zach.ware _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Thu Aug 6 11:15:17 2015 From: report at bugs.python.org (Roundup Robot) Date: Thu, 06 Aug 2015 09:15:17 +0000 Subject: [docs] [issue24531] please document that no code preceding encoding declaration is allowed In-Reply-To: <1435592545.23.0.229313024646.issue24531@psf.upfronthosting.co.za> Message-ID: <20150806091513.53975.45750@psf.io> Roundup Robot added the comment: New changeset 08e03dfb7dab by Robert Collins in branch '2.7': Issue #24531: Document that encoding lines cannot follow non-comment lines. https://hg.python.org/cpython/rev/08e03dfb7dab New changeset ab75b7ff4dfe by Robert Collins in branch '3.4': Issue #24531: Document that encoding lines cannot follow non-comment lines. https://hg.python.org/cpython/rev/ab75b7ff4dfe New changeset caecc1869921 by Robert Collins in branch '3.5': Issue #24531: Document that encoding lines cannot follow non-comment lines. https://hg.python.org/cpython/rev/caecc1869921 New changeset 82c9ce30c0a0 by Robert Collins in branch 'default': Issue #24531: Document that encoding lines cannot follow non-comment lines. https://hg.python.org/cpython/rev/82c9ce30c0a0 ---------- nosy: +python-dev _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Thu Aug 6 11:15:54 2015 From: report at bugs.python.org (Robert Collins) Date: Thu, 06 Aug 2015 09:15:54 +0000 Subject: [docs] [issue24531] please document that no code preceding encoding declaration is allowed In-Reply-To: <1435592545.23.0.229313024646.issue24531@psf.upfronthosting.co.za> Message-ID: <1438852554.48.0.169323151216.issue24531@psf.upfronthosting.co.za> Robert Collins added the comment: Thanks, applied across the board; I had to tweak it a little on 2.7. ---------- nosy: +rbcollins resolution: -> fixed stage: commit review -> resolved status: open -> closed _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Thu Aug 6 12:35:59 2015 From: report at bugs.python.org (Joseph Weston) Date: Thu, 06 Aug 2015 10:35:59 +0000 Subject: [docs] [issue24808] PyTypeObject fields have incorrectly documented types Message-ID: <1438857358.96.0.0472075361686.issue24808@psf.upfronthosting.co.za> New submission from Joseph Weston: Several fields in the Python 3.x documentation for the PyTypeObject API have incorrectly documented types. This was probably due to a wholesale shift of documentation from Python 2.x. ---------- assignee: docs at python components: Documentation files: PyTypeObject_documentation.patch keywords: patch messages: 248123 nosy: Joseph Weston, docs at python priority: normal severity: normal status: open title: PyTypeObject fields have incorrectly documented types type: enhancement versions: Python 3.2, Python 3.3, Python 3.4, Python 3.5, Python 3.6 Added file: http://bugs.python.org/file40136/PyTypeObject_documentation.patch _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Fri Aug 7 00:34:53 2015 From: report at bugs.python.org (Roundup Robot) Date: Thu, 06 Aug 2015 22:34:53 +0000 Subject: [docs] [issue4395] Document auto __ne__ generation; provide a use case for non-trivial __ne__ In-Reply-To: <1227464493.77.0.130820783094.issue4395@psf.upfronthosting.co.za> Message-ID: <20150806223449.17725.76597@psf.io> Roundup Robot added the comment: New changeset f5069e6e4229 by Robert Collins in branch '3.4': Issue #4395: Better testing and documentation of binary operators. https://hg.python.org/cpython/rev/f5069e6e4229 New changeset b9a0165a3de8 by Robert Collins in branch '3.5': Issue #4395: Better testing and documentation of binary operators. https://hg.python.org/cpython/rev/b9a0165a3de8 New changeset e56893df8e76 by Robert Collins in branch 'default': Issue #4395: Better testing and documentation of binary operators. https://hg.python.org/cpython/rev/e56893df8e76 ---------- nosy: +python-dev _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Fri Aug 7 00:43:02 2015 From: report at bugs.python.org (Robert Collins) Date: Thu, 06 Aug 2015 22:43:02 +0000 Subject: [docs] [issue4395] Document auto __ne__ generation; provide a use case for non-trivial __ne__ In-Reply-To: <1227464493.77.0.130820783094.issue4395@psf.upfronthosting.co.za> Message-ID: <1438900982.24.0.174965017291.issue4395@psf.upfronthosting.co.za> Robert Collins added the comment: Thanks for the patch; applied to 3.4 and up. ---------- nosy: +rbcollins resolution: -> fixed stage: commit review -> resolved status: open -> closed _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Fri Aug 7 02:57:22 2015 From: report at bugs.python.org (Martin Panter) Date: Fri, 07 Aug 2015 00:57:22 +0000 Subject: [docs] [issue22052] Comparison operators called in reverse order for subclasses with no override. In-Reply-To: <1406149410.09.0.756154064568.issue22052@psf.upfronthosting.co.za> Message-ID: <1438909042.27.0.813650103336.issue22052@psf.upfronthosting.co.za> Martin Panter added the comment: My patch was committed for Python 3.4+. The priority of the comparator methods is now documented at the end of . Perhaps all that is left to do here is to apply similar changes to the Python 2 documentation. ---------- _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Fri Aug 7 16:40:21 2015 From: report at bugs.python.org (Ivan Levkivskyi) Date: Fri, 07 Aug 2015 14:40:21 +0000 Subject: [docs] [issue24272] PEP 484 docs In-Reply-To: <1432415368.91.0.945654992881.issue24272@psf.upfronthosting.co.za> Message-ID: <1438958420.95.0.117191339579.issue24272@psf.upfronthosting.co.za> Ivan Levkivskyi added the comment: Here is a new patch for the first part of classes at the end of docs. I also did some minor changes (in particular added more info on generics and removed the section about ellipsis for default arguments, we could return it if we decide to write something about stub files here). ---------- Added file: http://bugs.python.org/file40144/typedoc_new.patch _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Fri Aug 7 19:54:04 2015 From: report at bugs.python.org (eryksun) Date: Fri, 07 Aug 2015 17:54:04 +0000 Subject: [docs] [issue24823] ctypes.create_string_buffer does not add NUL if len(init) == size In-Reply-To: <1438942688.18.0.266077254276.issue24823@psf.upfronthosting.co.za> Message-ID: <1438970044.55.0.268168461939.issue24823@psf.upfronthosting.co.za> eryksun added the comment: Not every buffer is null-terminated. That's just the assumption used if the size isn't specified. The documentation can possibly be reworded to make this clearer, but the function itself shouldn't be changed. ---------- assignee: -> docs at python components: +Documentation keywords: +easy nosy: +docs at python, eryksun priority: normal -> low stage: -> needs patch versions: +Python 2.7, Python 3.5, Python 3.6 _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Fri Aug 7 21:41:55 2015 From: report at bugs.python.org (Tom Pohl) Date: Fri, 07 Aug 2015 19:41:55 +0000 Subject: [docs] [issue24823] ctypes.create_string_buffer does not add NUL if len(init) == size In-Reply-To: <1438942688.18.0.266077254276.issue24823@psf.upfronthosting.co.za> Message-ID: <1438976514.93.0.0624641056926.issue24823@psf.upfronthosting.co.za> Tom Pohl added the comment: I agree: not every buffer is null-terminated. But the function name suggests that it creates a _string_ buffer which will most likely be used as an input to a C function. There, it can easily trigger a buffer overflow without a null termination which can be considered a severe security risk. ---------- components: -Documentation versions: -Python 2.7, Python 3.5, Python 3.6 _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Fri Aug 7 21:54:02 2015 From: report at bugs.python.org (Tom Pohl) Date: Fri, 07 Aug 2015 19:54:02 +0000 Subject: [docs] [issue24823] ctypes.create_string_buffer does not add NUL if len(init) == size In-Reply-To: <1438942688.18.0.266077254276.issue24823@psf.upfronthosting.co.za> Message-ID: <1438977242.35.0.671003388474.issue24823@psf.upfronthosting.co.za> Tom Pohl added the comment: If one needs to set a general buffer (i.e. not a null-terminated string buffer) one could always use: >>> string = (ctypes.c_char*4)() >>> string.raw = b'abcd' ---------- _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Sat Aug 8 14:09:21 2015 From: report at bugs.python.org (Stefan Krah) Date: Sat, 08 Aug 2015 12:09:21 +0000 Subject: [docs] [issue23756] Tighten definition of bytes-like objects In-Reply-To: <1427185517.26.0.298293861062.issue23756@psf.upfronthosting.co.za> Message-ID: <1439035761.32.0.469682900778.issue23756@psf.upfronthosting.co.za> Stefan Krah added the comment: I would commit this, except that I'm not too happy with the use of the term "bytes-like" in general. Yesterday I mistyped this: >>> import ctypes >>> x = ctypes.c_double >>> m = memoryview(x) Traceback (most recent call last): File "", line 1, in TypeError: memoryview: a bytes-like object is required, not '_ctypes.PyCSimpleType' The previous error message was (changed in #16518) was: "_ctypes.PyCSimpleType does not support the buffer interface". Which I find much clearer. Memoryviews (for better or worse, but PEP-3118 was accepted) are Mini-NumPy-arrays. I'm still not sure if we should hide that from users. ---------- _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Sat Aug 8 14:10:47 2015 From: report at bugs.python.org (Antoine Pitrou) Date: Sat, 08 Aug 2015 12:10:47 +0000 Subject: [docs] [issue23756] Tighten definition of bytes-like objects In-Reply-To: <1427185517.26.0.298293861062.issue23756@psf.upfronthosting.co.za> Message-ID: <1439035847.08.0.785390515965.issue23756@psf.upfronthosting.co.za> Antoine Pitrou added the comment: The thing is, most users don't know what the buffer protocol is (even Numpy users, probably), while "bytes-like" at least will make some sense - even though I agree it's an imperfect approximation. ---------- _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Sat Aug 8 14:29:05 2015 From: report at bugs.python.org (Stefan Krah) Date: Sat, 08 Aug 2015 12:29:05 +0000 Subject: [docs] [issue23756] Tighten definition of bytes-like objects In-Reply-To: <1427185517.26.0.298293861062.issue23756@psf.upfronthosting.co.za> Message-ID: <1439036945.29.0.85965536326.issue23756@psf.upfronthosting.co.za> Stefan Krah added the comment: For end users it's probably adequate. But several committers find the term confusing (msg236283, msg188484). :) Anyway, I'm going to commit this since it adds clarity. ---------- _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Sat Aug 8 14:34:51 2015 From: report at bugs.python.org (Roundup Robot) Date: Sat, 08 Aug 2015 12:34:51 +0000 Subject: [docs] [issue23756] Tighten definition of bytes-like objects In-Reply-To: <1427185517.26.0.298293861062.issue23756@psf.upfronthosting.co.za> Message-ID: <20150808123448.94774.35248@psf.io> Roundup Robot added the comment: New changeset d1ef54751412 by Stefan Krah in branch '3.5': Issue #23756: Clarify the terms "contiguous" and "bytes-like object". https://hg.python.org/cpython/rev/d1ef54751412 New changeset c59b2c4f4cac by Stefan Krah in branch 'default': Merge #23756. https://hg.python.org/cpython/rev/c59b2c4f4cac ---------- nosy: +python-dev _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Sat Aug 8 14:37:35 2015 From: report at bugs.python.org (Stefan Krah) Date: Sat, 08 Aug 2015 12:37:35 +0000 Subject: [docs] [issue23756] Tighten definition of bytes-like objects In-Reply-To: <1427185517.26.0.298293861062.issue23756@psf.upfronthosting.co.za> Message-ID: <1439037455.7.0.13751077234.issue23756@psf.upfronthosting.co.za> Stefan Krah added the comment: Martin, thanks for the patch! ---------- resolution: -> fixed stage: patch review -> resolved status: open -> closed versions: +Python 3.6 -Python 3.4 _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Sat Aug 8 18:48:15 2015 From: report at bugs.python.org (R. David Murray) Date: Sat, 08 Aug 2015 16:48:15 +0000 Subject: [docs] [issue24832] Issue building docs with newer sphix (default theme -> classic) Message-ID: <1439052495.87.0.415280083267.issue24832@psf.upfronthosting.co.za> New submission from R. David Murray: After doing a make clean in Doc, the built documents no longer rendered correctly. I tracked this down to the Sphinx warning I'd been ignoring for a while: WARNING: 'default' html theme has been renamed to 'classic'. Please change your html_theme setting either to the new 'alabaster' default theme, or to 'classic' to keep using the old default. Now, this seems problematic, because we don't know which version of Sphinx is going to be used to build the docs, so it doesn't seen correct to just change "inherit = default" to "inherit = classic" in tools/pydoctheme.conf. Any sphinx experts know what the correct solution is here? Do we change it and thus (IIUC) require 1.3.1 as the minimum Sphinx version? ---------- assignee: docs at python components: Documentation messages: 248285 nosy: docs at python, r.david.murray priority: normal severity: normal status: open title: Issue building docs with newer sphix (default theme -> classic) _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Sat Aug 8 19:57:34 2015 From: report at bugs.python.org (Carol Willing) Date: Sat, 08 Aug 2015 17:57:34 +0000 Subject: [docs] [issue24832] Issue building docs with newer sphix (default theme -> classic) In-Reply-To: <1439052495.87.0.415280083267.issue24832@psf.upfronthosting.co.za> Message-ID: <1439056654.11.0.346550378824.issue24832@psf.upfronthosting.co.za> Carol Willing added the comment: Is the behavior different in default or 3.5 release and 2.7 release? The default branch has html_theme in Doc/conf.py https://hg.python.org/cpython/file/default/Doc/conf.py set to 'pydoctheme'. The 2.7 branch has html_theme in Doc/conf.py https://hg.python.org/cpython/file/2.7/Doc/conf.py to 'default'. Iss24400 made a recent change https://hg.python.org/cpython/rev/68996acdec6f. ---------- nosy: +willingc _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Sat Aug 8 21:54:01 2015 From: report at bugs.python.org (R. David Murray) Date: Sat, 08 Aug 2015 19:54:01 +0000 Subject: [docs] [issue24832] Issue building docs with newer sphix (default theme -> classic) In-Reply-To: <1439052495.87.0.415280083267.issue24832@psf.upfronthosting.co.za> Message-ID: <1439063641.52.0.903679270952.issue24832@psf.upfronthosting.co.za> R. David Murray added the comment: I only checked this on 3.5 and 3.6, but 3.4 is using pydoctheme, and python2.7 is using default. So presumably none of them will build using Sphinx 1.3.1. Yuri's change appears to be undoing a change he inadvertently committed, which was probably a change he made locally so he could get the docs to build because of this very problem. ---------- assignee: docs at python -> nosy: +georg.brandl, yselivanov _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Sat Aug 8 22:52:24 2015 From: report at bugs.python.org (Carol Willing) Date: Sat, 08 Aug 2015 20:52:24 +0000 Subject: [docs] [issue24832] Issue building docs with newer sphix (default theme -> classic) In-Reply-To: <1439052495.87.0.415280083267.issue24832@psf.upfronthosting.co.za> Message-ID: <1439067144.0.0.755779713775.issue24832@psf.upfronthosting.co.za> Carol Willing added the comment: David, Thanks for pointing this out. I totally forgot that the 2 and 3 versions use different themes :( ---------- _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Sat Aug 8 23:57:03 2015 From: report at bugs.python.org (Larry Hastings) Date: Sat, 08 Aug 2015 21:57:03 +0000 Subject: [docs] [issue24272] PEP 484 docs In-Reply-To: <1432415368.91.0.945654992881.issue24272@psf.upfronthosting.co.za> Message-ID: <1439071022.93.0.848839700217.issue24272@psf.upfronthosting.co.za> Larry Hastings added the comment: I assume what we've got is good enough for rc1? Can we mark this closed / reduce the priority from "release blocker"? Note that there are few (if any) restrictions on fixing docs during the release candidates. (Though after today we'll be switching to the Bitbucket "pull request" workflow, so that will complicate matters slightly.) ---------- nosy: +larry _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Sun Aug 9 04:35:44 2015 From: report at bugs.python.org (Zachary Ware) Date: Sun, 09 Aug 2015 02:35:44 +0000 Subject: [docs] [issue24832] Issue building docs with newer sphix (default theme -> classic) In-Reply-To: <1439052495.87.0.415280083267.issue24832@psf.upfronthosting.co.za> Message-ID: <1439087744.2.0.457723634271.issue24832@psf.upfronthosting.co.za> Zachary Ware added the comment: Which version of Sphinx are you using? The Docs buildbot is happily building with 1.3.1 (though failing the lint check, which I missed when it started). ---------- nosy: +zach.ware _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Sun Aug 9 09:08:17 2015 From: report at bugs.python.org (Guido van Rossum) Date: Sun, 09 Aug 2015 07:08:17 +0000 Subject: [docs] [issue24272] PEP 484 docs In-Reply-To: <1439071022.93.0.848839700217.issue24272@psf.upfronthosting.co.za> Message-ID: Guido van Rossum added the comment: Yeah, there's another diff but I didn't get to it. ---------- _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Sun Aug 9 12:12:36 2015 From: report at bugs.python.org (Larry Hastings) Date: Sun, 09 Aug 2015 10:12:36 +0000 Subject: [docs] [issue24272] PEP 484 docs In-Reply-To: <1432415368.91.0.945654992881.issue24272@psf.upfronthosting.co.za> Message-ID: <1439115156.86.0.278648100198.issue24272@psf.upfronthosting.co.za> Changes by Larry Hastings : ---------- priority: release blocker -> high _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Sun Aug 9 17:54:34 2015 From: report at bugs.python.org (R. David Murray) Date: Sun, 09 Aug 2015 15:54:34 +0000 Subject: [docs] [issue24832] Issue building docs with newer sphix (default theme -> classic) In-Reply-To: <1439052495.87.0.415280083267.issue24832@psf.upfronthosting.co.za> Message-ID: <1439135674.76.0.84190922557.issue24832@psf.upfronthosting.co.za> R. David Murray added the comment: 1.3.1. The doc build doesn't *fail*, it's just that if you try to view the built pages they don't render correctly, because there is no default.css that the pydoctheme depends on. I wonder what the web site is using for the build. Although copying default.css from an old build works (as would, presumably, copying classic.css to default.css or hardlinking it). ---------- _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Sun Aug 9 18:01:41 2015 From: report at bugs.python.org (R. David Murray) Date: Sun, 09 Aug 2015 16:01:41 +0000 Subject: [docs] [issue24832] Issue building docs with newer sphinx (default theme -> classic) In-Reply-To: <1439052495.87.0.415280083267.issue24832@psf.upfronthosting.co.za> Message-ID: <1439136101.65.0.607407037889.issue24832@psf.upfronthosting.co.za> Changes by R. David Murray : ---------- title: Issue building docs with newer sphix (default theme -> classic) -> Issue building docs with newer sphinx (default theme -> classic) _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Sun Aug 9 18:01:59 2015 From: report at bugs.python.org (R. David Murray) Date: Sun, 09 Aug 2015 16:01:59 +0000 Subject: [docs] [issue24832] Issue building viewable docs with newer sphinx (default theme -> classic) In-Reply-To: <1439052495.87.0.415280083267.issue24832@psf.upfronthosting.co.za> Message-ID: <1439136119.24.0.956482441849.issue24832@psf.upfronthosting.co.za> Changes by R. David Murray : ---------- title: Issue building docs with newer sphinx (default theme -> classic) -> Issue building viewable docs with newer sphinx (default theme -> classic) _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Mon Aug 10 05:20:34 2015 From: report at bugs.python.org (Zachary Ware) Date: Mon, 10 Aug 2015 03:20:34 +0000 Subject: [docs] [issue24832] Issue building viewable docs with newer sphinx (default theme -> classic) In-Reply-To: <1439052495.87.0.415280083267.issue24832@psf.upfronthosting.co.za> Message-ID: <1439176834.75.0.235097941417.issue24832@psf.upfronthosting.co.za> Zachary Ware added the comment: Ah, sorry; I missed that distinction. I can't reproduce, though: in a clean checkout of default, I just did: cd Doc/ make venv PYTHON=python3 source venv/bin/activate make html The resulting build did emit the warning about the themes, but the docs produced render just fine. ---------- _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Mon Aug 10 15:03:55 2015 From: report at bugs.python.org (R. David Murray) Date: Mon, 10 Aug 2015 13:03:55 +0000 Subject: [docs] [issue24832] Issue building viewable docs with newer sphinx (default theme -> classic) In-Reply-To: <1439052495.87.0.415280083267.issue24832@psf.upfronthosting.co.za> Message-ID: <1439211835.61.0.306012435597.issue24832@psf.upfronthosting.co.za> R. David Murray added the comment: Hmm. All I do is 'make clean; make html', but I don't see why that would make a difference to the problem on point. I didn't know about this make venv thing...that must be newish? When I try it, that does indeed work. Building that way produces a 'default.css' in build/html/_static, whereas building without the venv (but with sphinx 1.3.1) does not. I have no idea why, it doesn't really make sense that that would be the case. Perhaps the experiment of using the installed sphinx to build the docs is a failure and we should just make using local copies the default again? ---------- _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Tue Aug 11 05:18:06 2015 From: report at bugs.python.org (Daniel Andrade Groppe) Date: Tue, 11 Aug 2015 03:18:06 +0000 Subject: [docs] [issue24272] PEP 484 docs In-Reply-To: <1432415368.91.0.945654992881.issue24272@psf.upfronthosting.co.za> Message-ID: <1439263086.53.0.355514242065.issue24272@psf.upfronthosting.co.za> Daniel Andrade Groppe added the comment: Here's a patch for the second half of remaining classes (this file is a complement of Ivan Levkivskyi's patch). ---------- _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Tue Aug 11 05:19:36 2015 From: report at bugs.python.org (Daniel Andrade Groppe) Date: Tue, 11 Aug 2015 03:19:36 +0000 Subject: [docs] [issue24272] PEP 484 docs In-Reply-To: <1432415368.91.0.945654992881.issue24272@psf.upfronthosting.co.za> Message-ID: <1439263176.52.0.470933849034.issue24272@psf.upfronthosting.co.za> Daniel Andrade Groppe added the comment: Missing Generator. ---------- Added file: http://bugs.python.org/file40161/typying_documentation_part2.patch _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Tue Aug 11 06:17:28 2015 From: report at bugs.python.org (Chris Rebert) Date: Tue, 11 Aug 2015 04:17:28 +0000 Subject: [docs] [issue24842] Mention SimpleNamespace in namedtuple docs Message-ID: <1439266648.77.0.275297386928.issue24842@psf.upfronthosting.co.za> New submission from Chris Rebert: There is a cross-reference to namedtuple in SimpleNamespace's docs, but not vice-versa, despite these types being fairly similar. ---------- assignee: docs at python components: Documentation messages: 248389 nosy: cvrebert, docs at python priority: normal severity: normal status: open title: Mention SimpleNamespace in namedtuple docs type: enhancement versions: Python 3.6 _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Tue Aug 11 06:40:33 2015 From: report at bugs.python.org (Serhiy Storchaka) Date: Tue, 11 Aug 2015 04:40:33 +0000 Subject: [docs] [issue24842] Mention SimpleNamespace in namedtuple docs In-Reply-To: <1439266648.77.0.275297386928.issue24842@psf.upfronthosting.co.za> Message-ID: <1439268033.27.0.448648072636.issue24842@psf.upfronthosting.co.za> Changes by Serhiy Storchaka : ---------- assignee: docs at python -> rhettinger nosy: +rhettinger priority: normal -> low _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Tue Aug 11 07:16:59 2015 From: report at bugs.python.org (Benjamin Peterson) Date: Tue, 11 Aug 2015 05:16:59 +0000 Subject: [docs] [issue24832] Issue building viewable docs with newer sphinx (default theme -> classic) In-Reply-To: <1439052495.87.0.415280083267.issue24832@psf.upfronthosting.co.za> Message-ID: <1439270219.23.0.406366470079.issue24832@psf.upfronthosting.co.za> Benjamin Peterson added the comment: Please keep the doc build compatible with Sphinx 1.2.*. Sphinx 1.3.1 has a problem with LaTeX generation, so we can't upgrade the automated docs build to use it until 1.3.2 is released. ---------- nosy: +benjamin.peterson _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Tue Aug 11 08:13:33 2015 From: report at bugs.python.org (Raymond Hettinger) Date: Tue, 11 Aug 2015 06:13:33 +0000 Subject: [docs] [issue24842] Mention SimpleNamespace in namedtuple docs In-Reply-To: <1439266648.77.0.275297386928.issue24842@psf.upfronthosting.co.za> Message-ID: <1439273613.12.0.0778299550824.issue24842@psf.upfronthosting.co.za> Raymond Hettinger added the comment: The NT docs are already very long and I don't think an additional crossref is beneficial (NTs are closer to tuples and SNs are closer to dicts). Also, the uptake for SNs are nearly zero. ---------- _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Tue Aug 11 08:35:10 2015 From: report at bugs.python.org (Stefan Behnel) Date: Tue, 11 Aug 2015 06:35:10 +0000 Subject: [docs] [issue24842] Mention SimpleNamespace in namedtuple docs In-Reply-To: <1439266648.77.0.275297386928.issue24842@psf.upfronthosting.co.za> Message-ID: <1439274910.91.0.269736808315.issue24842@psf.upfronthosting.co.za> Stefan Behnel added the comment: > Also, the uptake for SNs are nearly zero. That suggests to me that pointing users to it could help. It's currently hidden in the types module and if I didn't know it existed, I could end up looking in collections, and failing to find it there, write my own. ---------- nosy: +scoder _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Tue Aug 11 17:02:30 2015 From: report at bugs.python.org (R. David Murray) Date: Tue, 11 Aug 2015 15:02:30 +0000 Subject: [docs] [issue24842] Mention SimpleNamespace in namedtuple docs In-Reply-To: <1439266648.77.0.275297386928.issue24842@psf.upfronthosting.co.za> Message-ID: <1439305350.77.0.914265775233.issue24842@psf.upfronthosting.co.za> R. David Murray added the comment: I use SimpleNamespace in just about every project I'm currently working on. I would *not* say that their uptake is "nearly zero" :) And yes, I wouldn't be aware of it if I hadn't been following python-dev when it was introduced, and had (before it was introduced) written my own variations numerous times. ---------- nosy: +r.david.murray _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Tue Aug 11 20:14:39 2015 From: report at bugs.python.org (Steve Dower) Date: Tue, 11 Aug 2015 18:14:39 +0000 Subject: [docs] [issue24640] no ensurepip in embedded Windows distribution In-Reply-To: <1436992591.69.0.374487494039.issue24640@psf.upfronthosting.co.za> Message-ID: <1439316879.37.0.417432830699.issue24640@psf.upfronthosting.co.za> Steve Dower added the comment: Updated the documentation and it should be in 3.5.0rc1's docs on using with Windows. ---------- resolution: -> fixed stage: -> resolved status: open -> closed _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Thu Aug 13 00:34:53 2015 From: report at bugs.python.org (Robert Collins) Date: Wed, 12 Aug 2015 22:34:53 +0000 Subject: [docs] [issue24079] xml.etree.ElementTree.Element.text does not conform to the documentation In-Reply-To: <1430350495.43.0.91352789573.issue24079@psf.upfronthosting.co.za> Message-ID: <1439418893.79.0.47224478127.issue24079@psf.upfronthosting.co.za> Robert Collins added the comment: So it is downplayed but it is still documented as being application usable. I'll give this another week for Ned to reply, then commit it in the absence of a reply: I think its ok as is. I'd be ok with a tweaked version along the lines Ned proposed too: both ways are better than whats in tree today. ---------- nosy: +rbcollins _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Thu Aug 13 00:37:10 2015 From: report at bugs.python.org (Robert Collins) Date: Wed, 12 Aug 2015 22:37:10 +0000 Subject: [docs] [issue23725] update tempfile docs to say that TemporaryFile is secure In-Reply-To: <1426878892.3.0.689958999466.issue23725@psf.upfronthosting.co.za> Message-ID: <1439419030.55.0.173794127994.issue23725@psf.upfronthosting.co.za> Robert Collins added the comment: Sorry, I didn't realise that Zbigniew was an alternative spelling of your first name. ---------- _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Thu Aug 13 01:38:58 2015 From: report at bugs.python.org (Roundup Robot) Date: Wed, 12 Aug 2015 23:38:58 +0000 Subject: [docs] [issue23725] update tempfile docs to say that TemporaryFile is secure In-Reply-To: <1426878892.3.0.689958999466.issue23725@psf.upfronthosting.co.za> Message-ID: <20150812233854.53414.70879@psf.io> Roundup Robot added the comment: New changeset 51d00482d403 by Robert Collins in branch '3.5': Issue #23725: Overhaul tempfile docs. https://hg.python.org/cpython/rev/51d00482d403 New changeset 256d2f01e975 by Robert Collins in branch 'default': Issue #23725: Overhaul tempfile docs. https://hg.python.org/cpython/rev/256d2f01e975 ---------- nosy: +python-dev _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Thu Aug 13 01:41:21 2015 From: report at bugs.python.org (Robert Collins) Date: Wed, 12 Aug 2015 23:41:21 +0000 Subject: [docs] [issue23725] update tempfile docs to say that TemporaryFile is secure In-Reply-To: <1426878892.3.0.689958999466.issue23725@psf.upfronthosting.co.za> Message-ID: <1439422881.28.0.613875882426.issue23725@psf.upfronthosting.co.za> Robert Collins added the comment: Thanks for the patch. I've committed the current status as an unambiguous improvement; we can add tempdir as deprecated later if there is consensus on that, the current patch did improve its docs per R. David Murray's request anyhow. ---------- resolution: -> fixed stage: commit review -> resolved status: open -> closed _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Thu Aug 13 02:20:34 2015 From: report at bugs.python.org (John Hagen) Date: Thu, 13 Aug 2015 00:20:34 +0000 Subject: [docs] [issue24852] Python 3.5.0rc1 "HOWTO Use Python in the web" needs fix Message-ID: <1439425233.4.0.643704057203.issue24852@psf.upfronthosting.co.za> New submission from John Hagen: https://docs.python.org/3.5/howto/webservers.html#setting-up-fastcgi The "HOWTO Use Python in the web" documentation for 3.5.0rc1 prescribes to use flup in its example, which is not compatible with Python 3. This has led to some confusion: https://stackoverflow.com/questions/23482357/fastcgi-wsgi-library-in-python-3 Perhaps the whole article could be given a once over to ensure it is still the best advice as of 2015. ---------- assignee: docs at python components: Documentation messages: 248491 nosy: John Hagen, docs at python priority: normal severity: normal status: open title: Python 3.5.0rc1 "HOWTO Use Python in the web" needs fix type: enhancement versions: Python 3.5 _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Thu Aug 13 10:48:53 2015 From: report at bugs.python.org (Berker Peksag) Date: Thu, 13 Aug 2015 08:48:53 +0000 Subject: [docs] [issue24852] Python 3.5.0rc1 "HOWTO Use Python in the web" needs fix In-Reply-To: <1439425233.4.0.643704057203.issue24852@psf.upfronthosting.co.za> Message-ID: <1439455733.65.0.890349009187.issue24852@psf.upfronthosting.co.za> Berker Peksag added the comment: +1 I'd delete most of the CGI section, add a note about PEP 3333 and mention Gunicorn, uwsgi and Waitress. The frameworks section also needs a cleanup. Do you want to work on a patch? ---------- nosy: +berker.peksag stage: -> needs patch versions: +Python 3.4, Python 3.6 _______________________________________ Python tracker _______________________________________ From edsmith79 at outlook.com Wed Aug 12 21:33:46 2015 From: edsmith79 at outlook.com (Ed Smith) Date: Wed, 12 Aug 2015 20:33:46 +0100 Subject: [docs] Documentation Message-ID: Hi, As a relative newcomer to the Python language, I just felt like commenting how useful I'm finding the documentation provided on your website. Many thanks! Ed Smith. -------------- next part -------------- An HTML attachment was scrubbed... URL: From nikita.kostylev at gmx.de Mon Aug 10 14:28:41 2015 From: nikita.kostylev at gmx.de (Nikita Kostylev) Date: Mon, 10 Aug 2015 14:28:41 +0200 Subject: [docs] Tutorials Message-ID: <55C898F9.9030309@gmx.de> I am german and can not understand the tutorials good. Can I change the language somehow? Can I find in the Internet all tutorial german? Thanks for helping. From shresthaneha87 at gmail.com Thu Aug 13 08:56:13 2015 From: shresthaneha87 at gmail.com (NEHA SHRESTHA) Date: Thu, 13 Aug 2015 02:56:13 -0400 Subject: [docs] Unable to remove or repair Python 2.7.10 (64-bit) for windows 8.1 Message-ID: Hi, For some reason Python has stopped working in my computer. I recently installed numpy-1.9.2+unoptimized-cp27-none-win_amd64.whl scipy-0.16.0-cp27-none-win_amd64.whl That's the only update I made....A week ago with this install it was working fine but for some reason now it gives me an error saying "This app can't run on your PC. To find a version for your PC, check with the software publisher". When i try to repair or remove it gives me following message. "There is a problem with this Windows Installer package. a program required for this install to complete could not be run. Contact your support personnel or package vendor." Please let me know how can I run python successfully. Regards, Neha Shrestha -------------- next part -------------- An HTML attachment was scrubbed... URL: From Westley.Turner at edd.ca.gov Thu Aug 13 00:04:32 2015 From: Westley.Turner at edd.ca.gov (Turner, Westley@EDD) Date: Wed, 12 Aug 2015 22:04:32 +0000 Subject: [docs] Not a 'bug' just a documentation question Message-ID: <4105B5FB42A1674180CB21798CCEA24A1E49E59B@MRF01DAG4S06.rf01.itservices.ca.gov> I recently have a need to learn some basics about Python, so I was reading through the tutorial. I got to section 2.2.1 and found a reference that isn't clear. The first paragraph there says, "It is possible to use encodings different than ASCII in Python source files. The best way to do it is to put one more special comment line right after the #! line to define the source file encoding:", but there hasn't been a previous mention of a #! line. I am sufficiently familiar with Unix systems to know that scripts usually start with a pointer to the interpreter to be used to run the rest of the script, but many readers may not be. I would suggest a minor entry explaining the differences between scripting and interactive mode. That would give an opportunity to introduce basic shell etiquette. Thanks for the detailed online instructions! I am learning lots. :-) -------------- next part -------------- An HTML attachment was scrubbed... URL: From report at bugs.python.org Thu Aug 13 11:01:39 2015 From: report at bugs.python.org (Georg Brandl) Date: Thu, 13 Aug 2015 09:01:39 +0000 Subject: [docs] [issue24852] Python 3.5.0rc1 "HOWTO Use Python in the web" needs fix In-Reply-To: <1439425233.4.0.643704057203.issue24852@psf.upfronthosting.co.za> Message-ID: <1439456499.38.0.21406933837.issue24852@psf.upfronthosting.co.za> Georg Brandl added the comment: It's probably better to remove the document for now, and add a rewritten version back when it arrives. Although, this topic sees lot of change regularly, so it is probably not a good one for the standard documentation after all. ---------- nosy: +georg.brandl _______________________________________ Python tracker _______________________________________ From mail at timgolden.me.uk Thu Aug 13 12:19:33 2015 From: mail at timgolden.me.uk (Tim Golden) Date: Thu, 13 Aug 2015 11:19:33 +0100 Subject: [docs] Documentation In-Reply-To: References: Message-ID: <55CC6F35.8080708@timgolden.me.uk> On 12/08/2015 20:33, Ed Smith wrote: > Hi, > > As a relative newcomer to the Python language, I just felt like > commenting how useful I?m finding the documentation provided on your > website. > > Many thanks! Thanks for taking the trouble to write an tell is, Ed. As you can imagine, most of the comments we receive are negative, which is understandable. Hopefully you'll continue to enjoy the documentation and the language. TJG From mail at timgolden.me.uk Thu Aug 13 12:24:57 2015 From: mail at timgolden.me.uk (Tim Golden) Date: Thu, 13 Aug 2015 11:24:57 +0100 Subject: [docs] Unable to remove or repair Python 2.7.10 (64-bit) for windows 8.1 In-Reply-To: References: Message-ID: <55CC7079.5030205@timgolden.me.uk> On 13/08/2015 07:56, NEHA SHRESTHA wrote: > Hi, > > For some reason Python has stopped working in my computer. I recently > installed > numpy-1.9.2+unoptimized-cp27-none-win_amd64.whl > scipy-0.16.0-cp27-none-win_amd64.whl > > That's the only update I made....A week ago with this install it was > working fine but for some reason now it gives me an error saying "This > app can't run on your PC. To find a version for your PC, check with the > software publisher". When i try to repair or remove it gives me > following message. "There is a problem with this Windows Installer > package. a program required for this install to complete could not be > run. Contact your support personnel or package vendor." Neha Shrestha, This isn't really the appropriate forum for general topics like yours. You'll do better (and get a wider audience) if you post to the main Python mailing list: https://mail.python.org/mailman/listinfo/python-list When you do post there, be sure to give more detail: does the problem happen when you simply start the Python interpreter? Does it only happen when you run some specific piece of code? etc. TJG From report at bugs.python.org Thu Aug 13 14:04:50 2015 From: report at bugs.python.org (John Hagen) Date: Thu, 13 Aug 2015 12:04:50 +0000 Subject: [docs] [issue24852] Python 3.5.0rc1 "HOWTO Use Python in the web" needs fix In-Reply-To: <1439425233.4.0.643704057203.issue24852@psf.upfronthosting.co.za> Message-ID: <1439467490.94.0.406441763167.issue24852@psf.upfronthosting.co.za> John Hagen added the comment: A couple other notes I saw: The examples (https://docs.python.org/3.5/howto/webservers.html#setting-up-fastcgi) do not follow PEP 8 (should not have an encoding statement if it is UTF-8 Python 3) or the current guidance in PEP 394 to use "python3" in the shebang rather than "python". Unfortunately, I think I should defer writing the patch/new page to someone with more experience in the Python/web world. I am still pretty new to it. ---------- _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Thu Aug 13 20:37:58 2015 From: report at bugs.python.org (Roundup Robot) Date: Thu, 13 Aug 2015 18:37:58 +0000 Subject: [docs] [issue16554] The description of the argument of MAKE_FUNCTION and MAKE_CLOSURE is incorrect In-Reply-To: <1353881740.2.0.222803994959.issue16554@psf.upfronthosting.co.za> Message-ID: <20150813183754.10874.23958@psf.io> Roundup Robot added the comment: New changeset c515b40a70eb by Antoine Pitrou in branch '3.4': Issue #16554: fix description for MAKE_CLOSURE. Initial patch by Daniel Urban. https://hg.python.org/cpython/rev/c515b40a70eb New changeset 2a41fb63c095 by Antoine Pitrou in branch '3.5': Issue #16554: fix description for MAKE_CLOSURE. Initial patch by Daniel Urban. https://hg.python.org/cpython/rev/2a41fb63c095 New changeset 7aed2d7e7dd5 by Antoine Pitrou in branch 'default': Issue #16554: fix description for MAKE_CLOSURE. Initial patch by Daniel Urban. https://hg.python.org/cpython/rev/7aed2d7e7dd5 ---------- nosy: +python-dev _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Thu Aug 13 20:38:33 2015 From: report at bugs.python.org (Antoine Pitrou) Date: Thu, 13 Aug 2015 18:38:33 +0000 Subject: [docs] [issue16554] The description of the argument of MAKE_FUNCTION and MAKE_CLOSURE is incorrect In-Reply-To: <1353881740.2.0.222803994959.issue16554@psf.upfronthosting.co.za> Message-ID: <1439491113.47.0.0570694233811.issue16554@psf.upfronthosting.co.za> Antoine Pitrou added the comment: The description for MAKE_FUNCTION had already been fixed in the meantime, so I pushed the changes for MAKE_CLOSURE. Thank you! ---------- nosy: +pitrou resolution: -> fixed stage: patch review -> resolved status: open -> closed _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Fri Aug 14 22:29:34 2015 From: report at bugs.python.org (Raymond Hettinger) Date: Fri, 14 Aug 2015 20:29:34 +0000 Subject: [docs] [issue24852] Python 3.5.0rc1 "HOWTO Use Python in the web" needs fix In-Reply-To: <1439425233.4.0.643704057203.issue24852@psf.upfronthosting.co.za> Message-ID: <1439584174.18.0.908589120978.issue24852@psf.upfronthosting.co.za> Raymond Hettinger added the comment: > It's probably better to remove the document for now I concur. > Although, this topic sees lot of change regularly, > so it is probably not a good one for the standard > documentation after all. This makes sense. We typically use wiki pages for this kind of material. For example, see the debugging tools page at: https://wiki.python.org/moin/PythonDebuggingTools ---------- nosy: +rhettinger _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Sun Aug 16 17:07:07 2015 From: report at bugs.python.org (Akira Li) Date: Sun, 16 Aug 2015 15:07:07 +0000 Subject: [docs] [issue24842] Mention SimpleNamespace in namedtuple docs In-Reply-To: <1439266648.77.0.275297386928.issue24842@psf.upfronthosting.co.za> Message-ID: <1439737627.4.0.683378249099.issue24842@psf.upfronthosting.co.za> Akira Li added the comment: People do have problems that SimpleNamespace can solve: - Why Python does not support record type i.e. mutable namedtuple [1] - Does Python have anonymous classes? [2] - How to create inline objects with properties in Python? [3] - python create object and add attributes to it [4] [1] http://stackoverflow.com/questions/5227839/why-python-does-not-support-record-type-i-e-mutable-namedtuple [2] http://stackoverflow.com/questions/1123000/does-python-have-anonymous-classes [3] http://stackoverflow.com/questions/1528932/how-to-create-inline-objects-with-properties-in-python [4] http://stackoverflow.com/questions/2827623/python-create-object-and-add-attributes-to-it ---------- nosy: +akira _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Sun Aug 16 17:32:18 2015 From: report at bugs.python.org (Roundup Robot) Date: Sun, 16 Aug 2015 15:32:18 +0000 Subject: [docs] [issue24842] Mention SimpleNamespace in namedtuple docs In-Reply-To: <1439266648.77.0.275297386928.issue24842@psf.upfronthosting.co.za> Message-ID: <20150816153212.6804.64016@psf.io> Roundup Robot added the comment: New changeset 678d93c273de by Raymond Hettinger in branch 'default': Issue #24842: Cross-reference types.SimpleNamespace from the namedtuple docs https://hg.python.org/cpython/rev/678d93c273de ---------- nosy: +python-dev _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Sun Aug 16 17:32:46 2015 From: report at bugs.python.org (Raymond Hettinger) Date: Sun, 16 Aug 2015 15:32:46 +0000 Subject: [docs] [issue24842] Mention SimpleNamespace in namedtuple docs In-Reply-To: <1439266648.77.0.275297386928.issue24842@psf.upfronthosting.co.za> Message-ID: <1439739166.61.0.831805500755.issue24842@psf.upfronthosting.co.za> Changes by Raymond Hettinger : ---------- resolution: -> fixed status: open -> closed _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Mon Aug 17 06:28:58 2015 From: report at bugs.python.org (Raymond Hettinger) Date: Mon, 17 Aug 2015 04:28:58 +0000 Subject: [docs] [issue24878] Add docstrings to selected named tuples Message-ID: <1439785738.06.0.883729285767.issue24878@psf.upfronthosting.co.za> New submission from Raymond Hettinger: Add docstrings to some named tuples that could benefit from it (there was more documentation or useful information other than just the field name). This makes the help() on those named tuples much more informative. ---------- assignee: docs at python components: Documentation files: ntdoc.diff keywords: patch messages: 248712 nosy: docs at python, rhettinger priority: low severity: normal stage: patch review status: open title: Add docstrings to selected named tuples versions: Python 3.6 Added file: http://bugs.python.org/file40193/ntdoc.diff _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Mon Aug 17 06:32:47 2015 From: report at bugs.python.org (Raymond Hettinger) Date: Mon, 17 Aug 2015 04:32:47 +0000 Subject: [docs] [issue24878] Add docstrings to selected named tuples In-Reply-To: <1439785738.06.0.883729285767.issue24878@psf.upfronthosting.co.za> Message-ID: <1439785967.22.0.910527052706.issue24878@psf.upfronthosting.co.za> Raymond Hettinger added the comment: For example: >>> import sched >>> help(sched.Event) class Event(Event) | Event(time, priority, action, argument, kwargs) | ... | ---------------------------------------------------------------------- | Data descriptors inherited from Event: | | action | Executing the event means executing | action(*argument, **kwargs) | | argument | argument is a sequence holding the positional | arguments for the action. | | kwargs | kwargs is a dictionary holding the keyword | arguments for the action. | | priority | Events scheduled for the same time will be executed | in the order of their priority. | | time | Numeric type compatible with the return value of the | timefunc function passed to the constructor. ---------- _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Mon Aug 17 20:08:36 2015 From: report at bugs.python.org (Raymond Hettinger) Date: Mon, 17 Aug 2015 18:08:36 +0000 Subject: [docs] [issue24878] Add docstrings to selected named tuples In-Reply-To: <1439785738.06.0.883729285767.issue24878@psf.upfronthosting.co.za> Message-ID: <1439834916.3.0.579655935506.issue24878@psf.upfronthosting.co.za> Changes by Raymond Hettinger : Added file: http://bugs.python.org/file40197/ntdoc2.diff _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Tue Aug 18 04:17:03 2015 From: report at bugs.python.org (Roundup Robot) Date: Tue, 18 Aug 2015 02:17:03 +0000 Subject: [docs] [issue24079] xml.etree.ElementTree.Element.text does not conform to the documentation In-Reply-To: <1430350495.43.0.91352789573.issue24079@psf.upfronthosting.co.za> Message-ID: <20150818021644.36745.32430@psf.io> Roundup Robot added the comment: New changeset d3cda8cf4d42 by Ned Deily in branch '2.7': Issue #24079: Improve description of the text and tail attributes for https://hg.python.org/cpython/rev/d3cda8cf4d42 New changeset ad0491f85050 by Ned Deily in branch '3.4': Issue #24079: Improve description of the text and tail attributes for https://hg.python.org/cpython/rev/ad0491f85050 New changeset 17ce3486fd8f by Ned Deily in branch '3.5': Issue #24079: merge from 3.4 https://hg.python.org/cpython/rev/17ce3486fd8f New changeset 3c94ece57c43 by Ned Deily in branch 'default': Issue #24079: merge from 3.5 https://hg.python.org/cpython/rev/3c94ece57c43 ---------- nosy: +python-dev _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Tue Aug 18 04:20:53 2015 From: report at bugs.python.org (Ned Deily) Date: Tue, 18 Aug 2015 02:20:53 +0000 Subject: [docs] [issue24079] xml.etree.ElementTree.Element.text does not conform to the documentation In-Reply-To: <1430350495.43.0.91352789573.issue24079@psf.upfronthosting.co.za> Message-ID: <1439864453.59.0.237804812584.issue24079@psf.upfronthosting.co.za> Ned Deily added the comment: Thanks for all of your contributions on this. I've committed a version along the lines I suggested along with Martin's example. ---------- resolution: -> fixed stage: commit review -> resolved status: open -> closed type: behavior -> _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Tue Aug 18 07:04:54 2015 From: report at bugs.python.org (Roundup Robot) Date: Tue, 18 Aug 2015 05:04:54 +0000 Subject: [docs] [issue24878] Add docstrings to selected named tuples In-Reply-To: <1439785738.06.0.883729285767.issue24878@psf.upfronthosting.co.za> Message-ID: <20150818050451.4925.92360@psf.io> Roundup Robot added the comment: New changeset 40f2bbb922e6 by Raymond Hettinger in branch 'default': Issue #24878: Add docstrings to selected namedtuples https://hg.python.org/cpython/rev/40f2bbb922e6 ---------- nosy: +python-dev _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Tue Aug 18 07:05:16 2015 From: report at bugs.python.org (Raymond Hettinger) Date: Tue, 18 Aug 2015 05:05:16 +0000 Subject: [docs] [issue24878] Add docstrings to selected named tuples In-Reply-To: <1439785738.06.0.883729285767.issue24878@psf.upfronthosting.co.za> Message-ID: <1439874316.18.0.333080754371.issue24878@psf.upfronthosting.co.za> Changes by Raymond Hettinger : ---------- resolution: -> fixed stage: patch review -> resolved status: open -> closed _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Tue Aug 18 07:13:22 2015 From: report at bugs.python.org (TAKASE Arihiro) Date: Tue, 18 Aug 2015 05:13:22 +0000 Subject: [docs] [issue24883] Typo in c-api/buffer documentation Message-ID: <1439874802.02.0.402789203299.issue24883@psf.upfronthosting.co.za> New submission from TAKASE Arihiro: https://docs.python.org/3/c-api/buffer.html Some links to the members of Py_buffer are not available. "~Py_Buffer" should be "~Py_buffer". The attached patch fixes it. ---------- assignee: docs at python components: Documentation files: bufferdoc.patch keywords: patch messages: 248758 nosy: artakase, docs at python priority: normal severity: normal status: open title: Typo in c-api/buffer documentation type: behavior versions: Python 3.4, Python 3.5, Python 3.6 Added file: http://bugs.python.org/file40200/bufferdoc.patch _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Tue Aug 18 08:20:17 2015 From: report at bugs.python.org (Stefan Behnel) Date: Tue, 18 Aug 2015 06:20:17 +0000 Subject: [docs] [issue24079] xml.etree.ElementTree.Element.text does not conform to the documentation In-Reply-To: <1430350495.43.0.91352789573.issue24079@psf.upfronthosting.co.za> Message-ID: <1439878817.31.0.604403376224.issue24079@psf.upfronthosting.co.za> Stefan Behnel added the comment: The "can store arbitrary objects" sentence is now duplicated, and still way too visible. I have to read three sentences until it tells me what I need to know. ---------- _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Tue Aug 18 08:29:21 2015 From: report at bugs.python.org (Stefan Behnel) Date: Tue, 18 Aug 2015 06:29:21 +0000 Subject: [docs] [issue24079] xml.etree.ElementTree.Element.text does not conform to the documentation In-Reply-To: <1430350495.43.0.91352789573.issue24079@psf.upfronthosting.co.za> Message-ID: <1439879361.65.0.697372211376.issue24079@psf.upfronthosting.co.za> Stefan Behnel added the comment: I think the first two sentences can simply be removed to fix this, without loss of readability or information. ---------- _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Tue Aug 18 08:39:23 2015 From: report at bugs.python.org (Roundup Robot) Date: Tue, 18 Aug 2015 06:39:23 +0000 Subject: [docs] [issue24883] Typo in c-api/buffer documentation In-Reply-To: <1439874802.02.0.402789203299.issue24883@psf.upfronthosting.co.za> Message-ID: <20150818063920.13734.26866@psf.io> Roundup Robot added the comment: New changeset 0c5af3e398f0 by Benjamin Peterson in branch '3.4': 'Py_Buffer' should be 'Py_buffer' (closes #24883) https://hg.python.org/cpython/rev/0c5af3e398f0 New changeset 76892906253c by Benjamin Peterson in branch '3.5': merge 3.4 (#24883) https://hg.python.org/cpython/rev/76892906253c New changeset c1e6bc6a9d69 by Benjamin Peterson in branch 'default': Merge 3.5 (#24883) https://hg.python.org/cpython/rev/c1e6bc6a9d69 ---------- nosy: +python-dev resolution: -> fixed stage: -> resolved status: open -> closed _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Tue Aug 18 12:17:36 2015 From: report at bugs.python.org (Petr Viktorin) Date: Tue, 18 Aug 2015 10:17:36 +0000 Subject: [docs] [issue24878] Add docstrings to selected named tuples In-Reply-To: <1439785738.06.0.883729285767.issue24878@psf.upfronthosting.co.za> Message-ID: <1439893056.52.0.0412191613658.issue24878@psf.upfronthosting.co.za> Petr Viktorin added the comment: I see some typos in aifc.py: +_aifc_params.sampwidth.__doc__ = 'Ample width in bytes' +_aifc_params.compname.__doc__ = ("""A human-readable version ofcompression type Should that be "Sample width" and "of compression"? ---------- nosy: +encukou _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Tue Aug 18 16:36:31 2015 From: report at bugs.python.org (Geoffrey Royer) Date: Tue, 18 Aug 2015 14:36:31 +0000 Subject: [docs] [issue24888] FileNotFoundException raised by subprocess.call Message-ID: <1439908591.24.0.224694175166.issue24888@psf.upfronthosting.co.za> New submission from Geoffrey Royer: According to the documentation of the subprocess.check_call function: https://docs.python.org/3/library/subprocess.html#subprocess.check_call It would be nice to notify the reader that this function can raise FileNotFoundException. It is raised in case when the binary one wants to call does not exist. Example: Python 3.4.0 (default, Jun 19 2015, 14:20:21) [GCC 4.8.2] on linux Type "help", "copyright", "credits" or "license" for more information. >>> import subprocess >>> subprocess.check_call(["foo", "bar"]) Traceback (most recent call last): File "", line 1, in File "/usr/lib/python3.4/subprocess.py", line 552, in check_call retcode = call(*popenargs, **kwargs) File "/usr/lib/python3.4/subprocess.py", line 533, in call with Popen(*popenargs, **kwargs) as p: File "/usr/lib/python3.4/subprocess.py", line 848, in __init__ restore_signals, start_new_session) File "/usr/lib/python3.4/subprocess.py", line 1446, in _execute_child raise child_exception_type(errno_num, err_msg) FileNotFoundError: [Errno 2] No such file or directory: 'foo' ---------- assignee: docs at python components: Documentation messages: 248773 nosy: Geoffrey Royer, docs at python priority: normal severity: normal status: open title: FileNotFoundException raised by subprocess.call _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Tue Aug 18 16:43:45 2015 From: report at bugs.python.org (R. David Murray) Date: Tue, 18 Aug 2015 14:43:45 +0000 Subject: [docs] [issue24888] FileNotFoundException raised by subprocess.call In-Reply-To: <1439908591.24.0.224694175166.issue24888@psf.upfronthosting.co.za> Message-ID: <1439909025.33.0.988937657056.issue24888@psf.upfronthosting.co.za> R. David Murray added the comment: We don't in general document all the exceptions that can be raised by a piece of code. This could be an edge case, though. Let's see what others thing. ---------- nosy: +r.david.murray _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Tue Aug 18 16:44:02 2015 From: report at bugs.python.org (R. David Murray) Date: Tue, 18 Aug 2015 14:44:02 +0000 Subject: [docs] [issue24888] FileNotFoundException raised by subprocess.call In-Reply-To: <1439908591.24.0.224694175166.issue24888@psf.upfronthosting.co.za> Message-ID: <1439909042.47.0.717122141345.issue24888@psf.upfronthosting.co.za> R. David Murray added the comment: think. ---------- _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Tue Aug 18 16:47:06 2015 From: report at bugs.python.org (Geoffrey Royer) Date: Tue, 18 Aug 2015 14:47:06 +0000 Subject: [docs] [issue24888] FileNotFoundException raised by subprocess.call In-Reply-To: <1439908591.24.0.224694175166.issue24888@psf.upfronthosting.co.za> Message-ID: <1439909226.78.0.635210740381.issue24888@psf.upfronthosting.co.za> Changes by Geoffrey Royer : ---------- versions: +Python 3.4 _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Tue Aug 18 16:53:33 2015 From: report at bugs.python.org (Geoffrey Royer) Date: Tue, 18 Aug 2015 14:53:33 +0000 Subject: [docs] [issue24888] FileNotFoundException raised by subprocess.call In-Reply-To: <1439908591.24.0.224694175166.issue24888@psf.upfronthosting.co.za> Message-ID: <1439909613.02.0.46487992205.issue24888@psf.upfronthosting.co.za> Changes by Geoffrey Royer : ---------- type: -> behavior _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Tue Aug 18 20:50:17 2015 From: report at bugs.python.org (Yury Selivanov) Date: Tue, 18 Aug 2015 18:50:17 +0000 Subject: [docs] [issue24692] types.coroutines() idempotence documentation In-Reply-To: <1437650502.32.0.0288592289227.issue24692@psf.upfronthosting.co.za> Message-ID: <1439923817.23.0.403237731294.issue24692@psf.upfronthosting.co.za> Yury Selivanov added the comment: Is this still something that we need to address? I think that the current types.coroutine docs are pretty accurate and don't see where the proposed patch really improves them. ---------- nosy: +yselivanov _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Wed Aug 19 03:34:58 2015 From: report at bugs.python.org (eryksun) Date: Wed, 19 Aug 2015 01:34:58 +0000 Subject: [docs] [issue24890] Windows launcher docs don't fully explain shebang semantics In-Reply-To: <1439932466.21.0.43365988759.issue24890@psf.upfronthosting.co.za> Message-ID: <1439948098.04.0.0222199705474.issue24890@psf.upfronthosting.co.za> eryksun added the comment: The patch for issue 23465 (PEP 486) updated the docs to explain the behavior of #!/usr/bin/env as follows: The /usr/bin/env form of shebang line has one further special property. Before looking for installed Python interpreters, this form will search the executable PATH for a Python executable. This corresponds to the behaviour of the Unix env program, which performs a PATH search. This paragraph needs to be added to the 3.4 docs. Another undocumented feature is adding custom commands in the [commands] section of py.ini. The read_commands function handles this. Speaking of which, a side effect of defining SEARCH_PATH in PC/launcher.c is that PATH is searched in find_command if the command isn't found in the global "commands" array. This can lead to unexpected behavior when combined with SKIP_PREFIX (i.e. the skip_prefix function skips past any of the builtin_prefixes in the shebang). For example, #!/usr/bin/perl will search the current directory and PATH for "perl.COM" "perl.EXE", "perl.BAT", etc (i.e. trying each extension listed in PATHEXT). This behavior should be documented. Preferably I think it should also be constrained to only search when the prefix is /usr/bin/env, such as by adding a "search" boolean parameter to the find_command function. ---------- assignee: -> docs at python components: +Documentation nosy: +docs at python, eryksun versions: +Python 3.4 _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Wed Aug 19 08:10:25 2015 From: report at bugs.python.org (Ezio Melotti) Date: Wed, 19 Aug 2015 06:10:25 +0000 Subject: [docs] [issue24894] iso-8859-11 missing from codecs table Message-ID: <1439964625.02.0.805508700241.issue24894@psf.upfronthosting.co.za> New submission from Ezio Melotti: In https://docs.python.org/3/library/codecs.html#standard-encodings iso8859_11 appears to be missing. 'thai' seems a valid alias for this encoding, but there might be others. cp874 also covers the thai alphabet, but it's a different encoding. Note that iso8859_12 is also missing, but that is expected. See also https://en.wikipedia.org/wiki/ISO/IEC_8859#The_Parts_of_ISO.2FIEC_8859 ---------- assignee: docs at python components: Documentation, Unicode keywords: easy messages: 248819 nosy: docs at python, ezio.melotti, haypo priority: normal severity: normal stage: needs patch status: open title: iso-8859-11 missing from codecs table type: enhancement versions: Python 2.7, Python 3.3, Python 3.4, Python 3.5, Python 3.6 _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Wed Aug 19 11:43:30 2015 From: report at bugs.python.org (=?utf-8?q?Gerhard_H=C3=A4ring?=) Date: Wed, 19 Aug 2015 09:43:30 +0000 Subject: [docs] [issue11691] sqlite3 Cursor.description doesn't set type_code In-Reply-To: <1301199375.2.0.455501522423.issue11691@psf.upfronthosting.co.za> Message-ID: <1439977410.01.0.988432014823.issue11691@psf.upfronthosting.co.za> Gerhard H?ring added the comment: There is no guarantee that all any column in a SQlite resultset always has the same type. That's why I decided to err on the side of setting the type code to "undefined". Closing as wontfix. ---------- resolution: -> wont fix status: open -> closed _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Wed Aug 19 14:38:11 2015 From: report at bugs.python.org (Leif Arne Storset) Date: Wed, 19 Aug 2015 12:38:11 +0000 Subject: [docs] [issue24896] It is undocumented that re.UNICODE affects re.IGNORECASE Message-ID: <1439987891.31.0.547960058443.issue24896@psf.upfronthosting.co.za> New submission from Leif Arne Storset: A non-ASCII string does not match a regular expression case-insensitively unless the UNICODE flag is set. This seems reasonable, but the documentation seems to imply that this is not the case. The example: import re # Does not match re.compile(u"???????????????", re.IGNORECASE) \ .findall(u"???????????????") # Matches re.compile(u"???????????????", re.IGNORECASE | re.UNICODE) \ .findall(u"???????????????") (In Python 3, it does not match if re.ASCII is given.) The documentation (2.7) says: re.UNICODE Make \w, \W, \b, \B, \d, \D, \s and \S dependent on the Unicode character properties database. (https://docs.python.org/2/library/re.html#re.UNICODE) My regex does not use any of those escapes, yet the regex changes behavior with the UNICODE flag. This leads to confusion when the regex doesn't match. The documentation is very specific about the behavior that changes with the flag, implying that behavior not mentioned is unaffected. Of course, it's easy to guess the correct (hopefully) solution. Still, I suggest changing the documentation to mention that re.IGNORECASE is affected. Looking at the source code, there seems to be further consequences (it mentions "Unicode locale") which may also warrant a mention. If you do want to avoid specifics, however, even a hand-wavy reference to something like "match according to Unicode" would help, because it implies that not only the escapes change behavior. In Python 3, there is a counterpart to the 2.7 problem: re.ASCII makes our Cyrillic string not match. Again, this behavior makes intuitive sense, but the documentation seems to indicate something different: re.ASCII Make \w, \W, \b, \B, \d, \D, \s and \S perform ASCII-only matching instead of full Unicode matching. This is only meaningful for Unicode patterns, and is ignored for byte patterns. ? re.IGNORECASE Perform case-insensitive matching; expressions like [A-Z] will match lowercase letters, too. This is not affected by the current locale and works for Unicode characters as expected. re.ASCII does appear to affect re.IGNORECASE. Since this is the non-default case, however, I'm not sure it's worth calling it out. I'd be happy even if only the 2.7 docs change. ---------- assignee: docs at python components: Documentation messages: 248829 nosy: Leif Arne Storset, docs at python priority: normal severity: normal status: open title: It is undocumented that re.UNICODE affects re.IGNORECASE versions: Python 2.7, Python 3.4 _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Wed Aug 19 15:12:34 2015 From: report at bugs.python.org (R. David Murray) Date: Wed, 19 Aug 2015 13:12:34 +0000 Subject: [docs] [issue24896] It is undocumented that re.UNICODE affects re.IGNORECASE In-Reply-To: <1439987891.31.0.547960058443.issue24896@psf.upfronthosting.co.za> Message-ID: <1439989954.06.0.497096163147.issue24896@psf.upfronthosting.co.za> R. David Murray added the comment: I think it would be reasonable to add re.IGNORECASE to the list of things affected, since it obviously does switch between using the unicode database and not doing so. ---------- nosy: +r.david.murray _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Thu Aug 20 04:34:48 2015 From: report at bugs.python.org (Ted Lemon) Date: Thu, 20 Aug 2015 02:34:48 +0000 Subject: [docs] [issue24898] Documentation for str.find() is confusing Message-ID: <1440038088.25.0.955584919768.issue24898@psf.upfronthosting.co.za> New submission from Ted Lemon: The documentation for str.find() on python.org, for all current versions, says: Return the lowest index in the string where substring sub is found, such that sub is contained in the slice s[start:end]. Optional arguments start and end are interpreted as in slice notation. Return -1 if sub is not found. I think that what is meant here is this: Return the lowest index in a string s where substring sub is found, such that if a is the returned index, and b == a + len(sub), sub is contained in the slice s[a:b]. Optional arguments start and end are interpreted as in slice notation. Return -1 if sub is not found. ---------- assignee: docs at python components: Documentation messages: 248872 nosy: Ted Lemon, docs at python priority: normal severity: normal status: open title: Documentation for str.find() is confusing versions: Python 3.6 _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Thu Aug 20 07:49:23 2015 From: report at bugs.python.org (Georg Brandl) Date: Thu, 20 Aug 2015 05:49:23 +0000 Subject: [docs] [issue24898] Documentation for str.find() is confusing In-Reply-To: <1440038088.25.0.955584919768.issue24898@psf.upfronthosting.co.za> Message-ID: <1440049763.46.0.0421925165752.issue24898@psf.upfronthosting.co.za> Georg Brandl added the comment: The "slice" clause is talking about the additional arguments. A clearer version could be Return the lowest index in the string where substring sub is found within the slice s[start:end]. Optional arguments start and end are interpreted as in slice notation. Return -1 if sub is not found. ---------- nosy: +georg.brandl _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Thu Aug 20 08:03:37 2015 From: report at bugs.python.org (Ezio Melotti) Date: Thu, 20 Aug 2015 06:03:37 +0000 Subject: [docs] [issue24899] Add an os.path <=> pathlib equivalence table in pathlib docs Message-ID: <1440050617.44.0.44226546659.issue24899@psf.upfronthosting.co.za> New submission from Ezio Melotti: I think it would be useful to add to the pathlib documentation a table listing os/os.path operations and their pathlib equivalent. This will be useful both for people porting their code to pathlib and for people that already know os/os.path and want to get familiar with pathlib. ---------- assignee: docs at python components: Documentation keywords: easy messages: 248877 nosy: docs at python, ezio.melotti, pitrou priority: normal severity: normal stage: needs patch status: open title: Add an os.path <=> pathlib equivalence table in pathlib docs type: enhancement versions: Python 3.4, Python 3.5, Python 3.6 _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Thu Aug 20 16:54:13 2015 From: report at bugs.python.org (Ted Lemon) Date: Thu, 20 Aug 2015 14:54:13 +0000 Subject: [docs] [issue24898] Documentation for str.find() is confusing In-Reply-To: <1440038088.25.0.955584919768.issue24898@psf.upfronthosting.co.za> Message-ID: <1440082453.68.0.0405684939943.issue24898@psf.upfronthosting.co.za> Ted Lemon added the comment: Hm, okay, that explains it. I was previously mystified. How about this as a refinement on your proposal, though: Return the lowest index in the string where substring sub is found within the string. Optional arguments start and end restrict the search to the slice of the string, s[start:end]. Returned index is relative to the beginning of the string, not the beginning of the slice. Return -1 if sub is not found. ---------- _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Fri Aug 21 03:41:34 2015 From: report at bugs.python.org (Robert Collins) Date: Fri, 21 Aug 2015 01:41:34 +0000 Subject: [docs] [issue24247] "unittest discover" modifies sys.path In-Reply-To: <1432145504.49.0.0792649435806.issue24247@psf.upfronthosting.co.za> Message-ID: <1440121294.05.0.137322228835.issue24247@psf.upfronthosting.co.za> Robert Collins added the comment: It did that because you did not specify a top level directory. Without that, the cwd is not on the path and that breaks many environments. We should probably document it better. The workaround for your needs is to either just run 'unittest discover', or run 'unittest discover tests -t .', not 'unittest discover tests'. The behaviour is however something I believe to be correct and essential to most user experiences. ---------- assignee: -> docs at python components: +Documentation nosy: +docs at python stage: -> needs patch title: "unittest discover" does modify sys.path -> "unittest discover" modifies sys.path _______________________________________ Python tracker _______________________________________ From atribone at gmail.com Tue Aug 18 06:56:03 2015 From: atribone at gmail.com (Andrew Tribone) Date: Mon, 17 Aug 2015 21:56:03 -0700 Subject: [docs] Commas at the end of lists and tuples Message-ID: https://docs.python.org/2/faq/design.html#why-does-python-allow-commas-at-the-end-of-lists-and-tuples I was wondering why this section does not talk about the fact that this is the only way to create a 1-tuple. And the danger of refactoring arguments of a function without removing the comma. Not sure if this has been brought up, I couldn't find an easy way to grep the archive without download all of the months. I would be happy to update the copy if I knew how to get it submitted and reviewed. Cheers. -------------- next part -------------- An HTML attachment was scrubbed... URL: From report at bugs.python.org Fri Aug 21 22:34:07 2015 From: report at bugs.python.org (zodalahtathi) Date: Fri, 21 Aug 2015 20:34:07 +0000 Subject: [docs] [issue24911] Context manager of socket.socket is not documented Message-ID: <1440189246.69.0.0632097129757.issue24911@psf.upfronthosting.co.za> New submission from zodalahtathi: socket.socket has a context manager to automatically close the socket with the `with` statement: https://hg.python.org/cpython/file/d1bf181afa82/Lib/socket.py#l138 However it is not documented, unlike socket.create_connection. ---------- assignee: docs at python components: Documentation messages: 248979 nosy: docs at python, zodalahtathi priority: normal severity: normal status: open title: Context manager of socket.socket is not documented versions: Python 3.4 _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Sat Aug 22 08:45:11 2015 From: report at bugs.python.org (Paddy McCarthy) Date: Sat, 22 Aug 2015 06:45:11 +0000 Subject: [docs] [issue24914] Python: Not just OO style but this is not mentioned on python.org or in FAQ Message-ID: <1440225910.92.0.539487452884.issue24914@psf.upfronthosting.co.za> New submission from Paddy McCarthy: Just read http://www.ibmsystemsmag.com/ibmi/developer/general/different-world-python/?utm_campaign=ibm-enews&utm_medium=email&utm_source=ibmi-jul22-2015?&utm_content=exclusive1-headline It states that they could have had an officially supported version of Python on that IBM platform much earlier but for this: > "The second was that everything we read on Python, and all the examples we encountered, led us to believe that it was a completely object oriented (OO) language" They may have used it earlier had they known then that Python can be written in a procedural style they having no love of Java's OO, but being able to use PHP and access PHP's OO bits. Looking again on python.org, the examples are not OO, but when you delve down, say to the FAQ - it gives the mistaken impression that OO is the _only_ style of programming supported: https://docs.python.org/2/faq/general.html#what-is-python Somehow we need to explain that OO is an implementation style, but the language allows code to be written in just as much - or as little, of proceedural/OO/functional styles as the programmer is comfortable with. ---------- assignee: docs at python components: Documentation messages: 248987 nosy: Paddy McCarthy, docs at python priority: normal severity: normal status: open title: Python: Not just OO style but this is not mentioned on python.org or in FAQ type: enhancement _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Sun Aug 23 03:45:49 2015 From: report at bugs.python.org (Brett Cannon) Date: Sun, 23 Aug 2015 01:45:49 +0000 Subject: [docs] [issue24914] Python: Not just OO style but this is not mentioned on python.org or in FAQ In-Reply-To: <1440225910.92.0.539487452884.issue24914@psf.upfronthosting.co.za> Message-ID: <1440294349.1.0.602377094732.issue24914@psf.upfronthosting.co.za> Brett Cannon added the comment: The problem is that technically Python is an object-oriented language as everything is a language (which is what makes Python more OO than Java). Having said that, you can use other programming styles. I'm fine with clarifying the entry in the FAQ that Python can be written in other programming styles such as procedural or functional. If you have suggested wording, Paddy, please feel free to propose a patch. ---------- nosy: +brett.cannon stage: -> needs patch versions: +Python 3.6 _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Sun Aug 23 08:52:07 2015 From: report at bugs.python.org (Paddy McCarthy) Date: Sun, 23 Aug 2015 06:52:07 +0000 Subject: [docs] [issue24914] Python: Not just OO style but this is not mentioned on python.org or in FAQ In-Reply-To: <1440225910.92.0.539487452884.issue24914@psf.upfronthosting.co.za> Message-ID: <1440312727.77.0.353824948397.issue24914@psf.upfronthosting.co.za> Paddy McCarthy added the comment: OK, here's a suggested re-wording: "Python is an interpreted, interactive, object-oriented programming language that also supports programming in procedural and functional styles. It incorporates modules, exceptions, dynamic typing, very high level dynamic data types, and classes; but statements are not required to be contained in class definitions and functions are first class - being able to be composed, returned from other functions and be a member of other container types such as dicts, sets, and lists." If that is too long,an alternative would be to delete my addition to the last sentence from "; but classes are not ..." Leaving it to the reader to research just how procedural and functional Python can be. (Where should a programmer, but newbie-to-Python look)? ---------- _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Sun Aug 23 20:28:10 2015 From: report at bugs.python.org (Roundup Robot) Date: Sun, 23 Aug 2015 18:28:10 +0000 Subject: [docs] [issue24878] Add docstrings to selected named tuples In-Reply-To: <1439785738.06.0.883729285767.issue24878@psf.upfronthosting.co.za> Message-ID: <20150823182807.67848.22866@psf.io> Roundup Robot added the comment: New changeset 4432c441b639 by Raymond Hettinger in branch 'default': Issue #24878: Fix typos and line wrap https://hg.python.org/cpython/rev/4432c441b639 ---------- _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Sun Aug 23 20:28:24 2015 From: report at bugs.python.org (Raymond Hettinger) Date: Sun, 23 Aug 2015 18:28:24 +0000 Subject: [docs] [issue24878] Add docstrings to selected named tuples In-Reply-To: <1439785738.06.0.883729285767.issue24878@psf.upfronthosting.co.za> Message-ID: <1440354504.96.0.475444784317.issue24878@psf.upfronthosting.co.za> Raymond Hettinger added the comment: Thanks Petr ---------- _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Sun Aug 23 22:20:07 2015 From: report at bugs.python.org (asldkjfn) Date: Sun, 23 Aug 2015 20:20:07 +0000 Subject: [docs] [issue24918] Docs layout bug Message-ID: <1440361207.71.0.0873906255469.issue24918@psf.upfronthosting.co.za> New submission from asldkjfn: Green bars cover yellow text box. https://docs.python.org/2/faq/windows.html ---------- assignee: docs at python components: Documentation messages: 249018 nosy: docs at python, reag priority: normal severity: normal status: open title: Docs layout bug versions: Python 2.7 _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Sun Aug 23 22:59:59 2015 From: report at bugs.python.org (Carol Willing) Date: Sun, 23 Aug 2015 20:59:59 +0000 Subject: [docs] [issue24918] Docs layout bug In-Reply-To: <1440361207.71.0.0873906255469.issue24918@psf.upfronthosting.co.za> Message-ID: <1440363599.59.0.786459956611.issue24918@psf.upfronthosting.co.za> Carol Willing added the comment: The highlighting of code box extends beyond the bounds of the box to the far right of the page. A screenshot is attached as an example. The behavior occurs on all versions (3.2+, 2.7.x) except 2.6. Thanks for reporting this issue. ---------- nosy: +willingc stage: -> needs patch type: -> behavior versions: +Python 3.2, Python 3.3, Python 3.4, Python 3.5, Python 3.6 Added file: http://bugs.python.org/file40235/Screenshot 2015-08-23 16.55.34.png _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Mon Aug 24 02:11:04 2015 From: report at bugs.python.org (Roundup Robot) Date: Mon, 24 Aug 2015 00:11:04 +0000 Subject: [docs] [issue22812] Documentation of unittest -p usage wrong on windows. In-Reply-To: <1415354409.44.0.0207378794997.issue22812@psf.upfronthosting.co.za> Message-ID: <20150824001057.79919.69113@psf.io> Roundup Robot added the comment: New changeset 3256764fadae by Robert Collins in branch '2.7': Issue #22812: Fix unittest discovery examples. https://hg.python.org/cpython/rev/3256764fadae ---------- nosy: +python-dev _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Mon Aug 24 02:16:28 2015 From: report at bugs.python.org (Roundup Robot) Date: Mon, 24 Aug 2015 00:16:28 +0000 Subject: [docs] [issue22812] Documentation of unittest -p usage wrong on windows. In-Reply-To: <1415354409.44.0.0207378794997.issue22812@psf.upfronthosting.co.za> Message-ID: <20150824001618.27305.8936@psf.io> Roundup Robot added the comment: New changeset e285606efb82 by Robert Collins in branch '3.4': Issue #22812: Fix unittest discovery examples. https://hg.python.org/cpython/rev/e285606efb82 New changeset 875a851b9d5a by Robert Collins in branch '3.5': Issue #22812: Fix unittest discovery examples. https://hg.python.org/cpython/rev/875a851b9d5a New changeset d9ec88a1e5d6 by Robert Collins in branch 'default': Issue #22812: Fix unittest discovery examples. https://hg.python.org/cpython/rev/d9ec88a1e5d6 ---------- _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Mon Aug 24 02:17:41 2015 From: report at bugs.python.org (Robert Collins) Date: Mon, 24 Aug 2015 00:17:41 +0000 Subject: [docs] [issue22812] Documentation of unittest -p usage wrong on windows. In-Reply-To: <1415354409.44.0.0207378794997.issue22812@psf.upfronthosting.co.za> Message-ID: <1440375461.35.0.373684202171.issue22812@psf.upfronthosting.co.za> Robert Collins added the comment: Thanks for the patch! ---------- resolution: -> fixed stage: needs patch -> resolved status: open -> closed _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Mon Aug 24 15:08:32 2015 From: report at bugs.python.org (Joseph Schachner) Date: Mon, 24 Aug 2015 13:08:32 +0000 Subject: [docs] [issue24921] Operator precedence table in 5.15 should be highest to lowest precedence Message-ID: <1440421712.73.0.607673856693.issue24921@psf.upfronthosting.co.za> New submission from Joseph Schachner: We should not make people who need to read Python documentation do an extra transformation in their heads to correctly understand that in section 5.15 higher precedence is at the bottom of the table and lower precedence is at the top. Because the documentation has this table inverted from the way it is usually presented in other references, one of the top hits in a Google search shows an instructor felt the need to make a version in the usual "high to low precedence" order to show students, see: http://www.mathcs.emory.edu/~valerie/courses/fall10/155/resources/op_precedence.html That version is so much more comfortable for me to read, it seems almost strange, but it is true. Please consider changing section 5.15 so it would not need the top paragraph explaining that the table order is not what the reader probably expects, instead just present the table as at the link above - in the order the reader does expect - higher precedence on top, lower on the bottom. That only needs two short sentences of explanation that don't make the reader think "wait ... what?" ---------- assignee: docs at python components: Documentation messages: 249046 nosy: Joseph Schachner, docs at python priority: normal severity: normal status: open title: Operator precedence table in 5.15 should be highest to lowest precedence versions: Python 2.7 _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Mon Aug 24 16:43:00 2015 From: report at bugs.python.org (Stefan Krah) Date: Mon, 24 Aug 2015 14:43:00 +0000 Subject: [docs] [issue24921] Operator precedence table in 5.15 should be highest to lowest precedence In-Reply-To: <1440421712.73.0.607673856693.issue24921@psf.upfronthosting.co.za> Message-ID: <1440427380.16.0.758780932555.issue24921@psf.upfronthosting.co.za> Stefan Krah added the comment: Yacc uses low to high. ---------- nosy: +skrah _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Mon Aug 24 17:12:05 2015 From: report at bugs.python.org (Skip Montanaro) Date: Mon, 24 Aug 2015 15:12:05 +0000 Subject: [docs] [issue24921] Operator precedence table in 5.15 should be highest to lowest precedence In-Reply-To: <1440421712.73.0.607673856693.issue24921@psf.upfronthosting.co.za> Message-ID: <1440429125.8.0.953099730861.issue24921@psf.upfronthosting.co.za> Skip Montanaro added the comment: YACC might be an outlier as well. In any case, it's probably better to use other common programming languages as a gauge of what's typical. A quick check of C, C#, C++, Java, Perl, Ruby, and Haskell shows they all list operator precedence in order from highest to lowest. ---------- nosy: +skip.montanaro _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Mon Aug 24 17:23:09 2015 From: report at bugs.python.org (Stefan Krah) Date: Mon, 24 Aug 2015 15:23:09 +0000 Subject: [docs] [issue24921] Operator precedence table in 5.15 should be highest to lowest precedence In-Reply-To: <1440421712.73.0.607673856693.issue24921@psf.upfronthosting.co.za> Message-ID: <1440429789.28.0.697251081652.issue24921@psf.upfronthosting.co.za> Stefan Krah added the comment: Agreed. I'm not sure though what the reason for this convention is: The flow in Grammar/Grammar (low to high) feels quite natural to me. That said, I'm +-0 on the change. ---------- _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Mon Aug 24 18:42:46 2015 From: report at bugs.python.org (Vineet Kumar Doshi) Date: Mon, 24 Aug 2015 16:42:46 +0000 Subject: [docs] [issue24926] Incorrect Example in HTMLParser.handle_comment(data) Message-ID: <1440434566.8.0.727706131725.issue24926@psf.upfronthosting.co.za> New submission from Vineet Kumar Doshi: Hi, link : https://docs.python.org/2/library/htmlparser.html#HTMLParser.HTMLParser.handle_comment Incorrect Line : The content of Internet Explorer conditional comments (condcoms) will also be sent to this method, so, for , this method will receive '[if IE 9]>IE-specific contentIE9-specific content, this method will receive '[if IE 9]>IE9-specific content _______________________________________ From report at bugs.python.org Mon Aug 24 18:51:41 2015 From: report at bugs.python.org (Roundup Robot) Date: Mon, 24 Aug 2015 16:51:41 +0000 Subject: [docs] [issue24926] Incorrect Example in HTMLParser.handle_comment(data) In-Reply-To: <1440434566.8.0.727706131725.issue24926@psf.upfronthosting.co.za> Message-ID: <20150824165131.76209.59825@psf.io> Roundup Robot added the comment: New changeset ff53dbcdc85f by R David Murray in branch '2.7': #24926: Fix typo in example. https://hg.python.org/cpython/rev/ff53dbcdc85f ---------- nosy: +python-dev _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Mon Aug 24 18:52:38 2015 From: report at bugs.python.org (R. David Murray) Date: Mon, 24 Aug 2015 16:52:38 +0000 Subject: [docs] [issue24926] Incorrect Example in HTMLParser.handle_comment(data) In-Reply-To: <1440434566.8.0.727706131725.issue24926@psf.upfronthosting.co.za> Message-ID: <1440435158.93.0.82347534405.issue24926@psf.upfronthosting.co.za> R. David Murray added the comment: Thanks for the report. ---------- nosy: +r.david.murray resolution: -> fixed stage: -> resolved status: open -> closed _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Mon Aug 24 18:56:57 2015 From: report at bugs.python.org (Roundup Robot) Date: Mon, 24 Aug 2015 16:56:57 +0000 Subject: [docs] [issue24926] Incorrect Example in HTMLParser.handle_comment(data) In-Reply-To: <1440434566.8.0.727706131725.issue24926@psf.upfronthosting.co.za> Message-ID: <20150824165654.12145.11482@psf.io> Roundup Robot added the comment: New changeset 6eb5e59886e1 by R David Murray in branch '3.4': #24926: Fix typo in example. https://hg.python.org/cpython/rev/6eb5e59886e1 New changeset ae9a9f201870 by R David Murray in branch '3.5': Merge: #24926: Fix typo in example. https://hg.python.org/cpython/rev/ae9a9f201870 New changeset ccde4da4d0de by R David Murray in branch 'default': Merge: #24926: Fix typo in example. https://hg.python.org/cpython/rev/ccde4da4d0de ---------- _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Tue Aug 25 04:18:46 2015 From: report at bugs.python.org (Berker Peksag) Date: Tue, 25 Aug 2015 02:18:46 +0000 Subject: [docs] [issue24911] Context manager of socket.socket is not documented In-Reply-To: <1440189246.69.0.0632097129757.issue24911@psf.upfronthosting.co.za> Message-ID: <1440469126.96.0.900251975184.issue24911@psf.upfronthosting.co.za> Changes by Berker Peksag : ---------- keywords: +easy stage: -> needs patch type: -> enhancement versions: +Python 3.5, Python 3.6 _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Tue Aug 25 06:20:52 2015 From: report at bugs.python.org (Martin Panter) Date: Tue, 25 Aug 2015 04:20:52 +0000 Subject: [docs] [issue24808] PyTypeObject fields have incorrectly documented types In-Reply-To: <1438857358.96.0.0472075361686.issue24808@psf.upfronthosting.co.za> Message-ID: <1440476451.98.0.138536529473.issue24808@psf.upfronthosting.co.za> Martin Panter added the comment: Most of this looks good. For the record, tp_flags was changed to unsigned in 3.4 (Issue 16086). The const and Py_ssize_t changes were done before 3.0. The only bits I would hesitate about are adding back the two comments saying ?Assigned meaning in release 2?. These comments seem to have been removed from the Python 3 documentation in r67578, and I don?t see much point adding them back. I will have a go at committing the rest of the patch. (This is my first time making a commit.) ---------- assignee: docs at python -> martin.panter nosy: +berker.peksag, martin.panter stage: -> commit review versions: -Python 3.2, Python 3.3 _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Tue Aug 25 06:26:23 2015 From: report at bugs.python.org (Berker Peksag) Date: Tue, 25 Aug 2015 04:26:23 +0000 Subject: [docs] [issue24789] ctypes doc string In-Reply-To: <1438719738.53.0.780685651956.issue24789@psf.upfronthosting.co.za> Message-ID: <1440476783.08.0.236755907681.issue24789@psf.upfronthosting.co.za> Changes by Berker Peksag : ---------- keywords: +easy nosy: +berker.peksag stage: -> needs patch type: -> behavior _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Tue Aug 25 07:53:24 2015 From: report at bugs.python.org (Roundup Robot) Date: Tue, 25 Aug 2015 05:53:24 +0000 Subject: [docs] [issue24808] PyTypeObject fields have incorrectly documented types In-Reply-To: <1438857358.96.0.0472075361686.issue24808@psf.upfronthosting.co.za> Message-ID: <20150825055320.76207.71650@psf.io> Roundup Robot added the comment: New changeset 54a9c649281d by Martin Panter in branch '3.4': Issue #24808: Update the documentation of some PyTypeObject fields https://hg.python.org/cpython/rev/54a9c649281d New changeset e81d692a00b1 by Martin Panter in branch '3.5': Issue #24808: Merge 3.4 into 3.5; adjust new tp_as_async field https://hg.python.org/cpython/rev/e81d692a00b1 New changeset 2637e2593f01 by Martin Panter in branch 'default': Issue #24808: Merge 3.5 into 3.6 https://hg.python.org/cpython/rev/2637e2593f01 ---------- nosy: +python-dev _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Tue Aug 25 08:15:42 2015 From: report at bugs.python.org (Martin Panter) Date: Tue, 25 Aug 2015 06:15:42 +0000 Subject: [docs] [issue24808] PyTypeObject fields have incorrectly documented types In-Reply-To: <1438857358.96.0.0472075361686.issue24808@psf.upfronthosting.co.za> Message-ID: <1440483342.19.0.932197038062.issue24808@psf.upfronthosting.co.za> Martin Panter added the comment: Okay I think that worked smoothly (let me know if I missed something). Thanks for the patch Joseph. ---------- resolution: -> fixed stage: commit review -> resolved status: open -> closed _______________________________________ Python tracker _______________________________________ From vineetvivid at gmail.com Mon Aug 24 18:34:05 2015 From: vineetvivid at gmail.com (Vineet Kumar Doshi) Date: Mon, 24 Aug 2015 22:04:05 +0530 Subject: [docs] Incorrect Example in HTMLParser.handle_comment(data) Message-ID: Hi, link : https://docs.python.org/2/library/htmlparser.html#HTMLParser.HTMLParser.handle_comment Incorrect Line : The content of Internet Explorer conditional comments (condcoms) will also be sent to this method, so, for , this method will receive '[if IE 9]>IE-specific contentIE9-specific content, this method will receive '[if IE 9]>IE9-specific content From mascaro.lucas at yahoo.fr Tue Aug 25 02:59:27 2015 From: mascaro.lucas at yahoo.fr (mascaro.lucas at yahoo.fr) Date: Tue, 25 Aug 2015 02:59:27 +0200 Subject: [docs] Translation of the Python documentation Message-ID: <848996.39819.bm@smtp144.mail.ir2.yahoo.com> Hi?! Introducing myself, I?m Lucas, a French translator on the Transifex project of the documentation ( https://www.transifex.com/python-doc-ja/python-34-ja/) , and, in fact, i?m the only one on it (literally , the current coordinator have been inactive for month), so I was just wondering if the project was still on (knowing that only the Japanese part is progressing). If so, why don?t you make the project more visible for the community?? I think making the Python Doc? understandable for the most is a very good thing and a versy simple one to do for us, we only need people to make it. Thanks for your answers , i?ll continue to translate, slowly but i like to do it ^^ Have a good day?! -------------- next part -------------- An HTML attachment was scrubbed... URL: From songofacandy at gmail.com Tue Aug 25 10:12:05 2015 From: songofacandy at gmail.com (INADA Naoki) Date: Tue, 25 Aug 2015 17:12:05 +0900 Subject: [docs] Translation of the Python documentation In-Reply-To: <848996.39819.bm@smtp144.mail.ir2.yahoo.com> References: <848996.39819.bm@smtp144.mail.ir2.yahoo.com> Message-ID: Hi, Lucas. I'm the owner of the transifex project. (FYI, source is https://bitbucket.org/pydocja/cpython-ja, and the translated site is http://docs.python.jp/3/ ) We translates Python docs from more than 10 years ago. When starting translating Python 3, we start using sphinx-intl and Transifex. I've proposed to this ML to someone in PSF start official project. But no one starts. The name "python-doc-ja" means this is not official PSF project. I permitted other languages because there were strong request even I explained this is not official project. I hope there is official translation project in PSF. If PSF doesn't have manpower for the translation project, I think having official Transifex project is nice idea. Does anyone in PSF interested in it? On Tue, Aug 25, 2015 at 9:59 AM, wrote: > Hi ! > > Introducing myself, I?m Lucas, a French translator on the Transifex > project of the documentation ( > https://www.transifex.com/python-doc-ja/python-34-ja/) , and, in fact, > i?m the only one on it (literally , the current coordinator have been > inactive for month), so I was just wondering if the project was still on > (knowing that only the Japanese part is progressing). If so, why don?t you > make the project more visible for the community ? I think making the Python > Doc? understandable for the most is a very good thing and a versy simple > one to do for us, we only need people to make it. Thanks for your answers , > i?ll continue to translate, slowly but i like to do it ^^ > > Have a good day ! > > _______________________________________________ > docs mailing list > docs at python.org > https://mail.python.org/mailman/listinfo/docs > > -- INADA Naoki -------------- next part -------------- An HTML attachment was scrubbed... URL: From report at bugs.python.org Tue Aug 25 14:59:27 2015 From: report at bugs.python.org (R. David Murray) Date: Tue, 25 Aug 2015 12:59:27 +0000 Subject: [docs] [issue24808] PyTypeObject fields have incorrectly documented types In-Reply-To: <1438857358.96.0.0472075361686.issue24808@psf.upfronthosting.co.za> Message-ID: <1440507567.16.0.7618675484.issue24808@psf.upfronthosting.co.za> R. David Murray added the comment: Congratulation on your first commit, Martin :) Dropping the python2 reference was the right call: the python3 docs are supposed to be a "fresh start" and there are very few places where they mention python2. ---------- nosy: +r.david.murray _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Tue Aug 25 18:41:33 2015 From: report at bugs.python.org (Petr Viktorin) Date: Tue, 25 Aug 2015 16:41:33 +0000 Subject: [docs] [issue24937] Multiple problems in getters & setters in capsulethunk.h Message-ID: <1440520892.99.0.130273606833.issue24937@psf.upfronthosting.co.za> New submission from Petr Viktorin: In https://docs.python.org/3/howto/cporting.html#cobject-replaced-with-capsule (added in issue13053): 1) __PyCapsule_GetField is defined as:: #define __PyCapsule_GetField(capsule, field, default_value) ... but called as:: __PyCapsule_GetField(capsule, field) 2) __PyCapsule_SetField returns the wrong value (1 for success, 0 for failure). 3) Both the getter and setter don't set the exception on failure, leading to "SystemError: error return without exception set". Here's a patch. ---------- assignee: docs at python components: Documentation files: capsulethunk.patch keywords: patch messages: 249138 nosy: docs at python, encukou, larry, ncoghlan priority: normal severity: normal status: open title: Multiple problems in getters & setters in capsulethunk.h versions: Python 2.7, Python 3.2, Python 3.3, Python 3.4, Python 3.5, Python 3.6 Added file: http://bugs.python.org/file40256/capsulethunk.patch _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Tue Aug 25 18:58:50 2015 From: report at bugs.python.org (Petr Viktorin) Date: Tue, 25 Aug 2015 16:58:50 +0000 Subject: [docs] [issue24937] Multiple problems in getters & setters in capsulethunk.h In-Reply-To: <1440520892.99.0.130273606833.issue24937@psf.upfronthosting.co.za> Message-ID: <1440521930.16.0.675868444595.issue24937@psf.upfronthosting.co.za> Petr Viktorin added the comment: Note: I'm including a tested (+fixed, now) copy of capsulethunk.h in my set of Python3 C extension porting helpers, http://py3c.readthedocs.org Unfortunately the tests can't be added to CPython, because they need to run on Python 2.6 to be useful. That makes me think an external project might make a better home for this piece of code. If you agree, I can take over maintainership of capsulethunk, and make py3c the canonical home for it. ---------- _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Tue Aug 25 19:11:50 2015 From: report at bugs.python.org (Larry Hastings) Date: Tue, 25 Aug 2015 17:11:50 +0000 Subject: [docs] [issue24937] Multiple problems in getters & setters in capsulethunk.h In-Reply-To: <1440520892.99.0.130273606833.issue24937@psf.upfronthosting.co.za> Message-ID: <1440522710.71.0.979512367547.issue24937@psf.upfronthosting.co.za> Larry Hastings added the comment: Given that capsulethunk is only needed for 2.6 (and previous), and those versions are no longer maintained by the Python core community, yes I'd be happy for you to take over maintainership and host it externally. I'm sure we could change the documentation in 2.7, 3.4, and 3.5 to reflect this. ---------- _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Tue Aug 25 21:21:07 2015 From: report at bugs.python.org (Petr Viktorin) Date: Tue, 25 Aug 2015 19:21:07 +0000 Subject: [docs] [issue24937] Multiple problems in getters & setters in capsulethunk.h In-Reply-To: <1440520892.99.0.130273606833.issue24937@psf.upfronthosting.co.za> Message-ID: <1440530467.6.0.262120394809.issue24937@psf.upfronthosting.co.za> Petr Viktorin added the comment: Thanks! I'll take good care of it :) Give me a few days to prepare the docs change; this isn't very high priority. ---------- _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Wed Aug 26 00:18:18 2015 From: report at bugs.python.org (Robert Collins) Date: Tue, 25 Aug 2015 22:18:18 +0000 Subject: [docs] [issue23144] html.parser.HTMLParser: setting 'convert_charrefs = True' leads to dropped text In-Reply-To: <1420138028.63.0.996553076818.issue23144@psf.upfronthosting.co.za> Message-ID: <1440541097.99.0.535830916527.issue23144@psf.upfronthosting.co.za> Robert Collins added the comment: @ezio - you seem busy, so I'll commit this next week if its still pending. ---------- _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Wed Aug 26 02:42:15 2015 From: report at bugs.python.org (Robert Collins) Date: Wed, 26 Aug 2015 00:42:15 +0000 Subject: [docs] [issue23183] timeit CLI best of 3: undocumented output format In-Reply-To: <1420620799.47.0.00516438922368.issue23183@psf.upfronthosting.co.za> Message-ID: <1440549735.53.0.245816764123.issue23183@psf.upfronthosting.co.za> Changes by Robert Collins : ---------- stage: patch review -> commit review _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Wed Aug 26 03:40:14 2015 From: report at bugs.python.org (Martin Panter) Date: Wed, 26 Aug 2015 01:40:14 +0000 Subject: [docs] [issue24911] Context manager of socket.socket is not documented In-Reply-To: <1440189246.69.0.0632097129757.issue24911@psf.upfronthosting.co.za> Message-ID: <1440553214.33.0.0200467068002.issue24911@psf.upfronthosting.co.za> Martin Panter added the comment: IMO the change notice for create_connection() should be moved to apply to the ?socket? class, perhaps the ?Socket Objects? section. Issue 9794 looks like context manager support was added specifically for create_connection(), however any socket object, no matter what function is used to create it, should be usable the same way for free. Also, we should explicitly document that exiting the context manager (?with? statement) invokes close(), since that affects how the underlying socket is closed when makefile() has been used. ---------- nosy: +martin.panter _______________________________________ Python tracker _______________________________________ From dlwubi at gmail.com Wed Aug 26 17:36:51 2015 From: dlwubi at gmail.com (Desta Wubishet) Date: Wed, 26 Aug 2015 18:36:51 +0300 Subject: [docs] Distributing .c and .pyd modules Message-ID: Dear Sir, I got your email from the manual with the title "Distributing Python modules". After writing my modules in Python, I used Cython to convert them to .c and .pyd files. But I faced problem in creating a distribution package containing only the .c and .pyd files. Please let me know if there is any material that I can use as a reference for this purpose or I would appreciate if you can give me some hint especially in preparing the MANIFEST.in file. Best, Desta -------------- next part -------------- An HTML attachment was scrubbed... URL: From olivier.grisel at ensta.org Thu Aug 27 09:48:05 2015 From: olivier.grisel at ensta.org (Olivier Grisel) Date: Thu, 27 Aug 2015 09:48:05 +0200 Subject: [docs] [Distutils] Distributing .c and .pyd modules In-Reply-To: References: Message-ID: You can use the wheel package format to generate platform specific packages for Windows. Have a look at the python packaging documentation: https://packaging.python.org In particular: https://packaging.python.org/en/latest/distributing.html#wheels -- Olivier From i at introo.me Thu Aug 27 11:01:16 2015 From: i at introo.me (Shiyao Ma) Date: Thu, 27 Aug 2015 17:01:16 +0800 Subject: [docs] Should I fire a bug against io.IOBase.seek function sig ? Message-ID: Hi, The doc is here: https://docs.python.org/3/library/io.html#io.IOBase.seek It is said the parameter list is in the form of: seek(offset, whence=SEEK_SET) But actually only: *seek(offset) *or* seek(offset, SEEK_BAR)* is allowed. Passing *seek(offset, whence=SEEK_BAR) *will throw an error. Presumably it should be due to the difference between the argument handling of the C/Python realm, since io is a wrapper around _io. Should I fire a bug against it and modify the sig as: seek(offset, [SEEK_SET]) Or is it trivial enough to leave as it is? Regards. -- ????????????????https://introo.me ? -------------- next part -------------- An HTML attachment was scrubbed... URL: From berker.peksag at gmail.com Thu Aug 27 18:30:32 2015 From: berker.peksag at gmail.com (=?UTF-8?Q?Berker_Peksa=C4=9F?=) Date: Thu, 27 Aug 2015 19:30:32 +0300 Subject: [docs] Should I fire a bug against io.IOBase.seek function sig ? In-Reply-To: References: Message-ID: On Thu, Aug 27, 2015 at 12:01 PM, Shiyao Ma wrote: > Hi, > > The doc is here: https://docs.python.org/3/library/io.html#io.IOBase.seek > > It is said the parameter list is in the form of: > seek(offset, whence=SEEK_SET) > > > But actually only: > seek(offset) or seek(offset, SEEK_BAR) is allowed. > > Passing seek(offset, whence=SEEK_BAR) will throw an error. > > > Presumably it should be due to the difference between the argument handling > of the C/Python realm, since io is a wrapper around _io. > > Should I fire a bug against it and modify the sig as: > seek(offset, [SEEK_SET]) Yes, please open a new issue at bugs.python.org. The correct syntax should be ``seek(offset[, SEEK_SET])``. Also, we can make seek() accept a whence keyword argument on Python 3.6(similar to what we did for codecs.{encode,decode} for Python 3.5). --Berker From report at bugs.python.org Thu Aug 27 22:50:01 2015 From: report at bugs.python.org (tagatac) Date: Thu, 27 Aug 2015 20:50:01 +0000 Subject: [docs] [issue24947] asyncio-eventloop documentation grammar (minor) Message-ID: <1440708601.27.0.541488895387.issue24947@psf.upfronthosting.co.za> New submission from tagatac: "amongst which" in the Base Event Loop subsection of the docs does not really describe a list of facilities. "amongst which are" would be better, but "including" conveys the same thing more succinctly. https://docs.python.org/3/library/asyncio-eventloop.html ---------- assignee: docs at python components: Documentation files: mywork.patch keywords: patch messages: 249257 nosy: docs at python, tagatac priority: normal severity: normal status: open title: asyncio-eventloop documentation grammar (minor) Added file: http://bugs.python.org/file40277/mywork.patch _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Thu Aug 27 22:56:17 2015 From: report at bugs.python.org (Roundup Robot) Date: Thu, 27 Aug 2015 20:56:17 +0000 Subject: [docs] [issue24947] asyncio-eventloop documentation grammar (minor) In-Reply-To: <1440708601.27.0.541488895387.issue24947@psf.upfronthosting.co.za> Message-ID: <20150827205614.22338.42345@psf.io> Roundup Robot added the comment: New changeset cf15066861fc by Zachary Ware in branch '3.4': Issue #24947: Fix grammar in asyncio doc https://hg.python.org/cpython/rev/cf15066861fc New changeset 563d6f9fecfe by Zachary Ware in branch '3.5': Issue #24947: Merge 3.4 https://hg.python.org/cpython/rev/563d6f9fecfe New changeset b76346142b49 by Zachary Ware in branch 'default': Closes #24947: Merge with 3.5 https://hg.python.org/cpython/rev/b76346142b49 ---------- nosy: +python-dev resolution: -> fixed stage: -> resolved status: open -> closed _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Thu Aug 27 22:56:49 2015 From: report at bugs.python.org (Zachary Ware) Date: Thu, 27 Aug 2015 20:56:49 +0000 Subject: [docs] [issue24947] asyncio-eventloop documentation grammar (minor) In-Reply-To: <1440708601.27.0.541488895387.issue24947@psf.upfronthosting.co.za> Message-ID: <1440709009.64.0.537062266999.issue24947@psf.upfronthosting.co.za> Zachary Ware added the comment: Fixed, thanks for the report and patch! ---------- nosy: +zach.ware versions: +Python 3.4, Python 3.5, Python 3.6 _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Fri Aug 28 02:06:39 2015 From: report at bugs.python.org (Matheus Vieira Portela) Date: Fri, 28 Aug 2015 00:06:39 +0000 Subject: [docs] [issue24789] ctypes doc string In-Reply-To: <1438719738.53.0.780685651956.issue24789@psf.upfronthosting.co.za> Message-ID: <1440720399.72.0.996129614878.issue24789@psf.upfronthosting.co.za> Matheus Vieira Portela added the comment: Updated create_string_buffer docstring to "create_string_buffer(aBytes, anInteger) -> character array". ---------- keywords: +patch nosy: +matheus.v.portela Added file: http://bugs.python.org/file40279/issue24789_ctypes_doc_string.patch _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Fri Aug 28 16:59:08 2015 From: report at bugs.python.org (mattip) Date: Fri, 28 Aug 2015 14:59:08 +0000 Subject: [docs] [issue24952] stack_size([size]) is actually stack_size(size=0) Message-ID: <1440773948.16.0.0613964686365.issue24952@psf.upfronthosting.co.za> New submission from mattip: when using thread.stack_size or threading.stack_size, if no argument is provided the stack size is reset to default. Trivial patch for 3.5 provided ---------- assignee: docs at python components: Documentation files: stack_size.patch keywords: patch messages: 249280 nosy: docs at python, mattip priority: normal severity: normal status: open title: stack_size([size]) is actually stack_size(size=0) type: behavior versions: Python 3.5 Added file: http://bugs.python.org/file40281/stack_size.patch _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Fri Aug 28 17:16:03 2015 From: report at bugs.python.org (mattip) Date: Fri, 28 Aug 2015 15:16:03 +0000 Subject: [docs] [issue24952] stack_size([size]) is actually stack_size(size=0) In-Reply-To: <1440773948.16.0.0613964686365.issue24952@psf.upfronthosting.co.za> Message-ID: <1440774963.2.0.451278167668.issue24952@psf.upfronthosting.co.za> mattip added the comment: Add a patch for 2.7 ---------- versions: +Python 2.7 -Python 3.5 Added file: http://bugs.python.org/file40282/stack_size2.7.patch _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Sat Aug 29 00:21:13 2015 From: report at bugs.python.org (Martin Panter) Date: Fri, 28 Aug 2015 22:21:13 +0000 Subject: [docs] [issue24952] stack_size([size]) is actually stack_size(size=0) In-Reply-To: <1440773948.16.0.0613964686365.issue24952@psf.upfronthosting.co.za> Message-ID: <1440800473.89.0.881280986225.issue24952@psf.upfronthosting.co.za> Martin Panter added the comment: In my mind this notation implies the folowing should work: >>> threading.stack_size(size=0) Traceback (most recent call last): File "", line 1, in TypeError: stack_size() takes no keyword arguments Perhaps you really just want make it more explicit that the special value 0 is used by default if the argument omitted? See also Issue 8706 about supporting named keyword parameters, and Issue 13386 and Issue 23738 about other possible notations to document the default value. ---------- nosy: +martin.panter versions: +Python 3.4, Python 3.5, Python 3.6 _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Sat Aug 29 07:08:02 2015 From: report at bugs.python.org (Terry J. Reedy) Date: Sat, 29 Aug 2015 05:08:02 +0000 Subject: [docs] [issue24914] Python: Not just OO style but this is not mentioned on python.org or in FAQ In-Reply-To: <1440225910.92.0.539487452884.issue24914@psf.upfronthosting.co.za> Message-ID: <1440824882.89.0.67862293666.issue24914@psf.upfronthosting.co.za> Changes by Terry J. Reedy : ---------- nosy: +terry.reedy _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Sat Aug 29 07:10:37 2015 From: report at bugs.python.org (Terry J. Reedy) Date: Sat, 29 Aug 2015 05:10:37 +0000 Subject: [docs] [issue24921] Operator precedence table in 5.15 should be highest to lowest precedence In-Reply-To: <1440421712.73.0.607673856693.issue24921@psf.upfronthosting.co.za> Message-ID: <1440825037.97.0.726047753296.issue24921@psf.upfronthosting.co.za> Changes by Terry J. Reedy : ---------- nosy: +terry.reedy _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Sun Aug 30 05:18:45 2015 From: report at bugs.python.org (TAKASE Arihiro) Date: Sun, 30 Aug 2015 03:18:45 +0000 Subject: [docs] [issue24962] Unnecessary space in using/mac Message-ID: <1440904724.88.0.774285307228.issue24962@psf.upfronthosting.co.za> New submission from TAKASE Arihiro: https://docs.python.org/3.4/using/mac.html#configuration A newline in the file path of the .plist file makes a space in the rendered result. The attached patch fixes it. ---------- assignee: docs at python components: Documentation files: using_mac.patch keywords: patch messages: 249346 nosy: artakase, docs at python priority: normal severity: normal status: open title: Unnecessary space in using/mac type: behavior versions: Python 2.7, Python 3.4, Python 3.5, Python 3.6 Added file: http://bugs.python.org/file40298/using_mac.patch _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Sun Aug 30 05:27:59 2015 From: report at bugs.python.org (Roundup Robot) Date: Sun, 30 Aug 2015 03:27:59 +0000 Subject: [docs] [issue24962] Unnecessary space in using/mac In-Reply-To: <1440904724.88.0.774285307228.issue24962@psf.upfronthosting.co.za> Message-ID: <20150830032755.117772.85676@psf.io> Roundup Robot added the comment: New changeset 3ef2d694e976 by Zachary Ware in branch '2.7': Issue #24962: Remove space from filename https://hg.python.org/cpython/rev/3ef2d694e976 New changeset 2de6fba18ff6 by Zachary Ware in branch '3.4': Issue #24962: Remove space from filename https://hg.python.org/cpython/rev/2de6fba18ff6 New changeset 84c3188f6e1e by Zachary Ware in branch '3.5': Issue #24962: Merge 3.4 https://hg.python.org/cpython/rev/84c3188f6e1e New changeset 5711ffc2292f by Zachary Ware in branch 'default': Closes #24962: Merge with 3.5 https://hg.python.org/cpython/rev/5711ffc2292f ---------- nosy: +python-dev resolution: -> fixed stage: -> resolved status: open -> closed _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Sun Aug 30 05:28:48 2015 From: report at bugs.python.org (Zachary Ware) Date: Sun, 30 Aug 2015 03:28:48 +0000 Subject: [docs] [issue24962] Unnecessary space in using/mac In-Reply-To: <1440904724.88.0.774285307228.issue24962@psf.upfronthosting.co.za> Message-ID: <1440905328.38.0.499897655051.issue24962@psf.upfronthosting.co.za> Zachary Ware added the comment: Thanks for the report and patch! ---------- nosy: +zach.ware _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Sun Aug 30 05:41:07 2015 From: report at bugs.python.org (Roundup Robot) Date: Sun, 30 Aug 2015 03:41:07 +0000 Subject: [docs] [issue24272] PEP 484 docs In-Reply-To: <1432415368.91.0.945654992881.issue24272@psf.upfronthosting.co.za> Message-ID: <20150830034103.27009.6577@psf.io> Roundup Robot added the comment: New changeset 192c654a7c93 by Zachary Ware in branch '3.5': Issue #24272: Remove usage of default reST role from typing docs https://hg.python.org/cpython/rev/192c654a7c93 New changeset 10a63ded324c by Zachary Ware in branch 'default': Issue #24272: Merge with 3.5 https://hg.python.org/cpython/rev/10a63ded324c ---------- _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Sun Aug 30 18:26:25 2015 From: report at bugs.python.org (zodalahtathi) Date: Sun, 30 Aug 2015 16:26:25 +0000 Subject: [docs] [issue24963] ipaddress.IPv6Network doc typo Message-ID: <1440951985.53.0.495808420331.issue24963@psf.upfronthosting.co.za> New submission from zodalahtathi: This is probably not the biggest bug ever, but in the doc for ipaddress.IPv6Network: "An integer packed into a bytes object of length 16, bit-endian" should be changed to: "An integer packed into a bytes object of length 16, big-endian" ---------- assignee: docs at python components: Documentation messages: 249359 nosy: docs at python, zodalahtathi priority: normal severity: normal status: open title: ipaddress.IPv6Network doc typo versions: Python 3.4 _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Sun Aug 30 21:24:38 2015 From: report at bugs.python.org (mattip) Date: Sun, 30 Aug 2015 19:24:38 +0000 Subject: [docs] [issue24952] stack_size([size]) is actually stack_size(size=0) In-Reply-To: <1440773948.16.0.0613964686365.issue24952@psf.upfronthosting.co.za> Message-ID: <1440962678.01.0.903975645942.issue24952@psf.upfronthosting.co.za> mattip added the comment: Add the default value 0 to the documentation, please review this patch and not the previous one ---------- versions: -Python 3.4, Python 3.5, Python 3.6 Added file: http://bugs.python.org/file40304/stack_size.patch _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Sun Aug 30 21:30:49 2015 From: report at bugs.python.org (mattip) Date: Sun, 30 Aug 2015 19:30:49 +0000 Subject: [docs] [issue24952] stack_size([size]) is actually stack_size(size=0) In-Reply-To: <1440773948.16.0.0613964686365.issue24952@psf.upfronthosting.co.za> Message-ID: <1440963049.4.0.878069743562.issue24952@psf.upfronthosting.co.za> mattip added the comment: Add default value of 0 to documentation for 2.7 ---------- versions: +Python 3.5 -Python 2.7 Added file: http://bugs.python.org/file40305/stack_size2.7.patch _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Sun Aug 30 23:43:34 2015 From: report at bugs.python.org (Roundup Robot) Date: Sun, 30 Aug 2015 21:43:34 +0000 Subject: [docs] [issue24963] ipaddress.IPv6Network doc typo In-Reply-To: <1440951985.53.0.495808420331.issue24963@psf.upfronthosting.co.za> Message-ID: <20150830214331.117770.48596@psf.io> Roundup Robot added the comment: New changeset a892c67fa0eb by Benjamin Peterson in branch '3.4': fix spelling that was a bit confused (closes #24963) https://hg.python.org/cpython/rev/a892c67fa0eb New changeset b5434aff4e84 by Benjamin Peterson in branch '3.5': merge 3.4 (#24963) https://hg.python.org/cpython/rev/b5434aff4e84 New changeset 6463279d1358 by Benjamin Peterson in branch 'default': merge 3.5 (#24963) https://hg.python.org/cpython/rev/6463279d1358 ---------- nosy: +python-dev resolution: -> fixed stage: -> resolved status: open -> closed _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Mon Aug 31 03:18:42 2015 From: report at bugs.python.org (Martin Panter) Date: Mon, 31 Aug 2015 01:18:42 +0000 Subject: [docs] [issue24952] stack_size([size]) is actually stack_size(size=0) In-Reply-To: <1440773948.16.0.0613964686365.issue24952@psf.upfronthosting.co.za> Message-ID: <1440983922.1.0.676977196561.issue24952@psf.upfronthosting.co.za> Martin Panter added the comment: This version looks okay. I?ll commit it when I get a chance. BTW, there?s no point changing the version for each patch. The version field only applies to the whole bug report. ---------- assignee: docs at python -> martin.panter nosy: +berker.peksag stage: -> commit review versions: +Python 2.7, Python 3.4, Python 3.6 _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Mon Aug 31 05:43:52 2015 From: report at bugs.python.org (Roundup Robot) Date: Mon, 31 Aug 2015 03:43:52 +0000 Subject: [docs] [issue24952] stack_size([size]) is actually stack_size(size=0) In-Reply-To: <1440773948.16.0.0613964686365.issue24952@psf.upfronthosting.co.za> Message-ID: <20150831034348.82785.48044@psf.io> Roundup Robot added the comment: New changeset 328383905eaf by Martin Panter in branch '3.4': Issue #24952: Clarify default argument of stack_size() in threading, _thread https://hg.python.org/cpython/rev/328383905eaf New changeset 606082fa2804 by Martin Panter in branch '3.5': Issue #24952: Merge 3.4 into 3.5 https://hg.python.org/cpython/rev/606082fa2804 New changeset 501c9ab07996 by Martin Panter in branch 'default': Issue #24952: Merge 3.5 into 3.6 https://hg.python.org/cpython/rev/501c9ab07996 New changeset 79afd50396c5 by Martin Panter in branch '2.7': Issue #24952: Clarify default argument of stack_size() in threading, thread https://hg.python.org/cpython/rev/79afd50396c5 ---------- nosy: +python-dev _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Mon Aug 31 05:48:28 2015 From: report at bugs.python.org (Martin Panter) Date: Mon, 31 Aug 2015 03:48:28 +0000 Subject: [docs] [issue24952] stack_size([size]) is actually stack_size(size=0) In-Reply-To: <1440773948.16.0.0613964686365.issue24952@psf.upfronthosting.co.za> Message-ID: <1440992908.28.0.17059889707.issue24952@psf.upfronthosting.co.za> Martin Panter added the comment: Thanks for the patches ---------- resolution: -> fixed stage: commit review -> resolved status: open -> closed _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Mon Aug 31 06:14:54 2015 From: report at bugs.python.org (Martin Panter) Date: Mon, 31 Aug 2015 04:14:54 +0000 Subject: [docs] [issue24911] Context manager of socket.socket is not documented In-Reply-To: <1440189246.69.0.0632097129757.issue24911@psf.upfronthosting.co.za> Message-ID: <1440994494.78.0.360619948757.issue24911@psf.upfronthosting.co.za> Martin Panter added the comment: Here is my proposed patch ---------- keywords: +patch stage: needs patch -> patch review Added file: http://bugs.python.org/file40307/socket-context.patch _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Mon Aug 31 06:41:07 2015 From: report at bugs.python.org (Martin Panter) Date: Mon, 31 Aug 2015 04:41:07 +0000 Subject: [docs] [issue12833] raw_input misbehaves when readline is imported In-Reply-To: <1314205212.4.0.313319940132.issue12833@psf.upfronthosting.co.za> Message-ID: <1440996067.39.0.313565285445.issue12833@psf.upfronthosting.co.za> Martin Panter added the comment: I wonder if this information would be better off under the input() function, rather than under the Readline module itself. Also see Issue 17337, about control codes in the Readline prompt. Since these issues both relate to the prompt, it might be worth documenting both in the same section or paragraph. ---------- _______________________________________ Python tracker _______________________________________ From report at bugs.python.org Mon Aug 31 06:54:43 2015 From: report at bugs.python.org (Martin Panter) Date: Mon, 31 Aug 2015 04:54:43 +0000 Subject: [docs] [issue23639] Not documented special names In-Reply-To: <1426072501.09.0.6383465164.issue23639@psf.upfronthosting.co.za> Message-ID: <1440996883.69.0.897577728158.issue23639@psf.upfronthosting.co.za> Changes by Martin Panter : ---------- dependencies: +__base__ undocumented stage: needs patch -> patch review _______________________________________ Python tracker _______________________________________ From Chris.Dwyer at kbb.com Fri Aug 28 22:48:32 2015 From: Chris.Dwyer at kbb.com (Dwyer, Chris (KBB)) Date: Fri, 28 Aug 2015 20:48:32 +0000 Subject: [docs] unittest: test seem to be run out of order Message-ID: Hello, I am new to unittest, so I may have missed something in the docs. My understanding was that tests were run in the order they appear in the class. I am writing a series of tests that are related and I named the tests in the following manor: Testarea test case number test case letter (number major test area relation, letter minor test area relation) I wanted something like: California01a California01b California02a California02b California02c California03a California03b California04a California04b California04c California05a California05b California06a California06b California06c California07a California07b California08a California08b California08c However I had a typo and ended up with this: California01a California01b California02a California02b California02c California03a California03b California04a California04b California04c California05a California05b California6a California06b California06c California07a California07b California08a California08b California08c The first run seemed to run the California6a last. I corrected the typo and reran the test and everything ran in the expect order. Here is the output I capture for the failed run: Verify error message - "Requested category requires inclusion of a valid identifier" ... ok test_YMM_409_Conflict02a (__main__.Test_YMM_Core) Verify telemetry counter ...InsightTelemetryCounters.Failed_Insight_Requests ... FAIL test_YMM_409_Conflict02b (__main__.Test_YMM_Core) Verify telemetry counter ...InsightTelemetryCounters.Total_Insight_Request_Duration ... ok test_YMM_409_Conflict02c (__main__.Test_YMM_Core) Verify telemetry counter ...InsightTelemetryCounters.Total_Insight_Requests ... FAIL test_YMM_409_Conflict03a (__main__.Test_YMM_Core) Verify error code - "409" ... ok test_YMM_409_Conflict03b (__main__.Test_YMM_Core) Verify error message - "Requested category requires inclusion of a valid identifier" ... ok test_YMM_409_Conflict04a (__main__.Test_YMM_Core) Verify telemetry counter ...InsightTelemetryCounters.Failed_Insight_Requests ... FAIL test_YMM_409_Conflict04b (__main__.Test_YMM_Core) Verify telemetry counter ...InsightTelemetryCounters.Total_Insight_Request_Duration ... ok test_YMM_409_Conflict04c (__main__.Test_YMM_Core) Verify telemetry counter ...InsightTelemetryCounters.Total_Insight_Requests ... FAIL test_YMM_409_Conflict05a (__main__.Test_YMM_Core) Verify error code - "409" ... ok test_YMM_409_Conflict05b (__main__.Test_YMM_Core) Verify error message - "Requested category requires inclusion of a valid identifier" ... ok test_YMM_409_Conflict06b (__main__.Test_YMM_Core) Verify telemetry counter ...InsightTelemetryCounters.Total_Insight_Request_Duration ... FAIL test_YMM_409_Conflict06c (__main__.Test_YMM_Core) Verify telemetry counter ...InsightTelemetryCounters.Total_Insight_Requests ... ERROR test_YMM_409_Conflict07a (__main__.Test_YMM_Core) Verify error code - "409" ... ok test_YMM_409_Conflict07b (__main__.Test_YMM_Core) Verify error message - "Requested category requires inclusion of a valid identifier" ... ok test_YMM_409_Conflict08a (__main__.Test_YMM_Core) Verify telemetry counter ...InsightTelemetryCounters.Failed_Insight_Requests ... FAIL test_YMM_409_Conflict08b (__main__.Test_YMM_Core) Verify telemetry counter ...InsightTelemetryCounters.Total_Insight_Request_Duration ... ok test_YMM_409_Conflict08c (__main__.Test_YMM_Core) Verify telemetry counter ...InsightTelemetryCounters.Total_Insight_Requests ... FAIL test_YMM_409_Conflict6a (__main__.Test_YMM_Core) Verify telemetry counter ...InsightTelemetryCounters.Failed_Insight_Requests ... FAIL ====================================================================== ERROR: test_YMM_409_Conflict06c (__main__.Test_YMM_Core) Verify telemetry counter ...InsightTelemetryCounters.Total_Insight_Requests Here is the output from the run that did not get an error: test_YMM_409_Conflict01a (__main__.Test_YMM_Core) Verify error code - "409" ... ok test_YMM_409_Conflict01b (__main__.Test_YMM_Core) Verify error message - "Requested category requires inclusion of a valid identifier" ... ok test_YMM_409_Conflict02a (__main__.Test_YMM_Core) Verify telemetry counter ...InsightTelemetryCounters.Failed_Insight_Requests ... FAIL test_YMM_409_Conflict02b (__main__.Test_YMM_Core) Verify telemetry counter ...InsightTelemetryCounters.Total_Insight_Request_Duration ... ok test_YMM_409_Conflict02c (__main__.Test_YMM_Core) Verify telemetry counter ...InsightTelemetryCounters.Total_Insight_Requests ... FAIL test_YMM_409_Conflict03a (__main__.Test_YMM_Core) Verify error code - "409" ... ok test_YMM_409_Conflict03b (__main__.Test_YMM_Core) Verify error message - "Requested category requires inclusion of a valid identifier" ... ok test_YMM_409_Conflict04a (__main__.Test_YMM_Core) Verify telemetry counter ...InsightTelemetryCounters.Failed_Insight_Requests ... FAIL test_YMM_409_Conflict04b (__main__.Test_YMM_Core) Verify telemetry counter ...InsightTelemetryCounters.Total_Insight_Request_Duration ... ok test_YMM_409_Conflict04c (__main__.Test_YMM_Core) Verify telemetry counter ...InsightTelemetryCounters.Total_Insight_Requests ... FAIL test_YMM_409_Conflict05a (__main__.Test_YMM_Core) Verify error code - "409" ... ok test_YMM_409_Conflict05b (__main__.Test_YMM_Core) Verify error message - "Requested category requires inclusion of a valid identifier" ... ok test_YMM_409_Conflict06a (__main__.Test_YMM_Core) Verify telemetry counter ...InsightTelemetryCounters.Failed_Insight_Requests ... FAIL test_YMM_409_Conflict06b (__main__.Test_YMM_Core) Verify telemetry counter ...InsightTelemetryCounters.Total_Insight_Request_Duration ... ok test_YMM_409_Conflict06c (__main__.Test_YMM_Core) Verify telemetry counter ...InsightTelemetryCounters.Total_Insight_Requests ... FAIL test_YMM_409_Conflict07a (__main__.Test_YMM_Core) Verify error code - "409" ... ok test_YMM_409_Conflict07b (__main__.Test_YMM_Core) Verify error message - "Requested category requires inclusion of a valid identifier" ... ok test_YMM_409_Conflict08a (__main__.Test_YMM_Core) Verify telemetry counter ...InsightTelemetryCounters.Failed_Insight_Requests ... FAIL test_YMM_409_Conflict08b (__main__.Test_YMM_Core) Verify telemetry counter ...InsightTelemetryCounters.Total_Insight_Request_Duration ... ok test_YMM_409_Conflict08c (__main__.Test_YMM_Core) Verify telemetry counter ...InsightTelemetryCounters.Total_Insight_Requests ... FAIL Chris -------------- next part -------------- An HTML attachment was scrubbed... URL: From report at bugs.python.org Mon Aug 31 08:49:58 2015 From: report at bugs.python.org (Raymond Hettinger) Date: Mon, 31 Aug 2015 06:49:58 +0000 Subject: [docs] [issue23639] Not documented special names In-Reply-To: <1426072501.09.0.6383465164.issue23639@psf.upfronthosting.co.za> Message-ID: <1441003798.82.0.368054310699.issue23639@psf.upfronthosting.co.za> Raymond Hettinger added the comment: > I think most of these are either implementation details > or "private" names, so there is no need to document them. Also, we want to be careful to not guarantee implementation details that are subject to change. Most of these are not intended for users to base their code on. IIRC, Guido already opined on some of these (preferring to keep most of them undocumented) in some other tracker item this year. As one data point, I worked on the decimal module and defined the public API. The __decimal_context__ method is not part of the public API. ---------- nosy: +rhettinger _______________________________________ Python tracker _______________________________________