Differences between revisions 10 and 11
Revision 10 as of 2004-10-12 19:01:28
Size: 4711
Editor: 212-32-244-232
Comment:
Revision 11 as of 2004-10-12 20:17:29
Size: 4956
Editor: c-24-11-17-229
Comment:
Deletions are marked like this. Additions are marked like this.
Line 25: Line 25:
Possibly. I've written a few useful-to-me modules that I think others might also find useful. I'd like to share them, but I am NOT on-line 24/7, and would like someone to host them for downloading. As for WikiNames, would LWickJr do? If so, how do I change it? -- ["lwickjr"] ["lwickjr"] Possibly. I've written a few useful-to-me modules that I think others might also find useful. I'd like to share them, but I am NOT on-line 24/7, and would like someone to host them for downloading. As for WikiNames, would LWickJr do? If so, how do I change it?
Line 29: Line 29:
["lwickjr"] Don't have a passport. As for my "nick", the L is my first inital, the Wick is my family name, and the Jr is because I've got the same name as my father. Isn't this "real" enough? BTW, what do you think of the modules I describe below?
Line 37: Line 38:
   * Provides a mechanism whereby arbitrary one-word names may be assigned to callable objects for use with the preceding mechanism. This allows one to dispense with the requirement to type fully-quaqlified long.nested.module.names for selected callables, and is where the module gets its name.    * Provides a mechanism whereby arbitrary one-word names may be assigned to callable objects for use with the preceding mechanism. This allows one to dispense with the requirement to type fully-qualified long.nested.module.names for selected callables, and is where the module gets its name.

Welcome to my page.

I have a few questions that I've been unable to find answer for.

All the documentation I've seen seems to assume that someone wanting to publish Python modules has -- and knows how to use -- a 24/7 file server available to use.

This is not always the case.

Further, I have found the documentation on distributing Python modules to be strong on the mechanicals of how to PACKAGE modules [somewhat over-kill, I think, for simple drop-in single-file modules], and nearly non-existant on how to PUBLISH them.

Could someone please write a page on ["How to publish Python modules"] that is understandable by someone with significant *computer* experience but minimal *internet* experience?

SkipMontanaro


Hi Iwick, before I answer some of your questions, I'd like you to consider RealNamesPlease. It is one of our WikiGuidelines, and it has worked well for us so far.

I'm not completely sure what you mean by publishing Python modules. If you need a space to upload your Python modules, you might want to consider StarshipPython. It used to be free for PSA members, but the PSA has ceased to exist, so I guess a small donation to the PythonSoftwareFoundation will do now. Would that solve your problem?

-- JohannesGijsbers

["lwickjr"] Possibly. I've written a few useful-to-me modules that I think others might also find useful. I'd like to share them, but I am NOT on-line 24/7, and would like someone to host them for downloading. As for WikiNames, would LWickJr do? If so, how do I change it?

With a real name I meant the one in your passport, not capitalizing your nick into a WikiName. Changing it is easy: just create the new page and cut all content from this page into it. Then delete this page and log in using your new name. -- JohannesGijsbers

["lwickjr"] Don't have a passport. As for my "nick", the L is my first inital, the Wick is my family name, and the Jr is because I've got the same name as my father. Isn't this "real" enough? BTW, what do you think of the modules I describe below?


My more-interesting modules [by the way, how do I link to a Wiki page with text that doesn't match the destination page's name?] include "Alias", "Edit", and "UT". I'll add others to this page as I have opportunity [the machine I'm typing this on isn't my home system].

General outlines:

  • Alias
    • Provides a mechanism whereby arbitrary callables are *effectively* converted to commands in interactive Python, but not in modules. To do this, Alias splits off the first word of the command line, attempts to evaluate it, and iff it is callable, the tail of the command is also evaluated and passed to the callable as an argument tuple. This allows the manual use of "dir", "reload", et al, as statements without requiring that parentheses be typed. Parentheses are still required in module source, however, and in any function calls in the tail of the command line.
    • Provides a mechanism whereby arbitrary one-word names may be assigned to callable objects for use with the preceding mechanism. This allows one to dispense with the requirement to type fully-qualified long.nested.module.names for selected callables, and is where the module gets its name.
    • Provides a mechanism for allowing modules to be imported through a bare reference to the module name.
    • Provides a mechanism whereby modules imported by the preceding mechanism may auto-register aliases of their own choosing. Entering the name of a module that has already been imported does not re-import the module; rather it re-updates whatever auto-alias associations might exist in that module at the time the name is re-entered.
    • Provides its own list of aliases, available via the preceding mechanism, for managing the alias dictionary.
    • Does not function under IDLE without disabling the default sub-process. Probably does not function correctly, or even at all, without IDLE.
  • Edit
    • Provides an Alias that attempts to open for editing the source for the module where the argument was defined, positioned, if possible, on the line where the definition starts.
    • Provides a mechanism for recording the current size and position of the active IDLE window such that subsequent attempts to open the window open it with the remembered geometry.
    • Provides an IDLE menu item to trigger the preceding mechanism.
    • Functions only under IDLE. Does not function correctly without disabling the default sub-process.
  • UT
    • Provides several "utility" functions that I've found useful:
    • A "smart" reload substitute that can automaticaly re-load other modules in dependancy-order, if the module being reloaded registers its dependancies.
    • A convenience wrapper for cPickle that allows [un-]pickling single objects from/to a specified file with a single function call.
    • Others that I don't recall at the moment.


CategoryHomepage

lwickjr (last edited 2014-04-19 09:07:19 by DaleAthanasias)

Unable to edit the page? See the FrontPage for instructions.