Lysandros Nikolaou added the comment:
Mariatta noted at
https://mail.python.org/archives/list/core-mentors...@python.org/message/KFIGNAGJKWQXCXG72VGIGGA3OCKUHOFC/
that these issues are not reserved and are now available for first-time
contributors.
--
nosy: +lys.nikolaou
Lysandros Nikolaou added the comment:
Pinging for review.
--
___
Python tracker
<https://bugs.python.org/issue36182>
___
___
Python-bugs-list mailing list
Unsub
Lysandros Nikolaou added the comment:
Yeah, I am not currently working on this, so feel free to make a PR anytime you
want.
--
___
Python tracker
<https://bugs.python.org/issue35
Lysandros Nikolaou added the comment:
Noah, are you working on this?
--
nosy: +lys.nikolaou
___
Python tracker
<https://bugs.python.org/issue21314>
___
___
Pytho
Change by Lysandros Nikolaou :
--
keywords: +patch
pull_requests: +9891
stage: needs patch -> patch review
___
Python tracker
<https://bugs.python.org/issu
Change by Lysandros Nikolaou :
--
keywords: +patch, patch
pull_requests: +9891, 9892
stage: needs patch -> patch review
___
Python tracker
<https://bugs.python.org/issu
Change by Lysandros Nikolaou :
--
keywords: +patch, patch, patch
pull_requests: +9891, 9892, 9893
stage: needs patch -> patch review
___
Python tracker
<https://bugs.python.org/issu
Lysandros Nikolaou added the comment:
Ping.
--
___
Python tracker
<https://bugs.python.org/issue30410>
___
___
Python-bugs-list mailing list
Unsubscribe:
Lysandros Nikolaou added the comment:
I updated the PR with the new wording by Paul, since I found it easier to
understand as well.
--
___
Python tracker
<https://bugs.python.org/issue30
Lysandros Nikolaou added the comment:
Ping.
--
___
Python tracker
<https://bugs.python.org/issue22021>
___
___
Python-bugs-list mailing list
Unsubscribe:
Change by Lysandros Nikolaou :
--
nosy: +lys.nikolaou
___
Python tracker
<https://bugs.python.org/issue35398>
___
___
Python-bugs-list mailing list
Unsubscribe:
Lysandros Nikolaou added the comment:
This issue still stands. The output of all three methods is exactly the same as
it was when the original question was posted. Would it maybe make sense to add
a flag to the unquote_to_bytes method to parse the 'plus' symbol as a space? Or
mayb
Lysandros Nikolaou added the comment:
Pinging once more for review.
--
___
Python tracker
<https://bugs.python.org/issue22021>
___
___
Python-bugs-list mailin
Lysandros Nikolaou added the comment:
Ping for review.
--
___
Python tracker
<https://bugs.python.org/issue21314>
___
___
Python-bugs-list mailing list
Unsub
Lysandros Nikolaou added the comment:
Not that it makes a big difference, but write_text is a method of the Path
class, not PurePath.
--
nosy: +lys.nikolaou
___
Python tracker
<https://bugs.python.org/issue36
New submission from Lysandros Nikolaou :
Hi,
in the pathlib.Path.write_bytes() documentation it is clearly stated that "An
existing file of the same name is overwritten." Wouldn't it make sense to
include something similar to the pathlib.Path.write_text() docs. I had to
Lysandros Nikolaou added the comment:
For reference,
https://docs.python.org/3/library/pathlib.html#pathlib.Path.write_bytes.
--
___
Python tracker
<https://bugs.python.org/issue36
Lysandros Nikolaou added the comment:
I'll submit a PR shortly.
--
___
Python tracker
<https://bugs.python.org/issue36182>
___
___
Python-bugs-list m
Change by Lysandros Nikolaou :
--
keywords: +patch
pull_requests: +12159
stage: -> patch review
___
Python tracker
<https://bugs.python.org/issue36182>
___
_
Lysandros Nikolaou added the comment:
Can confirm for 3.7.2 on my macOS 10.14 system. Although this is the case in
3.7 on my current build of the master branch I get the following AssertionError
instead:
Assertion failed: (v->ob_type == w->ob_type), function unsafe_tuple_compare,
Lysandros Nikolaou added the comment:
I agree with Nick, that pydoc should somehow be updated to mark positional-only
parameters as such. I believe that the third approach proposed by Nick is the
most sensible one, as it makes the life of new developers easier by explicitly
listing all the
Lysandros Nikolaou added the comment:
Will you make a PR or shall I try to fix this?
--
nosy: +lys.nikolaou
___
Python tracker
<https://bugs.python.org/issue34
Lysandros Nikolaou added the comment:
Upon checking to see where the RuntimeError is coming from, I noticed that
there is some notorious behaviour in chunk.py. If one runs python with the
exact same parameters as Jussi Judin did in their first case and after stepping
through the call stack
New submission from Lysandros Nikolaou :
On my Mac OS X 10.13.6 system test_socket.test_host_resolution_bad_address
fails with the following error:
==
FAIL: test_host_resolution_bad_address
Lysandros Nikolaou added the comment:
Is this expected behaviour, should the tests be changes, or is it a bug?
--
___
Python tracker
<https://bugs.python.org/issue34
Lysandros Nikolaou added the comment:
When running the terminal command host '0.1.1.~1' I get the following output:
0.1.1.~1 has address 62.138.239.45
0.1.1.~1 has address 62.138.238.45
Host 0.1.1.~1 not found: 3(NXDOMAIN)
Host 0.1.1.~1 not found: 3(NXDOMAIN)
If I ping the above
New submission from Lysandros Nikolaou :
In the Doc README there is the following sentence after the make venv command:
Assuming the virtual environment was created in the env directory (the default;
configurable with the VENVDIR variable)
Should't it be venv directory instead? I
Change by Lysandros Nikolaou :
--
title: Doc README wrong directory name for vent -> Doc README wrong directory
name for venv
___
Python tracker
<https://bugs.python.org/issu
Lysandros Nikolaou added the comment:
I would be happy to change this. I will submit a PR ASAP.
--
nosy: +lys.nikolaou
___
Python tracker
<https://bugs.python.org/issue34
Lysandros Nikolaou added the comment:
Can I submit a PR for this or is anybody else on it?
--
nosy: +lys.nikolaou
___
Python tracker
<https://bugs.python.org/issue34
Lysandros Nikolaou added the comment:
IMHO this is not a bug. Every file starting with a dot is hidden by default, so
this is somewhat correct behaviour. Since it is documented correctly I don't
this something needs to change here.
Yet again, could someone more experienced offer
Lysandros Nikolaou added the comment:
Also this throws a TypeError, because http_info.get_content_charset() returns
None with the new link. I think, this should be fixed as well.
--
nosy: +lys.nikolaou
___
Python tracker
<https://bugs.python.
Change by Lysandros Nikolaou :
--
keywords: +patch
pull_requests: +9521
stage: -> patch review
___
Python tracker
<https://bugs.python.org/issue32804>
___
_
Lysandros Nikolaou added the comment:
Shall I create a PR for this?
--
nosy: +lys.nikolaou
___
Python tracker
<https://bugs.python.org/issue30410>
___
___
Pytho
Lysandros Nikolaou added the comment:
I am trying to create a PR for this and was thinking of somehow updating
test.support, in order for someone to be able to find out what compiler was
used to build python. Would that make sense?
Also, in case this is indeed something we'd li
New submission from Lysandros Nikolaou :
In sysconfig.py there is a comment starting with FIXME that states that
_PY_VERSION should get its value from sys.version_info instead of sys.version,
because it is an implementation detail.
Should this be changed? If so, I would like to create a PR
Change by Lysandros Nikolaou :
--
keywords: +patch
pull_requests: +9575
stage: -> patch review
___
Python tracker
<https://bugs.python.org/issue30410>
___
_
Lysandros Nikolaou added the comment:
I'm working on changing _PY_VERSION to get its value from sys.version_info
instead of sys.version, but I am not sure what the best way is to map between a
release stage to the corresponding letter(release->rc). Could someone help me a
tiny bit w
Change by Lysandros Nikolaou :
--
keywords: +patch
pull_requests: +9619
stage: needs patch -> patch review
___
Python tracker
<https://bugs.python.org/issu
Change by Lysandros Nikolaou :
--
pull_requests: +9623
___
Python tracker
<https://bugs.python.org/issue24916>
___
___
Python-bugs-list mailing list
Unsubscribe:
Lysandros Nikolaou added the comment:
Following up on
https://github.com/python/cpython/pull/10321#discussion_r230604393 I would like
to summarise here what's been going on, in order to move the discussion here
forward. I've tried to make a PR for this issue, in which _PY_VERSI
Change by Lysandros Nikolaou :
--
nosy: +lys.nikolaou
___
Python tracker
<https://bugs.python.org/issue30533>
___
___
Python-bugs-list mailing list
Unsubscribe:
Lysandros Nikolaou added the comment:
Is anybody working on this or can I submit a PR?
--
nosy: +lys.nikolaou
___
Python tracker
<https://bugs.python.org/issue22
Lysandros Nikolaou added the comment:
Since Serhiy said that this is a pure documentation issue, I thought that a doc
PR is all that was needed, which I would be happy to make. Am I missing
something here?
--
___
Python tracker
<ht
Change by Lysandros Nikolaou :
--
pull_requests: +9668
stage: needs patch -> patch review
___
Python tracker
<https://bugs.python.org/issue22021>
___
___
Py
Lysandros Nikolaou added the comment:
It's been more than 3 years, since this was opened, but I will ask
nevertheless. Should a PR maybe made for this issue?
--
nosy: +lys.nikolaou
___
Python tracker
<https://bugs.python.org/is
Lysandros Nikolaou added the comment:
I think this issue should be discussed once more. I am not sure it's worth
defining __all__, but then we would have to include them in the docs. If you
think __all__ should be defined instead, then I could go through the trouble of
doing so. Co
Lysandros Nikolaou added the comment:
...but then we would have to include them in the docs... should be *but then we
would have to include all the public functions in the docs*.
--
___
Python tracker
<https://bugs.python.org/issue17
New submission from Lysandros Nikolaou :
On
https://docs.python.org/3/library/urllib.request.html?highlight=request#ftphandler-objects
there is the sentence "The login is always done with empty username and
password.", but in the (not so rare) case I am not missing something here,
New submission from Lysandros Nikolaou :
In test_functools.TestSingleDispatch.test_invalid_registrations
(https://github.com/python/cpython/blob/4c596d54aa6a55e9d2a3db78891e656ebbfb63c8/Lib/test/test_functools.py#L2299)
there is a FIXME with an immediate return afterwards that says that the
Change by Lysandros Nikolaou :
--
keywords: +patch
pull_requests: +9797
stage: -> patch review
___
Python tracker
<https://bugs.python.org/issue35252>
___
_
Lysandros Nikolaou added the comment:
It actually seems like the test after the FIXME is wrong and should be changed
or deleted altogether. Can someone give a pointer or two on what would be the
best choice here?
--
___
Python tracker
<ht
301 - 352 of 352 matches
Mail list logo
