[issue44194] Folding ''.join() into f-strings

Serhiy Storchaka added the comment: I only seen this idiom in the code of Argument Clinic (written by Larry). I am sure that it is used in third-party code, but I do not know how common is it. As for the proposed code, checking that the value is a string is not enough. 1. It can be a str

[issue44194] Folding ''.join() into f-strings

Raymond Hettinger added the comment: I'm also dubious that this would be of value in real code. Looking at the implementation, it seems to throw way too much code at too small of a problem. I suspect is is more likely to cause maintenance problems than to produce noticeable benefits for

[issue44194] Folding ''.join() into f-strings

Eric V. Smith added the comment: > It is a pretty-targeted optimization, so I don't expect it to speed up the > macro benchmarks. Though that shouldn't be a blocker for small, targeted > optimizations. In the past we've rejected optimizations that make the code more complex and don't

[issue44194] Folding ''.join() into f-strings

Batuhan Taskaya added the comment: > We should check on a real-world benchmark instead of a micro benchmark. It is a pretty-targeted optimization, so I don't expect it to speed up the macro benchmarks. Though that shouldn't be a blocker for small, targeted optimizations. --

[issue28937] str.split(): allow removing empty strings (when sep is not None)

Matthew Barnett added the comment: I've only just realised that the test cases don't cover all eventualities: none of them test what happens with multiple spaces _between_ the letters, such as: ' a b c '.split(maxsplit=1) == ['a', 'b c '] Comparing that with: ' a b c '.split('

[issue44194] Folding ''.join() into f-strings

Eric V. Smith added the comment: To be pedantic, f-strings don't "cast" to a string, they call format(obj) on the argument. Typically this is the same as str(obj), but it need not be. I guess if all of the arguments are already exact strings then this distinction doesn't matte

[issue44194] Folding ''.join() into f-strings

New submission from Batuhan Taskaya : Since strings are immutable types, we could fold some operation on top of them. Serhiy has done some work on issue 28307 regarding folding `str % args` combination, which I think we can extend even further. One simple example that I daily encounter

[issue28937] str.split(): allow removing empty strings (when sep is not None)

Mark Bell added the comment: Thank you very much for confirming these test cases. Using these I believe that I have now been able to complete a patch that would implement this feature. The PR is available at https://github.com/python/cpython/pull/26222. As I am a first-time contributor,

[issue28937] str.split(): allow removing empty strings (when sep is not None)

Change by Mark Bell : -- pull_requests: +24839 pull_request: https://github.com/python/cpython/pull/26222 ___ Python tracker ___

[issue28937] str.split(): allow removing empty strings (when sep is not None)

Matthew Barnett added the comment: We have that already, although it's spelled: ' x y z'.split(maxsplit=1) == ['x', 'y z'] because the keepempty option doesn't exist yet. -- ___ Python tracker

[issue28937] str.split(): allow removing empty strings (when sep is not None)

Mark Bell added the comment: So I think I agree with you about the difference between .split() and .split(' '). However wouldn't that mean that ' x y z'.split(maxsplit=1, keepempty=False) == ['x', 'y z'] since it should do one split. -- ___

[issue28937] str.split(): allow removing empty strings (when sep is not None)

Matthew Barnett added the comment: The best way to think of it is that .split() is like .split(' '), except that it's splitting on any whitespace character instead of just ' ', and keepempty is defaulting to False instead of True. Therefore: ' x y z'.split(maxsplit=1, keepempty=True)

[issue28937] str.split(): allow removing empty strings (when sep is not None)

Mark Bell added the comment: > suggests that empty strings don't count towards maxsplit Thank you for the confirmation. Although just to clarify I guess you really mean "empty strings *that are dropped from the output* don't count towards maxsplit". Just to double check thi

[issue28937] str.split(): allow removing empty strings (when sep is not None)

Matthew Barnett added the comment: The case: ' a b c '.split(maxsplit=1) == ['a', 'b c '] suggests that empty strings don't count towards maxsplit, otherwise it would return [' a b c '] (i.e. the split would give ['', ' a b c '] and dropping the empty strings would give [' a b c

[issue28937] str.split(): allow removing empty strings (when sep is not None)

st two empty strings items are "free" and don't count towards the maxsplit. I think the length of the result returned must be <= maxsplit + 1, is this right? I'm about to rework the logic to avoid this, but before I go too far could someone double check my test cases to make sure that

[issue28937] str.split(): allow removing empty strings (when sep is not None)

Catherine Devlin added the comment: @ZackerySpytz - I made https://github.com/python/cpython/pull/26196 with a test for the desired behavior; hopefully it helps. I could try to adapt Barry's old patch myself, but it's probably better if somebody C-competent does so... --

[issue28937] str.split(): allow removing empty strings (when sep is not None)

Change by Catherine Devlin : -- nosy: +Catherine.Devlin nosy_count: 11.0 -> 12.0 pull_requests: +24813 stage: test needed -> patch review pull_request: https://github.com/python/cpython/pull/26196 ___ Python tracker

[issue38693] Use f-strings instead of str.format within importlib

Change by Serhiy Storchaka : -- versions: +Python 3.11 -Python 3.10 ___ Python tracker ___ ___ Python-bugs-list mailing list

[issue38693] Use f-strings instead of str.format within importlib

Serhiy Storchaka added the comment: I just have merged a change which makes many C-style formatting as fast as f-strings (issue28307) and am working on supporting more format codes (%d, %x, %f, etc). Using C-style formatting can be a good option if you want performance and backward

[issue38693] Use f-strings instead of str.format within importlib

Filipe Laíns added the comment: Both importlib_metadata and importlib_resources have dropped support for Python 2.7 and 3.5, this should now be unblocked. -- nosy: +FFY00 ___ Python tracker

[issue41692] Deprecate immortal interned strings: PyUnicode_InternImmortal()

Inada Naoki added the comment: For the record, I noticed PyUnicode_InternImmortal() is a stable ABI. We may need to keep the function to avoid dynamic link errors. But we can still change its implementation to just raise an exception. -- ___

[issue41411] Improve and consolidate f-strings docs

Raymond Hettinger added the comment: Eric, do you want to approve and apply these PRs ? -- assignee: docs@python -> eric.smith nosy: +rhettinger ___ Python tracker ___

[issue41411] Improve and consolidate f-strings docs

Stéphane Blondon added the comment: It seems ezio-melotti hesitates to continue the modifications in the PR https://github.com/python/cpython/pull/21552#pullrequestreview-458400056 IMO, the PR improves enough the documentation, so it would be nice to merge it, even without the other

[issue25817] modsupport: 'countformat' does not handle strings without bracket levels correctly

Change by Irit Katriel : -- resolution: -> not a bug stage: -> resolved status: open -> closed ___ Python tracker ___ ___

Re: Comparing text strings

sioning takes many > forms.  As suggested elsewhere, for Linux distribution packages, the > only reliable approach is to lean on the distro's packaging > infrastructure in some way, because those version strings (plus package > metadata which may have "replaces" or "obsoletes&

Re: Comparing text strings

On Sun, 18 Apr 2021 06:38:16 GMT, Gilmeh Serda wrote: > On Mon, 12 Apr 2021 16:11:21 -0700, Rich Shepard wrote: > >> All suggestions welcome. > > Assuming you want to know which is the oldest version and that the same > scheme is used all the time, could this work? >

Re: Comparing text strings

On Tue, 13 Apr 2021, jak wrote: If I understand your problem correctly, the problem would be dealing with numbers as such in file names. This is just a track but it might help you. This example splits filenames into strings and numbers into tuples, appends the tuple into a list, and then sorts

Re: Comparing text strings

is the same the version or build numbers differ. All suggestions welcome. Rich If I understand your problem correctly, the problem would be dealing with numbers as such in file names. This is just a track but it might help you. This example splits filenames into strings and numbers into tuples

Re: Comparing text strings

On 2021-04-12, 2qdxy4rzwzuui...@potatochowder.com <2qdxy4rzwzuui...@potatochowder.com> wrote: > I don't know whether or how Slackware handles "compound" package names > (e.g., python-flask), but at some point, you're going to have to pull > apart (aka---gasp--parse), the package names to come up

Re: Comparing text strings

strings (plus package metadata which may have "replaces" or "obsoletes" or some similar information) all have a defined meaning to *it* - it's the intended audience. Don't know if Slack exposes this information in some way, it may be hard to make a reliable script if not. I know

Re: Comparing text strings

On Tue, 13 Apr 2021, Cameron Simpson wrote: The problem is not that simple. Sometimes the package maintainer upgrades the package for the same version number so there could be abc-1.0_1_SBo.tgz and abc-1.0_2_SBo.tgz. The more involved route will be taken. If that _1, _2 thing is like RedHat's

Re: Comparing text strings

On 12Apr2021 19:11, Rich Shepard wrote: >On Tue, 13 Apr 2021, Cameron Simpson wrote: >>Alternatively, and now that I think about it, more simply: _if_ the >>package files can be sorted by version, then all you need to do is read a >>sorted listing and note that latest fil for a particular

Re: Comparing text strings

On Tue, 13 Apr 2021, Cameron Simpson wrote: I do not know if there are preexisting modules/tools for this, but I recommend looking at slackware's package management tool - they usually have some kind of 'clean" operation to purge "old" package install files. Sometimes that purges all the

Re: Comparing text strings

On Tue, Apr 13, 2021 at 9:54 AM Cameron Simpson wrote: > Note that this depends on sorting by version. A lexical sort (eg > "ls|sort") will look good intil a package version crosses a boundary > like this: > > 1.9.1 > 1.10.0 > > A lexical sort will put those the other way around because

Re: Comparing text strings

On 12Apr2021 16:11, Rich Shepard wrote: >I'm running Slackware64-14.2 and keep a list of installed packages. When a >package is upgraded I want to remove the earlier version, and I've not >before written a script like this. Could there be a module or tool that >already exists to do this? If not,

Re: Comparing text strings

On 2021-04-12 at 16:11:21 -0700, Rich Shepard wrote: > I'm running Slackware64-14.2 and keep a list of installed packages. When a > package is upgraded I want to remove the earlier version, and I've not > before written a script like this. Could there be a module or tool that > already exists to

Comparing text strings

I'm running Slackware64-14.2 and keep a list of installed packages. When a package is upgraded I want to remove the earlier version, and I've not before written a script like this. Could there be a module or tool that already exists to do this? If not, which string function would be best suited

Re: how to separate the strings in a string

c"', ' def'] The initial string looks like it's close enough to the CSV format. Unfortunately Python's csv module operates on files, not strings -- to use it you have to wrap the string into a stream: import csv import io next(csv.reader(io.StringIO('"ab,c" , def'))) ['ab,c ',

Re: how to separate the strings in a string

ing looks like it's close enough to the CSV format. Unfortunately Python's csv module operates on files, not strings -- to use it you have to wrap the string into a stream: >>> import csv >>> import io >>> next(csv.reader(io.StringIO('"ab,c" , def'))) ['ab,c ', ' def']

how to separate the strings in a string

I have a string like '"ab,c" , def' and need to separate it into "ab,c" and "def". split separates at the first ',': >>> bl '"a,bc", def' >>> bl.split(',') ['"a', 'bc"', ' def'] Egon signature.asc Description: OpenPGP digital signature --

[issue43695] Improve `=` in f-strings

(together with string representation of subexpressions). The same evaluator with different hook could be used for "="-substitutions in f-strings. So {a+b-c=} could be evaluated to "a=20, b=40, a+b=60, c=10, a+b-c=50". But it is too

[issue43695] Improve `=` in f-strings

Eric V. Smith added the comment: I'm going to close this. I agree with Serhiy that it's pushing f-strings too far. If you really want to pursue this, you'll need to specify the semantics much more clearly, and then bring it up on the python-ideas mailing list. But I don't want to give you

[issue43695] Improve `=` in f-strings

Serhiy Storchaka added the comment: I think it goes too far. It was initially designed as a simple for implementation and use feature which covers a large amount of use cases of using f-strings for debugging. You propose to add syntactically a new postfix operator which is valid only

[issue43695] Improve `=` in f-strings

Eric V. Smith added the comment: I don't see how this would be possible in general. What would you do with a function call that has side effects? f'{a()+b+c=}' ? You'd end up calling a() twice, or inventing your own expression evaluator. -- nosy: +eric.smith

[issue43695] Improve `=` in f-strings

wyz23x2 added the comment: Well, it's: >>> f'{a+b-c=?}' # Suffix `=` to apply to all? 20+40-10=50 P.S. When will the bug tracker enable message editing? -- ___ Python tracker

[issue43695] Improve `=` in f-strings

New submission from wyz23x2 : In Python 3.8, `=` was added into f-strings: >>> a, b, c = 20, 40, 10 >>> f'{a+b-c=}' a+b-c=50 But if `20+40-10` is wanted, this needs to be written: >>> f'{a}+{b}-{c}={a+b-c}' 20+40-10=50 So something could be added. For example, `?` (th

[issue43535] Make str.join auto-convert inputs to strings.

Change by Raymond Hettinger : -- stage: -> resolved status: open -> closed ___ Python tracker ___ ___ Python-bugs-list mailing

[issue43535] Make str.join auto-convert inputs to strings.

(sep=None, strtype=str, *strings) but that interface looks pretty bad... I think joinstr/joinbytes according to Grégory's suggestion (perhaps as classmethods of str/bytes?) would make the most sense. -- nosy: +ajoino ___ Python tracker <ht

[issue43535] Make str.join auto-convert inputs to strings.

Christian Heimes added the comment: I'm also -1 and would prefer something like Grégory's proposal instead. -- nosy: +christian.heimes ___ Python tracker ___

[issue43535] Make str.join auto-convert inputs to strings.

Grégory Starck added the comment: FWIW -1 from me too. That should be solved by creating a new function IMO : def joinstr(sep, *seq): return sep.join(str(i) for i in seq) -- nosy: +g.sta...@gmail.com ___ Python tracker

[issue43535] Make str.join auto-convert inputs to strings.

Change by Kamil Turek : -- nosy: +kamilturek ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue43535] Make str.join auto-convert inputs to strings.

Vedran Čačić added the comment: Yes, I know what strong typing means, and can you please read again what I've written? It was exactly about "In the face of ambiguity, refuse the temptation to guess.", because binary operators are inherently ambiguous when given differently typed operands.

[issue37871] Windows: WindowsConsoleIO produces mojibake for strings longer than 32 KiB

Eryk Sun added the comment: > side note: do we need to care about Windows 7 anymore in > 3.10 given that microsoft no longer supports it? If the fix comes in time for Python 3.8, then it needs to support Windows 7. For Python 3.9+, the 32 KiB limit can be removed. The console

[issue43535] Make str.join auto-convert inputs to strings.

Gregory P. Smith added the comment: There is a lot of doubt. That should clearly raise an exception because this function is intended to only operate on strings. Trivial types examples like that gloss over the actual problem. data_from_some_computations = [b"foo", b"ba

[issue37871] Windows: WindowsConsoleIO produces mojibake for strings longer than 32 KiB

Gregory P. Smith added the comment: Steve's approach makes sense and should be robust. side note: do we need to care about Windows 7 anymore in 3.10 given that microsoft no longer supports it? -- nosy: +gregory.p.smith ___ Python tracker

[issue43535] Make str.join auto-convert inputs to strings.

ot;. That's why it's possible to coerce. About the example with a list with mixed types: If the reason that example is buggy is "this list should only have strings", a better way to enforce that is to add types to enforces it. -- ___ P

[issue43535] Make str.join auto-convert inputs to strings.

Gregory P. Smith added the comment: -10. I agree with Serhiy. Automatic type conversion is rarely a feature. It leads to silent bugs when people pass the wrong things. Be explicit. We are intentionally not one of those everything is really a string languages like Perl or Javascript.

[issue43535] Make str.join auto-convert inputs to strings.

Terry J. Reedy added the comment: I read all the responses as of this timestamp. They left me more persuaded that joining objects with a string (or bytes) is explicit enough that the objects *must* be coerced to strings. A problem with coercion in "1 + '2'" is that there i

[issue43535] Make str.join auto-convert inputs to strings.

that this proposal will clearly benefit. I’m sure there will be some “None”-strings that will slip through this, but I think the upside far outweighs the downside in this case. Big +1 from me. -- nosy: +EmilStenstrom ___ Python tracker <https://bugs.python.

[issue43535] Make str.join auto-convert inputs to strings.

Raymond Hettinger added the comment: FWIW, I'm running a user poll on Twitter and have asked people to state their rationale: https://twitter.com/raymondh/status/1373315362062626823 Take it with a grain of salt. Polls totals don't reflect how much thought each person put into their

[issue43535] Make str.join auto-convert inputs to strings.

Change by jack1142 : -- nosy: +jack1142 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue43535] Make str.join auto-convert inputs to strings.

Raymond Hettinger added the comment: > Of 721 uses of the join() method (excluding os.path.join()) > in the stdlib, only 10 need forceful stringification with > map(str, ...) Thanks for looking a real world code. I'm surprised that the standard library stats aren't representative of my

[issue43535] Make str.join auto-convert inputs to strings.

Change by Batuhan Taskaya : -- nosy: +BTaskaya ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue37871] Windows: WindowsConsoleIO produces mojibake for strings longer than 32 KiB

