Am 15.06.2013 um 08:18 schrieb Christopher Armstrong :
>> As far as actual *proposals* go, I have these ones, that are all independent:
>>
>> 1. include all keyword arguments in log output without requiring
>> specifying the formatting in the string
>> 2. make it really easy to specify the "syst
Hi,
#6499 (Teach chain certificates to SSL server endpoints string syntax) has been
pronounced ready for merge but since I’m no committer, I can’t do that myself.
It would be *great* if it could be merged before Ashwini cuts the release
branch!
Thanks & sorry for the noise,
—h
On Jun 14, 2013, at 10:43 PM, Christopher Armstrong
wrote:
> I don't think it's worth coming up with some kind of GUID-based
> system, because I don't think anyone's going to go to the trouble to
> use it, and I think it basically offers no practical benefit over
> simple event names.
Here are
On Jun 14, 2013, at 10:48 PM, Christopher Armstrong
wrote:
> There's... a lot here. I'm overwhelmed by how complex this system
> would be, and I think that end users would be as well. I don't really
> want to put UUIDs into my source code, whether I type them or paste
> them, and I don't want t
This was resolved :)
cheers
lvh
___
Twisted-Python mailing list
Twisted-Python@twistedmatrix.com
http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python
On 06/15/2013 06:48 AM, Christopher Armstrong wrote:
There's... a lot here. I'm overwhelmed by how complex this system
would be, and I think that end users would be as well. I don't really
want to put UUIDs into my source code, whether I type them or paste
them, and I don't want to have to invok
On Jun 15, 2013, at 3:55 AM, Phil Mayers wrote:
> On 06/15/2013 06:48 AM, Christopher Armstrong wrote:
>
>> There's... a lot here. I'm overwhelmed by how complex this system
>> would be, and I think that end users would be as well. I don't really
>> want to put UUIDs into my source code, whethe
On Jun 14, 2013, at 11:18 PM, Christopher Armstrong
wrote:
> This conversation has gotten pretty sprawling; time to reel it in with
> some code.
>
> What do you think of this for an API that meets in the middle?
>
> https://gist.github.com/radeex/5787124
>
> This example implementation only
On 06/15/2013 12:13 PM, Glyph wrote:
I am really, really puzzled by this reaction. I am wondering if you
read my message carefully, or if I didn't express myself well.
Careful re-reading of the very last bit of your message suggests I may
have misunderstood.
I think I understand the "final
On Sat, Jun 15, 2013 at 2:18 AM, Hynek Schlawack wrote:
>
> Am 15.06.2013 um 08:18 schrieb Christopher Armstrong
> :
>> What do you think of this for an API that meets in the middle?
>>
>> https://gist.github.com/radeex/5787124
>>
>> This example implementation only concerns itself with the point
On Sat, Jun 15, 2013 at 6:37 AM, Glyph wrote:
>
> On Jun 14, 2013, at 11:18 PM, Christopher Armstrong
> wrote:
>
> This conversation has gotten pretty sprawling; time to reel it in with
> some code.
>
> What do you think of this for an API that meets in the middle?
>
> https://gist.github.com/rad
On Thu, Jun 13, 2013 at 5:14 PM, Glyph wrote:
> Hello everybody. Today I'd like to talk about everyone's favorite subsystem
> within Twisted: logging.
>
> There are a number of problems with Twisted's logging system.
>
> The general theme of these problems is that Twisted log system was designed
>
On Sat, Jun 15, 2013 at 11:09 AM, Christopher Armstrong
wrote:
> On Thu, Jun 13, 2013 at 5:14 PM, Glyph wrote:
>> Hello everybody. Today I'd like to talk about everyone's favorite subsystem
>> within Twisted: logging.
>>
>> There are a number of problems with Twisted's logging system.
>>
>> The g
On Jun 15, 2013, at 5:28 AM, Phil Mayers wrote:
> On 06/15/2013 12:13 PM, Glyph wrote:
>
>> I am really, really puzzled by this reaction. I am wondering if you
>> read my message carefully, or if I didn't express myself well.
>
> Careful re-reading of the very last bit of your message suggest
On Jun 15, 2013, at 8:33 AM, Christopher Armstrong
wrote:
> It sounds like you're arguing that the human-readable *.log format
> should be closer to the simple key/value representation that we use
> underneath.
>
> Would you also argue that instead of having a log line that looks like:
>
> 20
On Jun 15, 2013, at 8:46 AM, Christopher Armstrong
wrote:
> Yeah... I feel like a lot of the things you say in this email aren't
> related to the point I was trying to get across, which was the
> interface and effect, not the implementation of it.
Even if it's not really what you'd intended, I
On Jun 15, 2013, at 9:17 AM, Christopher Armstrong
wrote:
> I think I would just want one more feature:
>
Logger().emit(dudelog.LogLevel.warn, a="hi")
>
> Right now, this doesn't spit out anything into my log file, with
> default observers. I want it to emit some simple representation of
On Sat, Jun 15, 2013 at 9:38 PM, Glyph wrote:
>
> On Jun 15, 2013, at 9:17 AM, Christopher Armstrong <
> ra...@twistedmatrix.com> wrote:
>
> I think I would just want one more feature:
>
> Logger().emit(dudelog.LogLevel.warn, a="hi")
>
>
> Right now, this doesn't spit out anything into my log fil
18 matches
Mail list logo
