[issue36858] f-string '=' debugging output needs to be documented

[sushma]

sushma  added the comment:

Hello,

I'd like to work on this and will take a look.

--
nosy: +syadlapalli

___
Python tracker 
<https://bugs.python.org/issue36858>
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue37970] urllib.parse docstrings incomplete

[sushma]

sushma  added the comment:

hello!

I can see that we might want to add documentation for splitting netloc, but I 
don't understand why we'd have scheme and netloc, but nothing for path and 
query. What are you suggesting we add for scheme/allow_fragements? 

Thanks!

--
nosy: +syadlapalli

___
Python tracker 
<https://bugs.python.org/issue37970>
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue37970] urllib.parse docstrings incomplete

[sushma]

sushma  added the comment:

I guess what I'm wondering is this: 

urlsplit(url, scheme='', allow_fragments=True)
Parse a URL into 5 components:
:///?#
Return a 5-tuple: (scheme, netloc, path, query, fragment).
Note that we don't break the components up in smaller bits
(e.g. netloc is a single string) and we don't expand % escapes.
(END)

We don't have details regarding anything, i.e scheme, netloc, path or query or 
fragments. So I was curious about why we would have more documentation around 
netloc and scheme and nothing about path and query

Should we be adding information for all(scheme, netloc, path, query, fragment) 
of them, including extra attributes of the returned SplitResult? 

p.s - newbie trying to contribute here

--

___
Python tracker 
<https://bugs.python.org/issue37970>
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue37970] urllib.parse docstrings incomplete

[sushma]

sushma  added the comment:

got it - thanks for the detailed explanation! I'll go ahead and create a PR soon

--

___
Python tracker 
<https://bugs.python.org/issue37970>
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue39476] Not convinced with the dynamic data type assignment

[Sushma]

New submission from Sushma :

Hi 

Please find below example and the compiler error,

when i'm assigning value dynamically and when we comparing in "if" loop it is 
throwing compiler error. It should not throw error it should assign and act as 
int why it is thinking as string.
Code Snippet:
print("Hello World")

num = input("Enter number ")

print(num)

if(num%3 == 0):
num+=num
print(num)

Output in Console:
Hello World
Enter number 15
15
Traceback (most recent call last):
File "main.py", line 15, in 
   if(num%3 == 0):
TypeError: not all arguments converted during string formatting

--
messages: 360865
nosy: Sush0907
priority: normal
severity: normal
status: open
title: Not convinced with the dynamic data type assignment
type: compile error
versions: Python 3.8

___
Python tracker 
<https://bugs.python.org/issue39476>
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue39476] Not convinced with the dynamic data type assignment

[Sushma]

Sushma  added the comment:

Thank you

On Tue, Jan 28, 2020, 6:30 PM Steven D'Aprano 
wrote:

>
> Steven D'Aprano  added the comment:
>
> The "num" variable is not a number, it *is* a string. Just because you
> call it "num" doesn't magically turn it into a number. The `input` function
> returns a string.
>
> You might be thinking of Python 2.7 where `input` automatically evaluated
> the string as Python code. Python 3 does not do that. If you want to
> convert the string result of `input` to be a float or an int or some other
> type, you need to call the `float` or `int` functions.
>
> --
> nosy: +steven.daprano
> resolution:  -> not a bug
> stage:  -> resolved
> status: open -> closed
>
> ___
> Python tracker 
> <https://bugs.python.org/issue39476>
> ___
>

--

___
Python tracker 
<https://bugs.python.org/issue39476>
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue30754] textwrap.dedent mishandles empty lines

[sushma]

sushma  added the comment:

I'm going to try and contribute this documentation fix.

--
nosy: +syadlapalli

___
Python tracker 
<https://bugs.python.org/issue30754>
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue30754] textwrap.dedent mishandles empty lines

[sushma]

Change by sushma :


--
keywords: +patch
pull_requests: +14286
stage:  -> patch review
pull_request: https://github.com/python/cpython/pull/14469

___
Python tracker 
<https://bugs.python.org/issue30754>
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

[issue16970] argparse: bad nargs value raises misleading message

[sushma]

sushma  added the comment:

Hello!

I added the patch and submitted the PR and ran the test, could you please take 
a look?

Also, I see this 3.6

Thanks

--
message_count: 8.0 -> 9.0
nosy: +syadlapalli
nosy_count: 4.0 -> 5.0
pull_requests: +14635
stage: needs patch -> patch review
versions: +Python 3.6 -Python 2.7, Python 3.2, Python 3.3, Python 3.4
pull_request: https://github.com/python/cpython/pull/14844

___
Python tracker 
<https://bugs.python.org/issue16970>
___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com