Change by STINNER Victor : -- nosy: -vstinner ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue43535] Make str.join auto-convert inputs to strings.

Serhiy Storchaka added the comment: Vedran, it is not what strong typing means. Strong typing means that '2'+3 is an error instead of '23' or 5. str.join() expects an iterable of strings. If some of items is not a string, it is a sign of programming error. I prefer to get an exception

[issue37871] Windows: WindowsConsoleIO produces mojibake for strings longer than 32 KiB

Change by Eryk Sun : -- stage: -> needs patch versions: +Python 3.10, Python 3.8, Python 3.9 -Python 3.7 ___ Python tracker ___

[issue43535] Make str.join auto-convert inputs to strings.

Vedran Čačić added the comment: Matthew: can you then answer the same question I asked Serhiy? The example usually given when advocating strong typing is whether 2 + '3' should be '23' or 5. Our uneasiness with it doesn't stem from coercions between int and str, but from the fact that + has

[issue43535] Make str.join auto-convert inputs to strings.

Terry J. Reedy added the comment: I am sympathetic to the 'hiding bugs' argument in general, but what bugs would this proposal hide? What bugs does print hide by auto-converting non-strings to strings? I recently had the same thought as Raymond's: "it would be nice if str.join conv

[issue43535] Make str.join auto-convert inputs to strings.

