,
Vinay Sajip
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
please let me know if they object? Otherwise I'll
go ahead and add them to .hgeol in the next hour or so.
Regards,
Vinay Sajip
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
http
) has trouble.
Not sure if that makes a difference or not.
It's only really an issue for new / inexperienced users, I agree. Since these
files are installed only on Windows systems, there's no reason for them not to
have the native line endings.
Regards,
Vinay Sajip
.
Does anyone here see problems with that approach?
Regards,
Vinay Sajip
[1] http://stackoverflow.com/a/933996
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
http://mail.python.org
me
to.
Regards,
Vinay Sajip
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
to only update environments which were
set up with the particular version of Python which was updated. ISTM pyvenv.cfg
will need to have a version=X.Y.Z line in it, which is added during venv
creation. That information will be used by the tool to only update specific
environments.
Regards,
Vinay
an isolated set of library
dependencies for a project.
Regards,
Vinay Sajip
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
http://mail.python.org/mailman/options/python-dev/archive%40mail
,
__PYTHONV_LAUNCHER__, which points to itself, before it execs the real Python.
On OS X, Python code checks for this, rather than sys.executable, to determine
the location of the pyvenv.cfg file. This seems to work for me (Ned Deily is
looking into it more closely, I believe).
Regards,
Vinay Sajip
, but it also provides some useful information about
the version (for a user, rather than the update script) without actually having
to invoke the interpreter to check.
Regards,
Vinay Sajip
___
Python-Dev mailing list
Python-Dev@python.org
http
Is it something I'm doing wrong, or is there a problem with the issue
tracker/Rietveld integration?
Regards,
Vinay Sajip
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
http://mail.python.org
since I'm on vacation for one week
from June 2nd.
I believe it is ready to integrate now. I aim to do it tomorrow (26 May) a.m.
UTC, so that it can make the next alpha.
Regards,
Vinay Sajip
___
Python-Dev mailing list
Python-Dev@python.org
http
since I'm on vacation for one week
from June 2nd.
It's now implemented in the default branch :-)
Regards,
Vinay Sajip
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
http://mail.python.org
,
Vinay Sajip
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
now? It will need
integrating with the existing VS2010 solution file, and at the moment I cannot
do that integration because I haven't yet got a full VS2010 build environment,
just a VS2008 one.
Regards,
Vinay Sajip
___
Python-Dev mailing list
Python
. If people
generally feel strongly about this, I can delete the .exe and re-introduce it
later if/when appropriate. It might have had a few rough edges, but I wouldn't
have characterised the patch as half-finished - that seems a little harsh :-)
Regards,
Vinay Sajip
is gone.
Regards,
Vinay Sajip
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
.
There's nothing in there related to #12394 - just a pysetup3.exe file, which I
had originally overlooked and have now removed.
Regards,
Vinay Sajip
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
should have the correct shebang line, and the PEP 397 launcher should do the
right thing.
I'm sorry for all the confusion I've caused here :-(
Regards,
Vinay Sajip
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman
Antoine Pitrou solipsis at pitrou.net writes:
Deciding to remove packaging from 3.3 is another instance of the same
mistake, IMO.
What's the rationale for leaving it in, when it's known to be
incomplete/unfinished?
Regards,
Vinay Sajip
definitely needs to be supported in the stdlib, even if it's a
painful process getting there. The barriers seem more social than technical, but
hopefully the divide-and-conquer-with-multiple-PEPs approach will prevail.
Regards,
Vinay Sajip
___
Python-Dev mailing
that :-)
Regards,
Vinay Sajip
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
Nick Coghlan ncoghlan at gmail.com writes:
ini-style is often good enough, and failing that there's json. Or, you
just depend on PyYAML :)
Except when PyYAML is packaged and distributed using dist.yaml :-)
Regards,
Vinay Sajip
___
Python-Dev
between hooks
and code reuse between hooks. I don't see any drawback to using only one file ?
I was assuming that the dist.yaml file would just have callable references here;
I suppose having (sizable) Python fragments in dist.yaml might become unwieldy.
Regards,
Vinay Sajip
expect a C compiler to be installed everywhere. Perhaps security against
backdoors could also be provided through other mechanisms, such as signing of
binary installers.
Regards,
Vinay Sajip
___
Python-Dev mailing list
Python-Dev@python.org
http
see that it mandates use of
SSL, or even signing, by anyone. At least some people will require that an
installer be invokable with an option that causes it to bail if any part of
what's being installed can't be verified (for some value of verified).
Regards,
Vinay Sajip
to be optional (the user doing the installing
would be the decider as to whether to go ahead and install, with signature, or
lack thereof, in mind).
Regards,
Vinay Sajip
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo
martin at v.loewis.de writes:
See above. Also notice that such signing is already implemented, as part
of PEP 381.
BTW, I notice that the certificate for https://pypi.python.org/ expired a week
ago ...
Regards,
Vinay Sajip
___
Python-Dev
be fine, but I'm
not convinced that the command-class paradigm is appropriate in this case. The
whole intricate initialize_options/finalize_options/set_undefined_options
/get_finalized_command/reinitialize_command dance just makes me say,
Seriously?.
Regards,
Vinay Sajip
to ensure that all constituencies
are represented (for example, features needed only on Windows, such as binary
distributions and executable scripts, have lagged a little bit behind).
Regards,
Vinay Sajip
___
Python-Dev mailing list
Python-Dev
of
fulfilling those needs is too fragile - else, why do you need things like Bento?
Regards,
Vinay Sajip
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
http://mail.python.org/mailman/options
can be worked on in comparative isolation; other things, like
packaging, need inputs from a wider range of people to gain the necessary
credibility.
Regards,
Vinay Sajip
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman
that
there might be problems with its basic design.
Regards,
Vinay Sajip
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
http://mail.python.org/mailman/options/python-dev/archive%40mail
from this mirror, and I pulled and merged from it lots of times
without any issues.
Regards,
Vinay Sajip
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
http://mail.python.org/mailman
ensuring all their threads are done and there are no
unaccounted-for references to loggers and handlers.
Regards,
Vinay Sajip
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
http
someone please suggest any
improvements, or let me know if I've missed anything?
Regards,
Vinay Sajip
[1] http://bugs.python.org/issue4384
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
,
Vinay Sajip
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
, but please tell me if that's not the case.
Regards,
Vinay Sajip
[1] http://mail.python.org/pipermail/python-dev/2004-October/049282.html
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe
, and that the method can be overridden to use a more secure
implementation (e.g. HMAC-signed pickles).
Regards,
Vinay Sajip
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
http
call this
serializer with the LogRecord instance as the only argument, and use the return
value as the serialized form, instead of calling pickle.dumps.
Regards,
Vinay Sajip
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman
James Yonan james at openvpn.net writes:
I'd like to propose that the Python community standardize on a
deferred object for asynchronous return values
Have a look at PEP 3148:
http://www.python.org/dev/peps/pep-3148/
___
Python-Dev mailing list
James Yonan james at openvpn.net writes:
I'd like to propose that the Python community standardize on a
deferred object for asynchronous return values, modeled after the
well-thought-out Twisted Deferred class.
Ummm, sorry, I seem to need new glasses :-( ignore my last post.
Hi all,
I'm planning to make some smallish changes to logging in Python 3.2, please see
http://plumberjack.blogspot.com/2010/09/improved-queuehandler-queuelistener.html
If you're interested, I'd be grateful for any feedback you can give.
Regards,
Vinay Sajip
Nick Coghlan ncoghlan at gmail.com writes:
To further reduce overhead, would it make sense for the signature of
the QueueListener constructor to be (queue, *handlers)?
Good suggestion - thanks.
Regards,
Vinay
___
Python-Dev mailing list
, there may be other
small changes: but you can copy the code over from the 3.2 branch in the Python
SVN repository later and it should work fine under Python 2.6 and 2.7.
Of course if you do find any problems (or have any other questions), please let
me know asap :-)
Regards,
Vinay Sajip
Martin v. Löwis martin at v.loewis.de writes:
I'm still with Guido here: I'd accept PEP 333 as final in the state it
had last week, give PJE's edits a new PEP number, and accept that as
final right away also.
This sounds like it should make everyone happy - no rewriting of history, and no
of this change, I'll publicise to the wider community in a few days.
Regards,
Vinay Sajip
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
http://mail.python.org/mailman/options/python
Nick Coghlan ncoghlan at gmail.com writes:
Looking at your checkin though, I wonder if it might be worth
implementing some little formatting style classes to get rid of the
if/elif chains from the Formatter code. Something like:
Fair comment: I did think about the messiness of that if/elif,
or backwards-incompatible fixes do you
need to add, i.e. things which cannot be catered for by release27-maint? Or is
this just about the *principle* of having a 2.8?
Regards,
Vinay Sajip
___
Python-Dev mailing list
Python-Dev@python.org
http
Vinay Sajip vinay_sajip at yahoo.co.uk writes:
need to add, i.e. things which cannot be catered for by release27-maint? Or is
this just about the *principle* of having a 2.8?
Never mind - I've just picked up the extra posts on this thread, which for some
reason didn't show up in my reader
it used to be; it
was an inline check before, but now can be easily reimplemented e.g. via
subclassing and overriding the usesTime() method.
Regards,
Vinay Sajip
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo
taste than about the
actual usage of str.format's flexibility; we may as well accommodate that
preference, as it encourages in a small way the use of {}-formatting.
Regards,
Vinay Sajip
___
Python-Dev mailing list
Python-Dev@python.org
http
comment; I don't know your preferences. The basicConfig()
change has now been checked into the py3k branch.
Regards,
Vinay Sajip
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
http
, then everyone would get the print_stack()
even if they didn't want it.
Regards,
Vinay Sajip
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
http://mail.python.org/mailman/options/python-dev
change all usages to
SafeConfigParser; should I do it now (before the 3.2 beta is cut) or hold off
for now?
Regards,
Vinay Sajip
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
http
and replaced by StreamHandler pointing to a different stream.
This, I believe, should be changed in line with what I've said above.
Comments?
Regards,
Vinay Sajip
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python
logging
logging.basicConfig()
before calling mylib.func(), and you get
WARNING:mylib:Something happened!
which is what you would expect.
Regards,
Vinay Sajip
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python
it is - your mistake or mine?
Regards,
Vinay Sajip
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
- when NullHandler is added to a library logger (rather than the
root logger), basicConfig() works as expected. See the mylib/myapp example in my
other post on this thread.
Regards,
Vinay Sajip
___
Python-Dev mailing list
Python-Dev@python.org
http
infrastructure - adding to
test.support. Sorry, I should have been more explicit.
Regards,
Vinay Sajip
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
http://mail.python.org/mailman/options
be
helpful.
Regards,
Vinay Sajip
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
from
library modules in general? It could be argued that the behaviour you're
proposing is confusing/inconsistent to some people.
Regards,
Vinay Sajip
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
raise an exception, then don't
add a NullHandler to your top-level loggers.
Regards,
Vinay Sajip
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
http://mail.python.org/mailman/options
Django logger (e.g. django.db.models) would need to have that
handler added.
Regards,
Vinay Sajip
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
http://mail.python.org/mailman/options
stand by the statement that
one line (or more precisely, one function call) is not too much to ask here, so
yes - not too inconvenient. That's emphatically not because I'm the module's
author and used to it.
Regards,
Vinay Sajip
___
Python-Dev mailing
, but the correct thing for any code to do when an error condition is
detected (in most situations at least) is to raise an exception. It would be
quite wrong for code to e.g. call logger.error(...) instead of raise ...
Regards,
Vinay Sajip
___
Python-Dev
of view, IMO you're not adding to the discussion in the
same way that Nick, say, has.
Regards,
Vinay Sajip
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
http://mail.python.org/mailman
Brett did some philosophy studies).
See my earlier comment about formatting and the potential for bikeshedding ;-)
Regards,
Vinay Sajip
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe
that outputs received writes via the
logging module?
Is this for use at the C level? At the Python level, there's a post I wrote a
while back which shows how to use a logger like an output stream:
http://plumberjack.blogspot.com/2009/09/how-to-treat-logger-like-output-stream.html
Regards,
Vinay Sajip
logging support to their library; I don't believe their time has been wasted.
Regards,
Vinay Sajip
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
http://mail.python.org/mailman/options
to
support line-based output formats. Actually the line-based nature is a function
of the handler and/or formatter and just reflects what people tend to want most
of the time.
Regards,
Vinay Sajip
___
Python-Dev mailing list
Python-Dev@python.org
http
response to Nick's post (about concurrent.futures)
could be characterized as I don't care, as I even made a specific proposal
about how a change could be implemented.
Regards,
Vinay Sajip
___
Python-Dev mailing list
Python-Dev@python.org
http
of (say) the root logger.
Regards,
Vinay Sajip
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
), and the little details need to be agreed, so does it make sense to
create a PEP about this? What do people think - is this bureaucratic overkill?
Regards,
Vinay Sajip
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman
Antoine Pitrou solipsis at pitrou.net writes:
Ok, I'm sorry for the harsh words.
I really hope this discussions leads to somewhere.
No offence taken, and do do I :-)
Regards,
Vinay Sajip
___
Python-Dev mailing list
Python-Dev@python.org
http
skip at pobox.com writes:
logging.error(error 1 2 3 %s % yup)
ERROR:root:error 1 2 3 yup
logging.error(error 1 2 3 %s, yup)
ERROR:root:error 1 2 3 yup
The second form should be preferred in library code as long as the format
string expansion is deferred until after the
Vinay Sajip vinay_sajip at yahoo.co.uk writes:
No offence taken, and do do I
s/do do/so do/
Perhaps it was a Freudian slip admitting that I *am* a dodo!
Regards,
Vinay
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org
, I'll think about posting on this topic after
ruminating on it for a bit.
Regards,
Vinay Sajip
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
http://mail.python.org/mailman/options
of knowing which
threads are currently servicing a particular app is to maintain a set of them.
Regards,
Vinay Sajip
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
http://mail.python.org
Vinay Sajip vinay_sajip at yahoo.co.uk writes:
Glenn Linderman v+python at g.nevcal.com writes:
Or what am I missing?
And one more thing: the filters for *both* apps are called for a given request.
One will return True, the other will return False.
Bear in mind that the intention
quite see what you were getting at.
Having looked at it more carefully, you're right: the threads set is not needed.
You can just return tlocal.appName == self.app.name. I missed that, so thanks
for teaching me something, too :-)
Regards,
Vinay Sajip
. It needn't be.
Indeed, and the very first code sample in the logging documentation shows
exactly the simplistic easy usage you're talking about. I can't see why anyone
would be scared off by that example.
Regards,
Vinay Sajip
___
Python-Dev mailing
behaviour can be obtained by setting logging.lastResort = None.
Regards,
Vinay Sajip
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
http://mail.python.org/mailman/options/python-dev/archive
not intentional. The diff
of the changes is here:
https://gist.github.com/736120
Comments are of course welcome.
Regards,
Vinay Sajip
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
http
Antoine Pitrou solipsis at pitrou.net writes:
Yes, I am talking about this one. I am not asking that you revert it; I
am just saying that it is generally appreciated if substantial patches
get proposed on the tracker before being committed.
OK, sorry - point taken.
In this case since
, which would
be off-putting for most users.
Regards,
Vinay Sajip
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
http://mail.python.org/mailman/options/python-dev/archive%40mail
if it helps make possible a better resolution of
#10626 (as an archetype of unraisable-exception scenarios), that would be a
good outcome.
Regards,
Vinay Sajip
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo
the focus of
diagnostic scrutiny is at those times.
Severity is not the only filtering mechanism, merely the simplest and most
common one, that people can readily grasp.
Regards,
Vinay Sajip
___
Python-Dev mailing list
Python-Dev@python.org
http
API, so that it can be inherited from etc?
I realise we're in beta and hence feature freeze ... just sayin'. We're all
consenting adults here, after all :-)
Regards,
Vinay Sajip
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org
Nick Coghlan ncoghlan at gmail.com writes:
This could actually make a reasonably good basic for a task oriented
subsection of the logging documentation. Something like:
Good suggestion, I'll see what I can do.
Thanks,
Vinay Sajip
___
Python
thinking needs to be done
around this area.
Regards,
Vinay Sajip
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
).
But it seemed a little unwieldy and came across plainly as the afterthought it
admittedly was :-)
Regards,
Vinay Sajip
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
http://mail.python.org
don't want me to add more verbiage about basicConfig when your
overall feeling is that there's too much documentation?
Regards,
Vinay Sajip
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
) but also as a tool to provide
program output (e.g. doing some of the program's real work, say by calling
error() to print an error message).
Regards,
Vinay Sajip
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo
Nick Coghlan ncoghlan at gmail.com writes:
Gosh, Nick, that was fast! I'm still making changes, but thanks for spotting and
highlighting the typos and omissions. I've just checked in a further update;
hopefully it'll get built soon so we can all see the latest changes.
Regards,
Vinay Sajip
including lvl.
Please report this on bugs.python.org. Check that you were referring to the 2.6
documentation - I didn't see any references to attributes there (following a
quick scan). Ideally, link to the wrong doc section on docs.python.org in your
bug report.
Thanks,
Vinay Sajip
be
constructing a LogRecord using LogRecord(**kwargs)).
- Link to the latter section from the Formatter, Filter sections.
Anyone see problems with this, or have a better suggestion?
Regards,
Vinay Sajip
___
Python-Dev mailing list
Python-Dev@python.org
http
Tim Golden mail at timgolden.me.uk writes:
On 13/12/2010 10:31, Vinay Sajip wrote:
[...]
Ideally, link to the wrong doc section on docs.python.org in your bug
report.
Now that's not a piece of advice you see very often :)
True, but this area changed after 2.6 was released (after
Nick Coghlan ncoghlan at gmail.com writes:
Yep, that's what I had assumed you were going to do (this did come up
in the big thread about the logging docs, but you may have missed it).
I hadn't missed it - I'm just spelling out in more detail what I'm going to do.
That said, you can't get a
Nick Coghlan ncoghlan at gmail.com writes:
Yep, that's what I had assumed you were going to do (this did come up
in the big thread about the logging docs, but you may have missed it).
Ok, I've now checked in this change, and would be grateful for any feedback.
Time for a break :-)
Thanks a
Nick Coghlan ncoghlan at gmail.com writes:
Hmm, that may not have built correctly, since it isn't showing up in the web
version of the dev docs yet. I skimmed the diff on python-checkins though, and
it looked good to me.
I'll keep an eye on the build (built OK on my machine but I'm not sure
101 - 200 of 425 matches
Mail list logo
