[prev in list] [next in list] [prev in thread] [next in thread] 

List:       python-ideas
Subject:    Re: [Python-ideas] History on proposals for Macros?
From:       Guido van Rossum <guido () python ! org>
Date:       2015-03-31 14:52:38
Message-ID: CAP7+vJKACghN_2d9KhSExoe3iZSpwLwjgip7kqdjWx6fgmjKqg () mail ! gmail ! com
[Download RAW message or body]

[Attachment #2 (multipart/alternative)]


On Mon, Mar 30, 2015 at 9:26 PM, Matthew Rocklin <mrocklin@gmail.com> wrote:

> Is something stopping you from exploring this? Do you have specific ideas
>> on how to improve on macropy?
>>
>
> Macropy is great but it requires an import-hook.  Many scientific users
> work interactively.
>
>
>> It sounds almost as if you would like to implement this but you want some
>> kind of promise ahead of time that your work will be incorporated into the
>> language. But that's just not how it works. When you want to explore a big
>> idea like this, at some point you have to be willing to take the risk of
>> writing code without a guaranteed pay off. Haoyi didn't ask for macropy to
>> be incorporated into Python -- in fact he was surprised at the amount of
>> uptake it got.
>>
>
> The hard problem isn't building macros, it's deciding whether or not
> macros are good for Python.  I'm trying to start a discussion.  If this
> isn't the right place for that then I apologize.
>

This is the right place, and we're now at the point where it's your job to
either show a concrete design spec that can actually be implemented, and
have its tires kicked, or just go off and build something. In the latter
case you'll probably learn about some practical issues that nobody might
have thought of yet.


> You've received quite a bit of feedback (and, may I say, push back :-)
>> from a small number of python-ideas veterans -- you can take this or leave
>> it, but at this point I think you've gotten about as much mileage out of
>> the list as can be expected.
>>
>
> My apologies.  I didn't realize that I was misusing this list.  I also
> didn't realize that I was receiving push-back, the comments here seemed
> friendly and encouraging.
>

You weren't misusing the list. Maybe (based on your next message) you
weren't reading it though. :-)


> Last year at SciPy the message I heard was "If you want to convince the
> core team then come to python-ideas armed with motivating use cases."  Here
> I am :)
>
> Anyway, if there isn't any interest then I'll leave off.  Thank you all
> for your time,
>

I think you misunderstand. There's interest but there are also real
concerns. I really do think that an implementation (if, as you say, that
isn't the hard part) would be very helpful to judge whether it is a
desirable feature. (Maybe you discover you can do it in a way that can be
distributed via PYPI -- "pip install macros".)

-- 
--Guido van Rossum (python.org/~guido)

[Attachment #5 (text/html)]

<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On Mon, Mar 30, 2015 \
at 9:26 PM, Matthew Rocklin <span dir="ltr">&lt;<a href="mailto:mrocklin@gmail.com" \
target="_blank">mrocklin@gmail.com</a>&gt;</span> wrote:<br><blockquote \
class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc \
solid;padding-left:1ex"><div dir="ltr"><div class="gmail_extra"><div \
class="gmail_quote"><span class=""><blockquote class="gmail_quote" style="margin:0px \
0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div \
dir="ltr">Is something stopping you from exploring this? Do you have specific ideas \
on how to improve on \
macropy?<br></div></blockquote><div><br></div></span><div>Macropy is great but it \
requires an import-hook.   Many scientific users work interactively.  </div><span \
class=""><div>  </div><blockquote class="gmail_quote" style="margin:0px 0px 0px \
0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div \
dir="ltr"><div>It sounds almost as if you would like to implement this but you want \
some kind of promise ahead of time that your work will be incorporated into the \
language. But that&#39;s just not how it works. When you want to explore a big idea \
like this, at some point you have to be willing to take the risk of writing code \
without a guaranteed pay off. Haoyi didn&#39;t ask for macropy to be incorporated \
into Python -- in fact he was surprised at the amount of uptake it \
got.<br></div></div></blockquote><div><br></div></span><div>The hard problem \
isn&#39;t building macros, it&#39;s deciding whether or not macros are good for \
Python.   I&#39;m trying to start a discussion.   If this isn&#39;t the right place \
for that then I apologize.<br></div></div></div></div></blockquote><div><br></div><div>This \
is the right place, and we&#39;re now at the point where it&#39;s your job to either \
show a concrete design spec that can actually be implemented, and have its tires \
kicked, or just go off and build something. In the latter case you&#39;ll probably \
learn about some practical issues that nobody might have thought of \
yet.<br></div><div>  </div><blockquote class="gmail_quote" style="margin:0 0 0 \
.8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div \
class="gmail_extra"><div class="gmail_quote"><div></div><span class=""><blockquote \
class="gmail_quote" style="margin:0px 0px 0px \
0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div \
dir="ltr"><div></div>You&#39;ve received quite a bit of feedback (and, may I say, \
push back :-) from a small number of python-ideas veterans -- you can take this or \
leave it, but at this point I think you&#39;ve gotten about as much mileage out of \
the list as can be expected.<br></div></blockquote><div><br></div></span><div>My \
apologies.   I didn&#39;t realize that I was misusing this list.   I also didn&#39;t \
realize that I was receiving push-back, the comments here seemed friendly and \
encouraging.</div></div></div></div></blockquote><div><br></div><div>You weren&#39;t \
misusing the list. Maybe (based on your next message) you weren&#39;t reading it \
though. :-)<br></div><div>  </div><blockquote class="gmail_quote" style="margin:0 0 0 \
.8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div \
class="gmail_extra"><div class="gmail_quote"><div><div>Last year at SciPy the message \
I heard was &quot;If you want to convince the core team then come to python-ideas \
armed with motivating use cases.&quot;   Here I am \
:)</div></div><div><br></div><div>Anyway, if there isn&#39;t any interest then \
I&#39;ll leave off.   Thank you all for your time,  </div></div></div></div> \
</blockquote></div><br></div><div class="gmail_extra">I think you misunderstand. \
There&#39;s interest but there are also real concerns. I really do think that an \
implementation (if, as you say, that isn&#39;t the hard part) would be very helpful \
to judge whether it is a desirable feature. (Maybe you discover you can do it in a \
way that can be distributed via PYPI -- &quot;pip install macros&quot;.)<br \
clear="all"></div><div class="gmail_extra"><br>-- <br><div \
class="gmail_signature">--Guido van Rossum (<a \
href="http://python.org/~guido">python.org/~guido</a>)</div> </div></div>



_______________________________________________
Python-ideas mailing list
Python-ideas@python.org
https://mail.python.org/mailman/listinfo/python-ideas
Code of Conduct: http://python.org/psf/codeofconduct/

[prev in list] [next in list] [prev in thread] [next in thread] 

Configure | About | News | Add a list | Sponsored by KoreLogic