SilentGhost added the comment:
Lisa, please be careful with nosy list.
--
nosy: +Romuald, SilentGhost, William.McBrine, amaury.forgeotdarc, belopolsky,
brett.cannon, ccorbacho, ced, cptnwillard, davidfraser, dpalms2011, epu,
eric.smith, flox, fredwheeler, kzsolt, mark.dickinson
Changes by SilentGhost <ghost@runbox.com>:
--
nosy: +amaury.forgeotdarc, belopolsky, meador.inge, pitrou
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python
SilentGhost added the comment:
> Silent Ghost: perhaps you were thinking of Issue 23883 (adding to __all__ in
> various modules). This case is the opposite: we want to limit the exported
> names.
It was one of mine, issue 10895. Been dead for a
SilentGhost added the comment:
I wouldn't say it matter, "from configparser import _ChainMap" works too, but
that's just how imports work in Python. There is not reason to do what you've
done on purpose - ChainMap is undocumented and is clearly just a detail of
implementation.
SilentGhost added the comment:
What do you mean by "breaks"? Also, why do you encode your string as utf-8?
--
components: +Library (Lib) -Extension Modules
nosy: +SilentGhost, orsenthil
___
Python tracker <rep...@bugs.pyth
Changes by SilentGhost <ghost@runbox.com>:
--
components: +Library (Lib) -Extension Modules
nosy: +orsenthil
stage: -> patch review
___
Python tracker <rep...@bugs.python.org>
<http://bugs.pyt
Changes by SilentGhost <ghost@runbox.com>:
--
nosy: +haypo
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/issue26799>
___
__
Changes by SilentGhost <ghost@runbox.com>:
--
nosy: +haypo, martin.panter, yselivanov
stage: -> patch review
type: -> behavior
___
Python tracker <rep...@bugs.python.org>
<http://bugs.
SilentGhost added the comment:
I think the note at the top makes it perfectly clear that PEP 344 is superseded
by PEP 3134 which has correct Python version.
--
nosy: +SilentGhost
resolution: -> not a bug
stage: -> resolved
status: open -&g
Changes by SilentGhost <ghost@runbox.com>:
--
nosy: +georg.brandl
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/issue26794>
___
_
SilentGhost added the comment:
This seems to be only triggered when moving a symlink into its destination.
Assumption in the code is that when _samefile returns True, it must be due to
case-insensitive filesystem, rather than this edge case.
--
nosy: +SilentGhost, tarek
type
Changes by SilentGhost <ghost@runbox.com>:
--
versions: -Python 3.2, Python 3.3, Python 3.4
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python
Changes by SilentGhost <ghost@runbox.com>:
--
components: +Regular Expressions
nosy: +ezio.melotti, mrabarnett, pitrou, serhiy.storchaka
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python
Changes by SilentGhost <ghost@runbox.com>:
--
nosy: +georg.brandl
versions: -Python 3.2, Python 3.3, Python 3.4
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python
Changes by SilentGhost <ghost@runbox.com>:
--
components: +Extension Modules
nosy: +jnoller, sbt
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python
SilentGhost added the comment:
regex module is not part of the standard library and issues with it should be
reported on its bug tracker https://bitbucket.org/mrabarnett/mrab-regex
--
nosy: +SilentGhost
resolution: -> third party
stage: -> resolved
status: open -> closed
ty
SilentGhost added the comment:
While documentation seems not entirely clear, the openhook only applies to
files.
I'm not sure what is the logic behind the suggested change, what would openhook
do in your situation?
--
components: +Library (Lib)
nosy: +SilentGhost, serhiy.storchaka
Changes by SilentGhost <ghost@runbox.com>:
--
nosy: +serhiy.storchaka
type: -> behavior
___
Python tracker <rep...@bugs.python.org>
<http://bugs.pyt
Changes by SilentGhost <ghost@runbox.com>:
--
nosy: +michael.foord
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/issue26752>
___
_
Changes by SilentGhost <ghost@runbox.com>:
--
assignee: -> docs@python
components: +Documentation
nosy: +docs@python
stage: -> patch review
___
Python tracker <rep...@bugs.python.org>
<http://bugs.
Changes by SilentGhost <ghost@runbox.com>:
--
Removed message: http://bugs.python.org/msg263251
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python
Changes by SilentGhost <ghost@runbox.com>:
--
versions: -Python 3.4
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/issue25931>
___
Changes by SilentGhost <ghost@runbox.com>:
--
nosy: +lars.gustaebel
type: -> behavior
___
Python tracker <rep...@bugs.python.org>
<http://bugs.pyt
Changes by SilentGhost <ghost@runbox.com>:
--
components: +Interpreter Core
nosy: +haypo
stage: -> patch review
___
Python tracker <rep...@bugs.python.org>
<http://bugs.pyt
SilentGhost added the comment:
Documentation [0] has a very clear explanation of how str.strip works.
[0] https://docs.python.org/2/library/stdtypes.html#str.strip
--
nosy: +SilentGhost
resolution: -> not a bug
stage: -> resolved
status: open -&g
SilentGhost added the comment:
Serhiy, the OpenSSL links are now https
--
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/issue25910>
___
__
Changes by SilentGhost <ghost@runbox.com>:
--
nosy: +ncoghlan, yselivanov
stage: -> patch review
___
Python tracker <rep...@bugs.python.org>
<http://bugs.pyt
SilentGhost added the comment:
Licence text shouldn't be touched, I think.
http://www.openssl.org/docs/apps/ciphers.html#CIPHER_LIST_FORMAT became
https://www.openssl.org/docs/manmaster/apps/ciphers.html#CIPHER-LIST-FORMAT
If Martin still have the importer code somewhere, he probably could
Changes by SilentGhost <ghost@runbox.com>:
--
nosy: +jnoller, sbt
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/issue26732>
___
_
Changes by SilentGhost <ghost@runbox.com>:
--
components: +Interpreter Core -Extension Modules, Library (Lib)
nosy: +ncoghlan
stage: -> patch review
versions: +Python 3.6
___
Python tracker <rep...@bugs.python.org>
<http
Changes by SilentGhost <ghost@runbox.com>:
--
components: +Extension Modules, Library (Lib) -Interpreter Core
nosy: +georg.brandl
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python
Changes by SilentGhost <ghost@runbox.com>:
--
components: +Library (Lib)
nosy: +berker.peksag
stage: -> patch review
___
Python tracker <rep...@bugs.python.org>
<http://bugs.pyt
Changes by SilentGhost <ghost@runbox.com>:
--
nosy: +benjamin.peterson, brett.cannon, georg.brandl, haypo, ncoghlan,
yselivanov
stage: -> patch review
___
Python tracker <rep...@bugs.python.org>
<http://bugs.pyt
Changes by SilentGhost <ghost@runbox.com>:
--
nosy: +brett.cannon
type: -> behavior
versions: +Python 3.5
___
Python tracker <rep...@bugs.python.org>
<http://bugs.pyt
Changes by SilentGhost <ghost@runbox.com>:
--
components: +Extension Modules
nosy: +haypo, neologix, twouters
versions: +Python 3.6
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python
SilentGhost added the comment:
issue25485 seem to have addressed this.
--
nosy: +SilentGhost
resolution: -> duplicate
stage: -> resolved
status: open -> closed
___
Python tracker <rep...@bugs.python.org>
<http://bugs.pyt
SilentGhost added the comment:
Here is the review-able patch.
--
Added file: http://bugs.python.org/file42400/minrk_issue25544.diff
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/i
SilentGhost added the comment:
You can override the level if an environmental variable was defined. Not sure
why it needs to be responsibility of the ConfigParser.
While I'm not going to immediately close this issue, I don't think such a
backward-incompatible proposal is viable
Changes by SilentGhost <ghost@runbox.com>:
--
nosy: +michael.foord
stage: -> patch review
type: crash -> behavior
versions: -Python 3.4
___
Python tracker <rep...@bugs.python.org>
<http://bugs.
SilentGhost added the comment:
Here is the version of the patch suitable for the Rietveld. John, could you
perhaps provide an example file that uses UID values?
Also, the code is identical to handling of 0x50 token, perhaps it could be
incorporated into it.
--
nosy: +SilentGhost
Changes by SilentGhost <ghost@runbox.com>:
--
nosy: +pitrou
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/issue26703>
___
__
Changes by SilentGhost <ghost@runbox.com>:
--
nosy: +gpolo, kbk, roger.serwy, serhiy.storchaka, terry.reedy
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python
Changes by SilentGhost <ghost@runbox.com>:
--
status: pending -> open
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/issue26689>
___
_
SilentGhost added the comment:
I'm largely fine with it, bar the in-function import. It would also be good if
you could verify that no other temporary files are left after the function is
run.
As I said earlier, issue 25544 should have priority and it should get a
refreshed patch soon
Changes by SilentGhost <ghost@runbox.com>:
--
nosy: +ncoghlan, yselivanov
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python
Changes by SilentGhost <ghost@runbox.com>:
--
nosy: +jnoller, sbt
versions: +Python 3.6
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python
SilentGhost added the comment:
Hi Min RK, could you please update your patch so that it would cleanly apply to
the tip of default branch. Also since you're re-writing a big chunk of that
function, could I ask you to use with context manager for the temporary source
file.
--
nosy
SilentGhost added the comment:
I guess it would make sense to depend on issue25544 and implement the has_flag
with minrk's patch in mind. I guess his patch didn't get a second look because
it didn't apply cleanly.
In any case, for implementing has_flag using current best practice is what I'd
SilentGhost added the comment:
I understand that you're copying approach of has_function, but shouldn't you
remove this temporary file at the end of the function? Perhaps using
tempfile.NamedTemporaryFile would be a better solution (both in has_flag and
has_function). Also import can be moved
SilentGhost added the comment:
I've left a comment on Rietveld
--
nosy: +SilentGhost
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/i
Changes by SilentGhost <ghost@runbox.com>:
--
stage: -> patch review
versions: -Python 3.2, Python 3.3, Python 3.4, Python 3.5
___
Python tracker <rep...@bugs.python.org>
<http://bugs.pyt
Changes by SilentGhost <ghost@runbox.com>:
--
components: +email
nosy: +barry, r.david.murray
versions: +Python 3.5 -Python 3.4
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python
SilentGhost added the comment:
Left comments on Rietveld.
--
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/issue26488>
___
___
Pyth
SilentGhost added the comment:
Here is the patch.
--
nosy: +SilentGhost
stage: -> patch review
type: enhancement -> behavior
Added file: http://bugs.python.org/file42344/issue26679.diff
___
Python tracker <rep...@bugs.python.o
Changes by SilentGhost <ghost@runbox.com>:
--
resolution: fixed -> rejected
stage: -> resolved
___
Python tracker <rep...@bugs.python.org>
<http://bugs.
Changes by SilentGhost <ghost@runbox.com>:
--
versions: +Python 2.7
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/issue26673>
___
Changes by SilentGhost <ghost@runbox.com>:
--
components: +Extension Modules
nosy: +facundobatista, mark.dickinson, rhettinger, skrah
stage: -> patch review
versions: +Python 3.6
___
Python tracker <rep...@bugs.pytho
SilentGhost added the comment:
The mailing system is acting up, so just for the record, I've left comments on
rietveld regarding md5sum-style patch.
--
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/i
Changes by SilentGhost <ghost@runbox.com>:
--
nosy: +vinay.sajip
type: -> behavior
___
Python tracker <rep...@bugs.python.org>
<http://bugs.pyt
Changes by SilentGhost <ghost@runbox.com>:
--
resolution: -> wont fix
stage: -> resolved
status: open -> closed
___
Python tracker <rep...@bugs.python.org>
<http://bu
Changes by SilentGhost <ghost@runbox.com>:
--
components: +Tkinter
nosy: +gpolo, kbk, roger.serwy, serhiy.storchaka, terry.reedy
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python
SilentGhost added the comment:
I've left some comment on rietveld yesterday, not sure if you got the e-mail.
--
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/i
Changes by SilentGhost <ghost@gmail.com>:
--
nosy: +vinay.sajip
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/issue26664>
___
_
Changes by SilentGhost <ghost@gmail.com>:
--
nosy: +r.david.murray
versions: +Python 3.5
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python
Changes by SilentGhost <ghost@gmail.com>:
--
nosy: +benjamin.peterson, georg.brandl, pitrou, yselivanov
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python
Changes by SilentGhost <ghost@gmail.com>:
--
nosy: +georg.brandl
versions: +Python 3.6
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python
Changes by SilentGhost <ghost@gmail.com>:
--
components: +Windows
nosy: +martin.panter, paul.moore, steve.dower, tim.golden, zach.ware
versions: +Python 3.5
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python
Changes by SilentGhost <ghost@gmail.com>:
--
components: +Windows
nosy: +paul.moore, steve.dower, tim.golden, zach.ware
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python
Changes by SilentGhost <ghost@gmail.com>:
--
dependencies: +argparse.FileType for '-' doesn't work for a mode of 'rb'
nosy: +SilentGhost
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python
SilentGhost added the comment:
Ah, the bit about csv module doing it's own newline handling is what I missed.
Here is the updated patch.
--
Added file: http://bugs.python.org/file42306/issue26648_2.diff
___
Python tracker <rep...@bugs.python.
SilentGhost added the comment:
Here is the patch. Both this patch and the fix for #15421 might violate the
documented behaviour of getting the full week's worth of dates. I wonder if
that should also be documented.
--
keywords: +patch
nosy: +SilentGhost, rhettinger
stage: -> pa
Changes by SilentGhost <ghost@gmail.com>:
--
components: +Unicode
nosy: +ezio.melotti, haypo
type: -> behavior
___
Python tracker <rep...@bugs.python.org>
<http://bugs.pyt
SilentGhost added the comment:
While the 'U' mode has been deprecated it doesn't mean that your example
doesn't run in 3.5 - it runs just fine and will keep doing so until 4.0
I'm attaching patch that suggests using newline=None (even though it's a
default value for open), as that what seems
Changes by SilentGhost <ghost@gmail.com>:
--
nosy: +benjamin.peterson, brett.cannon, georg.brandl, ncoghlan, yselivanov
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python
Changes by SilentGhost <ghost@gmail.com>:
--
nosy: +bethard
versions: +Python 3.6 -Python 3.5
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python
Changes by SilentGhost <ghost@gmail.com>:
--
nosy: +loewis
versions: +Python 3.6 -Python 3.4
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python
SilentGhost added the comment:
Could any one of the core developers have a look? Seems like a rather
straightforward change.
--
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/i
Changes by SilentGhost <ghost@gmail.com>:
--
nosy: +jnoller, sbt
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/issue26633>
___
_
Changes by SilentGhost <ghost@gmail.com>:
--
nosy: +amaury.forgeotdarc, belopolsky, meador.inge
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python
Changes by SilentGhost <ghost@gmail.com>:
--
nosy: +georg.brandl
versions: -Python 3.4
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python
Changes by SilentGhost <ghost@gmail.com>:
--
nosy: +ezio.melotti, pitrou, rhettinger
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python
Changes by SilentGhost <ghost@gmail.com>:
--
nosy: +gvanrossum
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/issue26391>
___
_
Changes by SilentGhost <ghost@gmail.com>:
--
components: +Windows
nosy: +paul.moore, steve.dower, tim.golden, zach.ware
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python
SilentGhost added the comment:
Upon further investigation it seems this particular test needs to be just
skipped when running as __main__.
--
keywords: +patch
stage: -> patch review
Added file: http://bugs.python.org/file42255/issue25805.d
Changes by SilentGhost <ghost@gmail.com>:
--
dependencies: -trace module compares directories as strings (--ignore-dir)
resolution: -> rejected
stage: patch review -> resolved
status: open -> closed
___
Python tracker <rep.
Changes by SilentGhost <ghost@gmail.com>:
--
resolution: -> rejected
stage: patch review -> resolved
status: open -> closed
type: -> behavior
___
Python tracker <rep...@bugs.python.org>
<http:/
Changes by SilentGhost <ghost@gmail.com>:
--
stage: patch review -> resolved
status: open -> closed
___
Python tracker <rep...@bugs.python.org>
<http://bugs.
Changes by SilentGhost <ghost@gmail.com>:
--
components: +Interpreter Core
nosy: +benjamin.peterson, serhiy.storchaka
stage: -> patch review
___
Python tracker <rep...@bugs.python.org>
<http://bugs.pyt
SilentGhost added the comment:
I wonder if the devguide would be a more suitable place for these guidelines.
Here is the patch that adds them to stdblibchanges.rst
--
keywords: +patch
stage: needs patch -> patch review
versions: +Python 3.5, Python 3.6 -Python 3.4
Added file: h
SilentGhost added the comment:
I still think my fix is more appropriate as it ensures that known_paths and
sys.path stay connected somehow.
--
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/i
SilentGhost added the comment:
Documentation [0] has callable listed as a positional argument, and this is how
it should be used.
[0]
https://docs.python.org/2.7/library/unittest.html#unittest.TestCase.assertRaises
--
nosy: +SilentGhost
resolution: -> not a bug
stage: -> re
Changes by SilentGhost <ghost@gmail.com>:
--
nosy: +vinay.sajip
stage: -> patch review
___
Python tracker <rep...@bugs.python.org>
<http://bugs.pyt
SilentGhost added the comment:
Those methods were added in 3.5, so no wonder many people would be unaware of
them. I would suggest first taking such a proposal to python-ideas, since bug
tracker is not a venue for proposing/advocating such sweeping changes to the
language.
--
nosy
SilentGhost added the comment:
In fact most of the :exc: reference are pointing explicitly to
concurrent.futures.CancelledError (and those that don't probably should). It is
interesting that you weren't able to make use of that exception, because in
Lib/asyncio/futures.py#L23 it's clearly
SilentGhost added the comment:
Jason, could you provide an actual paste of interactive interpreter session, so
that any one could try to reproduce the issue.
--
nosy: +SilentGhost
stage: -> test needed
type: -> behavior
___
Python tracke
Changes by SilentGhost <ghost@gmail.com>:
--
nosy: +haypo
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/issue26601>
___
__
Changes by SilentGhost <ghost@gmail.com>:
--
nosy: +michael.foord, pitrou
versions: +Python 3.6 -Python 3.2, Python 3.3, Python 3.4
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python
SilentGhost added the comment:
This very much looks like a sentry problem. I'd suggest reporting it on their
bug tracker.
--
nosy: +SilentGhost
resolution: -> third party
stage: -> resolved
status: open -> closed
___
Python tra
Changes by SilentGhost <ghost@gmail.com>:
--
nosy: -SilentGhost
___
Python tracker <rep...@bugs.python.org>
<http://bugs.python.org/issue26267>
___
_
SilentGhost added the comment:
Erwin, you could clearly see in the screenshot that the print call is indented,
i.e. it starts in the 5th column, under letter "h" of the_world_is_flat. In
what you've typed here one can clearly see that "p" of print is under "
801 - 900 of 1379 matches
Mail list logo
