01:16.09 | *** join/#fredlug plarsen (n=plarsen@c-24-125-211-129.hsd1.va.comcast.net) |
02:15.05 | *** join/#fredlug doublejoon (n=doublejo@d-74-214-44-92.cpe.metrocast.net) |
03:30.11 | *** join/#fredlug jsmith_ (n=jsmith@216.207.245.1) |
10:30.42 | *** join/#fredlug jsmith_ (n=jsmith@216.207.245.1) |
13:29.37 | *** join/#fredlug plarsen (n=plarsen@208.176.91.226.ptr.us.xo.net) |
13:30.26 | plarsen | Good morning!! |
13:57.09 | *** join/#fredlug jsmith (n=jsmith@142.131.189.26) |
14:00.44 | *** join/#fredlug jsmith_ (n=jsmith@216.207.245.1) |
21:12.50 | *** join/#fredlug nmcbride_ (n=nmcbride@208.176.91.226.ptr.us.xo.net) |
21:13.40 | nmcbride_ | stickster: when you are using eclipse and create a new packge, what is the __init__.py for? Is that just where you are suppose to start the whole package at? |
21:15.00 | stickster | nmcbride_: Google "Python __init__.py" |
21:15.57 | nmcbride_ | The â__init__.pyâ files are required to make Python treat the directories as containing packages; this is done to prevent directories with a common name, such as âstringâ, from unintentionally hiding valid modules that occur later on the module search path. In the simplest case, â__init__.pyâ can just be an empty file, but it can also execute initialization code for the package or set the __all__ variable, described later. |
21:16.21 | nmcbride_ | so then what ever the name of the directory is, is what you would use for the module :D |
21:24.45 | stickster | right |
22:23.21 | *** join/#fredlug quigleymd (n=quigley@c-24-125-204-247.hsd1.va.comcast.net) |
22:54.39 | *** join/#fredlug quigleymd (n=quigley@c-24-125-204-247.hsd1.va.comcast.net) |
23:40.06 | *** join/#fredlug forsaken (n=eric@c-71-62-234-185.hsd1.va.comcast.net) |
23:59.48 | *** join/#fredlug forsaken (n=eric@c-71-62-234-185.hsd1.va.comcast.net) |