Re: Formal Question to Steering Council (re recent PEP8 changes)

[Random832]

On Fri, Jul 3, 2020, at 08:48, Rhodri James wrote:
> As I said in my preamble, it doesn't matter whether you believe that is 
> true or think it's utter bollocks.  I asked the question to get the 
> Steering Council's opinion, not anyone else's.  If you collectively 
> really must rehash the arguments again, please have the decency to do so 
> in a different thread.

The idea that the statement was in any way related to one of the authors being 
named "White" was an *obvious factual mistake* in your post. Regardless of 
anything else, that is *not a matter of opinion*, so saying whose opinion you 
wanted is irrelevant.
-- 
https://mail.python.org/mailman/listinfo/python-list

Re: Formal Question to Steering Council (re recent PEP8 changes)

[o1bigtenor]

On Sat, Jul 4, 2020 at 10:41 AM Random832  wrote:

> On Fri, Jul 3, 2020, at 08:48, Rhodri James wrote:
> > As I said in my preamble, it doesn't matter whether you believe that is
> > true or think it's utter bollocks.  I asked the question to get the
> > Steering Council's opinion, not anyone else's.  If you collectively
> > really must rehash the arguments again, please have the decency to do so
> > in a different thread.
>
> The idea that the statement was in any way related to one of the authors
> being named "White" was an *obvious factual mistake* in your post.
> Regardless of anything else, that is *not a matter of opinion*, so saying
> whose opinion you wanted is irrelevant.
>

Copied from the commit:

Instead of requiring that comments be written in Strunk & White Standard
English, require instead that English-language comments be clear and easily
understandable by other English speakers. This accomplishes the same goal
without upholding relics of white supremacy. Many native English speakers
do not use Standard English as their native dialect, so requiring
conformation to Standard English centers whiteness in an inappropriate and
unnecessary way, and can alienate and put up barriers for people of color
and those whose native dialect of English is not Standard English. This
change is a simple way to correct that while maintaining the original
intent of the requirement.

I would point out that even suggesting that the issue be a *obvious factual
mistake* only serves to prove that you didn't read the thing and I, at
least, wonder why you're offering an opinion on any part of the discussion.

IMO the language in the commit is inflammatory and should either be revised
or it and the commit removed for its clear intellectual disfunction.

Regards

Regards
-- 
https://mail.python.org/mailman/listinfo/python-list

Re: Assign Excel cell value from Datepicker widget Selection using Python

[narenchunduri]

I am trying to assign a widget to an excel cell. Convertion wont help me.Thanks
-- 
https://mail.python.org/mailman/listinfo/python-list

Re: Formal Question to Steering Council (re recent PEP8 changes)

[Random832]

On Sat, Jul 4, 2020, at 12:33, o1bigtenor wrote:
> I would point out that even suggesting that the issue be a *obvious 
> factual mistake* only serves to prove that you didn't read the thing 
> and I, at least, wonder why you're offering an opinion on any part of 
> the discussion. 

I said obvious because even if it was not obvious from the commit message 
itself, it had *already been explained* in the thread on the other mailing list 
by the time Michael Torrie posted (July 02 15:14) his assertion of "The fact 
she would conflate an author's name with some kind of race-related thing". I 
even recall raising the question of whether he had in fact read any of that 
discussion. After all, Ethan Furman made the same mistake in his original post, 
and was corrected *very* early on in the discussion, so repeating it several 
days later makes little sense.

*Regardless whether you agree or not* with the premise that "standard english" 
is a subtle means of enforcing white supremacy, the fact that some people do 
believe that is a far more plausible explanation for the statement in the 
commit message than the fact that one of the authors happens to have been named 
"White", and the idea that it was because of the latter only exists in the 
imagination of those determined to assume the worst of the person who wrote the 
commit message.





