(Not Stephen either).
I've been using attrs for some time now, but only superficially. I'm not
sure yet if I want to make it mandatory for my team or not.
My biggest issues so far are:
- how to truly leverage it with a declarative ORM? (SQLAlchemy in my case,
the workaround being to only use a subset of attrs' functionalities, at the
expense of additional complexity).
- how to make it interop with type annotations? (Which is also an issue for
SQLAlchemy, AFAIK, at this point).
I won't be in Pycon (but I will be at PyParis next month, obviously, since
I'm organising it ;). Hynek will be there, from what I see so obviously if
a PEP or some fresh ideas emerge from the discussions there, I'll be more
than happy.
Have a nice Pycon.
S.
On Tue, May 16, 2017 at 11:04 PM, Guido van Rossum
Stephen,
What features of attrs specifically solve your use cases?
--Guido
On Tue, May 16, 2017 at 12:18 PM, Stephan Houben
wrote: Hi all,
Thanks to this thread I learned about the "attrs" library. I am a heavy namedtuple (ab)user but I think I will be using attrs going forward.
If something like attrs would made it in the standard library it would be awesome.
Thanks,
Stephan
2017-05-16 20:08 GMT+02:00 Brett Cannon
: Maybe we can bring this up as a lightning talk at the language summit to see who in the room has the appropriate background knowledge? And obviously someone can talk to Hynek to see if he wants to provide input based on community feedback for attrs and lessons learned.
On Tue, 16 May 2017 at 08:11 Guido van Rossum
wrote: Maybe Lukasz is interested?
On May 16, 2017 8:00 AM, "Chris Angelico"
wrote: On Wed, May 17, 2017 at 12:53 AM, Guido van Rossum
wrote: I could also try this myself in my spare time at PyCon
(surprisingly, I
have some!). It sounds kind of interesting. However I've never used the 'attrs' package...
Me neither, so I'm not really an ideal person to head this up. Is there anyone who (a) knows what is and isn't Pythonic, (b) has used 'attrs', and (c) has spare time? It's not an easy trifecta but we can hope!
ChrisA _______________________________________________ Python-ideas mailing list Python-ideas@python.org https://mail.python.org/mailman/listinfo/python-ideas Code of Conduct: http://python.org/psf/codeofconduct/
_______________________________________________ Python-ideas mailing list Python-ideas@python.org https://mail.python.org/mailman/listinfo/python-ideas Code of Conduct: http://python.org/psf/codeofconduct/
_______________________________________________ Python-ideas mailing list Python-ideas@python.org https://mail.python.org/mailman/listinfo/python-ideas Code of Conduct: http://python.org/psf/codeofconduct/
-- --Guido van Rossum (python.org/~guido)
_______________________________________________ Python-ideas mailing list Python-ideas@python.org https://mail.python.org/mailman/listinfo/python-ideas Code of Conduct: http://python.org/psf/codeofconduct/
-- Stefane Fermigier - http://fermigier.com/ - http://twitter.com/sfermigier - http://linkedin.com/in/sfermigier Founder & CEO, Abilian - Enterprise Social Software - http://www.abilian.com/ Chairman, Free&OSS Group / Systematic Cluster - http://www.gt-logiciel-libre.org/ Co-Chairman, National Council for Free & Open Source Software (CNLL) - http://cnll.fr/ Founder & Organiser, PyData Paris - http://pydata.fr/ --- “You never change things by fighting the existing reality. To change something, build a new model that makes the existing model obsolete.” — R. Buckminster Fuller