[issue19061] Shelve documentation security warning is not visible

anatoly techtonik added the comment: On Sun, Sep 22, 2013 at 2:57 PM, Georg Brandl wrote: > > Georg Brandl added the comment: > > > me[1]> open() function description is a wrong place for warning that is > related to a whole module > > you[2]> common, it is visible, that's the point anyway > > m

[issue19061] Shelve documentation security warning is not visible

Georg Brandl added the comment: > me[1]> open() function description is a wrong place for warning that is related to a whole module > you[2]> common, it is visible, that's the point anyway > me[3]> it is not visible on mobile > you[4]> we do not support mobile Your complaint was that it is "loca

[issue19061] Shelve documentation security warning is not visible

anatoly techtonik added the comment: On Sun, Sep 22, 2013 at 2:11 PM, Georg Brandl wrote: > > Georg Brandl added the comment: > > > I believe that it is pretty easy with mobile browser due to screen > > constraints. Can you test this on your mobile devices? > > Sorry, but we don't adapt the docs

[issue19061] Shelve documentation security warning is not visible

Georg Brandl added the comment: > I believe that it is pretty easy with mobile browser due to screen > constraints. Can you test this on your mobile devices? Sorry, but we don't adapt the docs *content* to any specific device. You should never only read just a screenful in any case. This is t

[issue19061] Shelve documentation security warning is not visible

anatoly techtonik added the comment: On Sun, Sep 22, 2013 at 12:42 PM, Georg Brandl wrote: > Oh, please. It's big and red and directly below the open() description, > how could you miss it? > I believe that it is pretty easy with mobile browser due to screen constraints. Can you test this on yo

[issue19061] Shelve documentation security warning is not visible

Georg Brandl added the comment: Oh, please. It's big and red and directly below the open() description, how could you miss it? -- ___ Python tracker ___

[issue19061] Shelve documentation security warning is not visible

Roundup Robot added the comment: New changeset 1d850260a356 by Georg Brandl in branch '2.7': Closes #19061: make shelve security warning consistent between 2.x and 3.x. http://hg.python.org/cpython/rev/1d850260a356 -- nosy: +python-dev resolution: -> fixed stage: -> committed/rejected

[issue19061] Shelve documentation security warning is not visible

anatoly techtonik added the comment: The scope of warning is wrong. It is not a warning for open() call, and that's why it is easy to miss. -- ___ Python tracker ___ ___

[issue19061] Shelve documentation security warning is not visible

Georg Brandl added the comment: Using the "warning" directive can be backported from the 3.x docs. For 3.x, it's already prominent enough. Your "screen border" is not everyone's screen border. -- nosy: +georg.brandl versions: -Python 2.6, Python 3.1, Python 3.2, Python 3.3, Python 3.4

[issue19061] Shelve documentation security warning is not visible

New submission from anatoly techtonik: This is a follow up to issue #8855. Currently the security warning is completely invisible from Python 2 docs http://docs.python.org/2/library/shelve.html and is located under screen border on Python 3 docs. The proposal is to move warning out of the des

[issue19061] Shelve documentation security warning is not visible

anatoly techtonik added the comment: tag:easy -- ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.p