Matthew Barnett added the comment: I'm also -1, for the same reason as Serhiy gave. However, if it was opt-in, then I'd be OK with it. -- nosy: +mrabarnett ___ Python tracker

[issue43535] Make str.join auto-convert inputs to strings.

Raymond Hettinger added the comment: > What changed? It comes up almost every week that I teach a Python course. Eventually, I've come to see the light :-) Also, I worked though the steps and found an efficiency gain for new code with no detriment to existing code. Lastly, I used to

[issue43535] Make str.join auto-convert inputs to strings.

Vedran Čačić added the comment: Does strong typing mean you should write if bool(condition): ... or for element in iter(sequence): ... or (more similar to this) my_set.symmetric_difference_update(set(some_iterable)) ? As Eric has said, if there's only one possible thing you

[issue43535] Make str.join auto-convert inputs to strings.

Serhiy Storchaka added the comment: It was proposed by newbies several times before. It was rejected because it would make errors to hide unnoticed. Python is dynamically but strongly typed, and it is its advantage. I am -1. -- nosy: +serhiy.storchaka

[issue43535] Make str.join auto-convert inputs to strings.

Eric V. Smith added the comment: I'm +0.5. Every time this bites me, I apply the same solution, so you're probably right that str.join should just do the work itself. And it's no doubt more performant that way, anyway. And I've probably got some code that's just waiting for the current