On Tue, Jun 30, 2020, at 08:44, Ethan Furman wrote:
> On 06/30/2020 05:03 AM, Łukasz Langa wrote:
> > 
> >> On 30 Jun 2020, at 12:44, Ethan Furman  >> > wrote:
> >>
> >> Of course I don't know if Keara or Guido knew any of this, but it 
> >> certainly feels to me that the commit message is ostracizing an entire 
> >> family line because they had the misfortune to have the wrong last name.  
> >> In fact, it seems like Strunk & White is making changes to be inclusive in 
> >> its advice -- exactly what I would have thought we wanted on our side 
> >> ("our side" being the diverse and welcoming side).
> > 
> > In any case, saying that Keara and Guido mistook the family name of one of 
> > the authors for skin color feels derogatory.
> 
> My apologies, that was not my intent.  As I said, I never knew what it 
> was until today (er, yesterday now).
-- 
https://mail.python.org/mailman/listinfo/python-list

Re: Formal Question to Steering Council (re recent PEP8 changes)

[Ethan Furman]

On 07/04/2020 10:32 AM, Random832 wrote:


I said obvious because even if it was not obvious from the commit message 
itself, it had *already been explained* in the thread on the other mailing list


That would require Michael to have been reading the other mailing list to know 
that.  Just because the information is out there, doesn't mean everybody has 
seen it.

--
~Ethan~
--
https://mail.python.org/mailman/listinfo/python-list

Re: Assign Excel cell value from Datepicker widget Selection using Python

[DL Neil via Python-list]

On 5/07/20 5:20 AM, narenchund...@gmail.com wrote:

I am trying to assign a widget to an excel cell. Convertion wont help me.Thanks



That's true - and false!

Unfortunately, these posts have revealed little about you and your level 
of understanding of Python specifically, and computer programming more 
generally. This lack of information creates an impression that you are 
not used to working within a professional team. The example could easily 
be a professional task, or a student assignment. In the latter case, we 
will be happy to help you learn, but are not keen to 'do your homework'. 
(also, please be advised that there is a separate Python-Tutor 
Discussion List)


To solve this problem requires an understanding of Python and how it 
works, plus ipy/Jupiter and their widgets, and Excel as seen through the 
openpyxl library. It is not a trivial task!



To the problem:-

First, we must understand how ipy.widgets work 
(https://minrk-ipywidgets.readthedocs.io/en/latest/examples/Widget%20Basics.html). 
A widget is not like Python's basic input() which displays a "prompt" 
and collects a (str) value for return across an assignment statement, eg


amount = input( "How much? " )

A widget is an instantiated class, and as such we must consider its 
"attributes" and "methods" - which has the pre-requisite of 
understanding how Python works with "objects".


The web.ref describes the value property. So, if the DatePicker()'s 
result is assigned to an intermediate variable, that could be 
printed-out, together with its type(). This will provide valuable 
information.


Then, assign the value property of that variable (which is actually an 
object; that class instantiated) to another intermediate variable - 
let's call that returned_date, and print its value and type.


Finally, we should be able to reconcile the above data-items with the 
workbook's format/type demands, so that the date can be assigned to the 
B2 cell...



Let us know how you get on (copy-paste any relevant code and errors into 
your email message, if relevant)...

--
Regards =dn
--
https://mail.python.org/mailman/listinfo/python-list

Re: Formal Question to Steering Council (re recent PEP8 changes)

[Random832]

On Sat, Jul 4, 2020, at 18:17, Ethan Furman wrote:
> On 07/04/2020 10:32 AM, Random832 wrote:
> 
> > I said obvious because even if it was not obvious from the commit message 
> > itself, it had *already been explained* in the thread on the other mailing 
> > list
> 
> That would require Michael to have been reading the other mailing list 
> to know that.  Just because the information is out there, doesn't mean 
> everybody has seen it.

ok, you know what?

regardless of hairsplitting about how obvious or not it is what she meant, and 
whether or not "it's because of the name White" was a reasonable conclusion to 
jump to, none of that changes that the conclusion was, in fact, incorrect. So 
trying to fight with me for pointing that out and claiming I was offering my 
"opinion" was unreasonable. I was not offering an opinion, I was pointing out a 
factual error, and arguing that the error was reasonable to make rather than 
being obvious doesn't change that.
-- 
https://mail.python.org/mailman/listinfo/python-list