[issue33478] PEP 8 CapWords reference wrong?
Amit Saha <amitsaha...@gmail.com> added the comment:
Thanks for the reply. I think I was not clear - the behavior of
string.capitalize() is correct as per documentation. But the PEP8 referring to
CapWords as cap words case is the bit I am not clear about, since `Capwords`
back when you call `string.capwords('CapWords') and not `CapWords`.
(Just reopening so that it doesn't get lost)
--
status: closed -> open
___
Python tracker <rep...@bugs.python.org>
<https://bugs.python.org/issue33478>
___
___
Python-bugs-list mailing list
Unsubscribe:
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue33478] PEP 8 CapWords reference wrong?
New submission from Amit Saha <amitsaha...@gmail.com>:
PEP 8 suggests class names and type variable names to be in CapWords case.
However:
>>> import string
>>> string.capwords('CapWord')
'Capword'
Wondering if this this an oversight or am I misunderstanding something?
--
assignee: docs@python
components: Documentation
messages: 316446
nosy: Amit.Saha, docs@python
priority: normal
severity: normal
status: open
title: PEP 8 CapWords reference wrong?
___
Python tracker <rep...@bugs.python.org>
<https://bugs.python.org/issue33478>
___
___
Python-bugs-list mailing list
Unsubscribe:
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue26323] Add assert_called() and assert_called_once() methods for mock objects
Amit Saha added the comment: Thank you Victor. -- ___ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue26323> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue26323] Add assert_called() and assert_called_once() methods for mock objects
Amit Saha added the comment: Thanks Michael, so looks like we are all set for merging this? -- ___ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue26323> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue26323] Add assert_called() and assert_called_once() methods for mock objects
Amit Saha added the comment: Updated patch -- Added file: http://bugs.python.org/file41997/issue26323.patch ___ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue26323> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue26323] Add assert_called() and assert_called_once() methods for mock objects
Amit Saha added the comment: @haypo : Just a reminder request to please view the updated patch. -- nosy: +Amit Saha ___ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue26323> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue26323] Add assert_called() and assert_called_once() methods for mock objects
Amit Saha added the comment: Updated patch with docs and addressed review comments. -- Added file: http://bugs.python.org/file41961/issue26323.patch ___ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue26323> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue26323] Add assert_called() and assert_called_once() methods for mock objects
Changes by Amit Saha <amitsaha...@gmail.com>: -- title: Add a assert_called() method for mock objects -> Add assert_called() and assert_called_once() methods for mock objects ___ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue26323> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue26323] Add a assert_called() method for mock objects
Amit Saha added the comment: Updated patch -- Added file: http://bugs.python.org/file41952/issue26323.patch ___ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue26323> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue26323] Add a assert_called() method for mock objects
Amit Saha added the comment: Thanks for the review. Updated patch addressing the comments. -- ___ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue26323> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue26323] Add a assert_called() method for mock objects
Amit Saha added the comment: Added assert_call_once() -- Added file: http://bugs.python.org/file41946/issue26323.patch ___ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue26323> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue26323] Add a assert_called() method for mock objects
Amit Saha added the comment: Thanks for your comments. I am +1 to those additions and would be happy to update the patch. Let me know if I should go ahead. -- ___ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue26323> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue26323] Add a assert_called() method for mock objects
Amit Saha added the comment: Please take a look at the attached patch. -- keywords: +patch Added file: http://bugs.python.org/file41903/issue26323.patch ___ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue26323> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue26323] Add a assert_called() method for mock objects
Amit Saha added the comment: Fixed the test name -- Added file: http://bugs.python.org/file41904/issue26323.patch ___ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue26323> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue26323] Add a assert_called() method for mock objects
Changes by Amit Saha <amitsaha...@gmail.com>: -- type: -> enhancement ___ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue26323> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue26323] Add a assert_called() method for mock objects
New submission from Amit Saha: Would a patch for adding a assert_called() method to mocked objects be welcome for inclusion? We do have a assert_not_called() method, so I think this may be a good idea. Please let me know and I will work on it. -- components: Library (Lib) messages: 259960 nosy: Amit.Saha priority: normal severity: normal status: open title: Add a assert_called() method for mock objects ___ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue26323> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue17583] IDLE HOWTO
Amit Saha added the comment: Hello, I just wanted to check if I should attach the image files separately and submit the text as a diff? Thanks. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue17583 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue17854] symmetric difference operation applicable to more than two sets
New submission from Amit Saha:
The description of the symmetric difference operation implies that it cannot be
applied to more than two sets
(http://docs.python.org/3/library/stdtypes.html#set.symmetric_difference).
However, this is certainly possible:
s={1,2}
t={2,3}
u={3,4}
s^t^u
{1, 4}
s.symmetric_difference(t).symmetric_difference(u)
{1, 4}
I am not sure how much of a semantic sense that makes, given that symmetric
difference is by definition for two sets.
(http://en.wikipedia.org/wiki/Symmetric_difference).
So, either the operator should be fixed to allow only two sets or the
description be updated.
--
assignee: docs@python
components: Documentation
messages: 187899
nosy: Amit.Saha, docs@python
priority: normal
severity: normal
status: open
title: symmetric difference operation applicable to more than two sets
type: behavior
versions: Python 3.3
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue17854
___
___
Python-bugs-list mailing list
Unsubscribe:
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue17854] symmetric difference operation applicable to more than two sets
Amit Saha added the comment: On some more thought, perhaps the description should be updated. Since s^t^u is effectively (s^t)^u and hence the implementation does not violate the definition. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue17854 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue17854] symmetric difference operation applicable to more than two sets
Amit Saha added the comment: I think the only change I am suggesting is the description of the ^ operator to be something like this: set ^ other ^ .. Return a new set with elements from the sets which are not present in more than one set I do understand that this is not really what the operator and the corresponding operation symmetric_difference() allows semantically. But it does make it consistent with the description of operators such as the | or , but then their operation allows multiple sets semantically. Hmm may be it is fine as it is.. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue17854 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue17583] IDLE HOWTO
Amit Saha added the comment: I have tried to incorporate most of the suggestions and made some other changes as well. Hope it looks better now. I haven't yet split it into two separate versions. -- Added file: http://bugs.python.org/file29654/idle.patch ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue17583 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue17583] IDLE HOWTO
Amit Saha added the comment: Hello Éric Araujo, thanks. Oh I thought it did support, and hence I created the diff in exactly the way you mention. i also went ahead and tested it by 'hg import' -ing it into a cpython clone and i was all excited to see all my images there :-) But, yeah I can certainly attach the images separately. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue17583 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue17583] IDLE HOWTO
Amit Saha added the comment: Thanks Ezio. I am almost done with incorporating the changes suggested and will submit a patch sometime in the next day or so. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue17583 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue17583] IDLE HOWTO
Amit Saha added the comment: Hi Todd, I just signed the Python contributor agreement electronically. You probably missed the link to the rSt source in my original report. Here it is [1]. I would want this HOWTO to cover all aspects of IDLE from an user's perspective. I have some ideas about what to add, but I would like to hear from you as well. Thanks. [1] http://amitsaha.github.com/site/notes/_sources/articles/idle/article.txt -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue17583 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue17583] IDLE HOWTO
Amit Saha added the comment: Adding the patch here. I am not sure about how to add the screenshots, so I haven't done them. Just attached the document as a patch (note that I have placed in doc/howto). Thanks for the comments. -- hgrepos: +180 keywords: +patch Added file: http://bugs.python.org/file29641/idle.patch ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue17583 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue17583] IDLE HOWTO
Amit Saha added the comment:
Hi Ezio, thanks for your review comments.
I will make the changes to the document, and also add the images in a later
patch.
I do agree that repeating package names for Python 2 and Python 3 is perhaps
not an ideal way. I am also trying to think of other ways to justify having two
separate documents: may be the code samples? print 'Hello world' versus
print('Hello World') ?
Thanks.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue17583
___
___
Python-bugs-list mailing list
Unsubscribe:
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue17583] IDLE HOWTO
Amit Saha added the comment: Hi Todd, thanks for your comments. I wanted to clarify that I intend to make this a HOWTO, not a FAQ. I hope that's fine? -Amit. -- ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue17583 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue17583] IDLE HOWTO
New submission from Amit Saha: I would like to propose a new HOWTO discussing IDLE from a user's perspective. I feel that the current documentation at http://docs.python.org/3/library/idle.html is not sufficient to be pointed to a newbie programmer or someone who wants to teach his/her students to IDLE. For example, being an experienced person myself, I didn't know how to start IDLE on Linux! Whether it was a separate package, or whether it was already installed (That may be my own shortcoming, but never the less). I started a document this morning which can be seen here [1]. The source is here[2] [1] http://amitsaha.github.com/site/notes/articles/idle/article.html [2] http://amitsaha.github.com/site/notes/_sources/articles/idle/article.txt I am putting up my hand to write the HOWTO and maintain it for 2.7 and 3.3+. Comments? -- components: IDLE messages: 185600 nosy: Amit.Saha priority: normal severity: normal status: open title: IDLE HOWTO type: enhancement versions: Python 3.3 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue17583 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