[issue43535] Make str.join auto-convert inputs to strings.

Vedran Čačić added the comment: I can't find it now, but I seem to remember me having this same proposal (except the part for bytes) quite a few years ago, and you being the most vocal opponent. What changed? Of course, I'm still for it. (Your second list has fourth item extra. But it's

[issue43535] Make str.join auto-convert inputs to strings.

Change by Karthikeyan Singaravelan : -- nosy: +xtreak ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue43535] Make str.join auto-convert inputs to strings.

New submission from Raymond Hettinger : Rather than just erroring-out, it would be nice if str.join converted inputs to strings when needed. Currently: data = [10, 20, 30, 40, 50] s = ', '.join(map(str, data)) Proposed: s = ', '.join(data) That would simplify a common idiom

[issue23835] configparser does not convert defaults to strings

Change by STINNER Victor : -- pull_requests: -23600 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue23835] configparser does not convert defaults to strings

Change by junyixie : -- nosy: +JunyiXie nosy_count: 7.0 -> 8.0 pull_requests: +23600 pull_request: https://github.com/python/cpython/pull/24821 ___ Python tracker ___

[issue30435] Documentation either unclear or incorrect on comparisons between bytes and strings in Python 3

Change by Eryk Sun : -- type: behavior -> enhancement versions: +Python 3.10, Python 3.8, Python 3.9 -Python 3.5, Python 3.6, Python 3.7 ___ Python tracker ___

