Hi ,
I am new one but ur talked make me laugh too :D , although here is relevant
link for you
" if Tk cannot come up with an exact match, it tries to find a similar font.
If that fails, Tk falls back to a platform-specific default font. Tk's idea
of what is "similar enough" probably doesn't correspond to your own view, so
you shouldn't rely too much on this feature."
http://www.pythonware.com/library/tkinter/introduction/x444-fonts.htm
Hope it helps you
On Thu, Feb 10, 2011 at 9:55 PM, wrote:
> Send Python-list mailing list submissions to
>[email protected]
>
> To subscribe or unsubscribe via the World Wide Web, visit
>http://mail.python.org/mailman/listinfo/python-list
> or, via email, send a message with subject or body 'help' to
>[email protected]
>
> You can reach the person managing the list at
>[email protected]
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Python-list digest..."
>
> Today's Topics:
>
> 1. Yappi error "context not found" (Brian)
> 2. Re: Markdown to reStructuredText (Michele Simionato)
> 3. Shared memory python between two separate shell-launched
> processes (Charles Fox (Sheffield))
> 4. Re: Easy function, please help. (Jason Swails)
> 5. Re: Shared memory python between two separate shell-launched
> processes (Jean-Paul Calderone)
> 6. Re: Problem with giant font sizes in tkinter (Cousin Stanley)
> 7. Re: email.encoders.encode_base64 creates one line only
> ([email protected])
> 8. Re: OO Python (Dan Stromberg)
> 9. Re: Easy function, please help. (Ethan Furman)
> 10. Re: Problem with giant font sizes in tkinter (rantingrick)
>
>
> -- Forwarded message --
> From: Brian
> To: [email protected]
> Date: Thu, 10 Feb 2011 05:38:43 -0800 (PST)
> Subject: Yappi error "context not found"
> I'm posting here because I can't find a Yappi specific mailing list.
>
> I've been using the rather brilliant Yappi from
> http://code.google.com/p/yappi/
> It works well for small programs with a few threads. However, when
> trying to run it over large programs with several hundred threads I've
> been getting the error "context not found".
>
> The most basic example I can come up with which illustrates the
> problem is below. Changing the number of threads started from 25 down
> to, say, 10, works fine. Any more than ~25 and the error keeps
> appearing. This is using Python 2.6.5 and Ubuntu Linux 10.04. I don't
> have another box to try this out on at the moment.
>
> I've tested a similar script using thread.start_new_thread() and that
> doesn't seem to have the problem. So is there some issue with Yappi
> and inheriting from threading.Thread?
>
> import yappi
> import time
> import threading
>
> class MyThread(threading.Thread):
>def run(self):
>time.sleep(1)
>
> yappi.start()
>
> for i in range(0,25):
>c = MyThread()
>c.start()
> time.sleep(1)
>
> yappi.print_stats()
> yappi.stop()
>
>
> Running the above gives:
> [*] [yappi-err] context not found.
> [*] [yappi-err] context not found.
> [*] [yappi-err] context not found.
> [*] [yappi-err] context not found.
> ...
>
> Any help appreciated.
>
>
>
> -- Forwarded message --
> From: Michele Simionato
> To: [email protected]
> Date: Thu, 10 Feb 2011 00:03:19 -0800 (PST)
> Subject: Re: Markdown to reStructuredText
> Looks cool, I will have a look at it, thanks!
>
>
>
> -- Forwarded message --
> From: "Charles Fox (Sheffield)"
> To: [email protected]
> Date: Thu, 10 Feb 2011 06:30:18 -0800 (PST)
> Subject: Shared memory python between two separate shell-launched processes
> Hi guys,
> I'm working on debugging a large python simulation which begins by
> preloading a huge cache of data. I want to step through code on many
> runs to do the debugging. Problem is that it takes 20 seconds to
> load the cache at each launch. (Cache is a dict in a 200Mb cPickle
> binary file).
>
> So speed up the compile-test cycle I'm thinking about running a
> completely separate process (not a fork, but a processed launched form
> a different terminal) that can load the cache once then dunk it in an
> area of shareed memory.Each time I debug the main program, it can
> start up quickly and read from the shared memory instead of loading
> the cache itself.
>
> But when I look at posix_ipc and POSH it looks like you have to fork
> the second process from the first one, rather than access the shared
> memory though a key ID as in standard C unix shared memory. Am I
> missing something? Are there any other ways to do this?
>
> thanks,
> Charles
>
>
>
> -- Forwarded message --
> From: Jason Swails
> To: Benjamin Kaplan
> Date: Thu, 10 Feb 2011 09:50:18 -0500
> Subject: Re: Easy function, please help.
>
>
> On Thu, Feb 10, 2011 at 3:31 AM, Benjamin Kaplan > wrote:
>
>>
>> > On Wed, Feb 9