Re: [Twisted-Python] naming question before we end up committed...
Does anyone have an opinion on renaming it to twisted.logger? Or have a better suggestion? +1 on dropping `python` here. That's a weird namespace anyway something as central as logging shouldn't be there. ___ Twisted-Python mailing list Twisted-Python@twistedmatrix.com http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python
Re: [Twisted-Python] naming question before we end up committed...
+1 for twisted.logger. ___ Twisted-Python mailing list Twisted-Python@twistedmatrix.com http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python
[Twisted-Python] naming question before we end up committed...
While working on the package I just brought up in another thread, I realize we have another big new package coming in 14.1, twisted.python.logger, and I'm wondering what the .python part of that package name is doing in there, and what value it adds. It's where twisted.python.log used to be, of course, but now I'm just wondering if we're just making the same mistake twice. Does anyone have an opinion on renaming it to twisted.logger? Or have a better suggestion? -glyph ___ Twisted-Python mailing list Twisted-Python@twistedmatrix.com http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python
Re: [Twisted-Python] naming question before we end up committed...
+0 on “logger” (top-level names have a history of whimsy) +1 on making it top-level hth lvh signature.asc Description: Message signed with OpenPGP using GPGMail ___ Twisted-Python mailing list Twisted-Python@twistedmatrix.com http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python