[issue6114] distutils build_ext path comparison only based on strings

Steve Dower added the comment: Distutils is now deprecated (see PEP 632) and all tagged issues are being closed. From now until removal, only release blocking issues will be considered for distutils. If this issue does not relate to distutils, please remove the component and reopen it. If

[issue35212] Expressions with format specifiers in f-strings give wrong code position in AST

Change by daniel hahler : -- nosy: +blueyed ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue28937] str.split(): allow removing empty strings (when sep is not None)

Change by Dong-hee Na : -- nosy: +corona10 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue28937] str.split(): allow removing empty strings (when sep is not None)

Guido van Rossum added the comment: Excellent! -- ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue28937] str.split(): allow removing empty strings (when sep is not None)

Zackery Spytz added the comment: I am working on this issue. -- assignee: -> ZackerySpytz nosy: +ZackerySpytz versions: +Python 3.10 -Python 3.8 ___ Python tracker ___

[issue28937] str.split(): allow removing empty strings (when sep is not None)

Change by Raymond Hettinger : -- nosy: -rhettinger ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue28937] str.split(): allow removing empty strings (when sep is not None)

Guido van Rossum added the comment: This issue probably needs a new champion. There is broad agreement but some bike shedding, so a PEP isn’t needed.-- --Guido (mobile) -- ___ Python tracker

