This says is better than I: Often when people have problems with figuring out how to do something, or to make things work the way they expect, they will ask about it on the mail list. The most common response to their initial question is something like, "Please create a small runnable app that shows the problem and send that to the list." This is a very useful tool for those giving help because:
- They can run, tweak, and play with the sample, drawing on their own experiences with debugging wxPython apps. - There is nothing vague and confusing about code. If somebody just tries to explain what they tried to do in prose without sample code, it is very likely that there will be a break-down in communication somewhere, especially if the helper and the helpee speak different languages natively. - Having a runnable sample to play with makes *much* better use of the helper's time. Often a problem can be spotted in a minute or two, and a solution tested and sent back to the list in five. Without a sample the helper needs to first duplicate the problem (which may or may not be successful if the initial description is vague) and then find a solution. This can multiply the time spent on the problem 100% or more. - Most of the time, if the person needing help makes the effort to make a runnable sample he will figure out how to solve the problem himself before even sending it to the list, and will have learned something valuable in the process. - There is even an industry acronym for making small samples like this when requesting help. See SSCCE.org <http://sscce.org/>. On Fri, Apr 12, 2013 at 2:18 PM, Daniel Hyams <[email protected]> wrote: > So doesn't that mean that "the problem", whatever that is, is not related > to trying to exclude either one, as was the intent of the original post? > > I'm not trying to be too critical here, but your posts need to be more > specific about what's going on. Otherwise no one can help you. One other > HUGE hint....when you find a problem, create a runnable sample that > reproduces the problem. Post the sample along with any pyinstaller-related > info that you feel is specific to your situation (like what command line > options you used, your spec file if applicable, etc.). > > > > > > > > On Fri, Apr 12, 2013 at 2:10 PM, dbv <[email protected]> wrote: > >> The problem persists with either one or both copies of the module. >> >> -- >> You received this message because you are subscribed to the Google Groups >> "PyInstaller" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected]. >> To post to this group, send email to [email protected]. >> Visit this group at http://groups.google.com/group/pyinstaller?hl=en. >> For more options, visit https://groups.google.com/groups/opt_out. >> >> >> > > > > -- > Daniel Hyams > [email protected] > -- Daniel Hyams [email protected] -- You received this message because you are subscribed to the Google Groups "PyInstaller" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/pyinstaller?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