[issue28937] str.split(): allow removing empty strings (when sep is not None)

Change by karl : -- nosy: +karlcow ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue41224] Document is_annotate() in symtable and update doc strings

Change by Serhiy Storchaka : -- resolution: -> fixed stage: patch review -> resolved status: open -> closed versions: +Python 3.7 ___ Python tracker ___

[issue41224] Document is_annotate() in symtable and update doc strings

Serhiy Storchaka added the comment: New changeset bc15cdbc6eb112cb72acf189769ecd539dd45652 by Andre Delfino in branch '3.8': [3.8] bpo-41224: Add versionadded for Symbol.is_annotated (GH-23861). (GH-24016) https://github.com/python/cpython/commit/bc15cdbc6eb112cb72acf189769ecd539dd45652

[issue41224] Document is_annotate() in symtable and update doc strings

Serhiy Storchaka added the comment: New changeset 7a7f3e0d6a197c81fff83ad777c74324ceb4198f by Andre Delfino in branch '3.9': [3.9] bpo-41224: Add versionadded for Symbol.is_annotated (GH-23861). (GH-24017) https://github.com/python/cpython/commit/7a7f3e0d6a197c81fff83ad777c74324ceb4198f

[issue41224] Document is_annotate() in symtable and update doc strings

Change by Andrés Delfino : -- pull_requests: +22857 pull_request: https://github.com/python/cpython/pull/24017 ___ Python tracker ___

[issue41224] Document is_annotate() in symtable and update doc strings

Change by Andrés Delfino : -- pull_requests: +22856 stage: needs patch -> patch review pull_request: https://github.com/python/cpython/pull/24016 ___ Python tracker ___

[issue41224] Document is_annotate() in symtable and update doc strings

Serhiy Storchaka added the comment: The method was added in 3.6. Please backport documentation changes to 3.9 and 3.8. -- stage: resolved -> needs patch status: closed -> open versions: +Python 3.8, Python 3.9 -Python 3.10 ___ Python tracker

[issue41224] Document is_annotate() in symtable and update doc strings

Serhiy Storchaka added the comment: New changeset 2edfc86f69d8a74f4821974678f664ff94a9dc22 by Andre Delfino in branch 'master': bpo-41224: Add versionadded for Symbol.is_annotated (GH-23861) https://github.com/python/cpython/commit/2edfc86f69d8a74f4821974678f664ff94a9dc22 -- nosy:

[issue41224] Document is_annotate() in symtable and update doc strings

Change by Andrés Delfino : -- nosy: +adelfino nosy_count: 2.0 -> 3.0 pull_requests: +22838 pull_request: https://github.com/python/cpython/pull/23861 ___ Python tracker ___

[issue42607] raw strings SyntaxError

Eric V. Smith added the comment: This is a FAQ: https://docs.python.org/3/faq/design.html#why-can-t-raw-strings-r-strings-end-with-a-backslash Raw strings can't end with an odd number of backslashes. -- components: -Windows nosy: +eric.smith resolution: -> not a bug st

[issue42607] raw strings SyntaxError

85 nosy: anmikf, paul.moore, steve.dower, tim.golden, zach.ware priority: normal severity: normal status: open title: raw strings SyntaxError type: behavior versions: Python 3.8, Python 3.9 ___ Python trac

[issue28002] ast.unparse can't roundtrip some f-strings

Change by Eric V. Smith : -- resolution: not a bug -> fixed ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue28002] ast.unparse can't roundtrip some f-strings

Batuhan Taskaya added the comment: Thanks for your efforts Shantanu! -- ___ Python tracker ___ ___ Python-bugs-list mailing list

[issue28002] ast.unparse can't roundtrip some f-strings

Change by Batuhan Taskaya : -- resolution: -> not a bug stage: patch review -> resolved status: open -> closed ___ Python tracker ___

<    1   2   3   4   5   6   7   8   9   10   >