lwickjr

Legacy Wiki Page

This page was migrated from the old MoinMoin-based wiki. Information may be outdated or no longer applicable. For current documentation, see python.org.

lwickjr 2011-09-15 18:23:10: I`ve just reviewed the site.py bug mentioned below, and it still exists in Python 3.1.2. Will someone please fix it?

lwickjr 2011-09-15 18:20:53: Trivial edit to get the comment into the log. :)“)

Quote: “Editor: PaulBoddie Comment: Suspicious edit resembling spam. Apologies if casino stuff is now actually lwickjr’s focus.” Nope; you`re right. Thanks!

lwickjr 2010-09-06 19:25:09: Gah! I`ve lost my edits TWICE now, once to not being logged in [I haven’t been around so long that I forgot I had never logged in from this particular machine; it’s newish], and once to failing to answer the question that I presume protects the site from unauthorized editing.

Trying a *third* time… Ok, that worked; re-entering the actual information…

Hmm, I note that the DateTime tags below failed to stamp the time when I last edited this page YEARS ago. Odd. I guess I didn’t know how to use them then. ::shrug::

Having recently installed Python 2.7.0, I was browsing through the installation, specifically the site{.backtick} module [there wasn’t a usercustomize{.backtick} module last time I checked, and the new mechinism was interesting; I had been keeping my personal code in the site-packages{.backtick} directory on my personal Windoze machine] when I noticed an error in the definition of the addpackage{.backtick} function.

To whit, if addpackage{.backtick} is ever called with None{.backtick} as the value of known_paths{.backtick} [which it never is], addpackage{.backtick} makes a totaly useless call to _init_pathinfo{.backtick} without saving the results, which I infer should be stored into known_paths{.backtick} [as is done in addsitedir{.backtick}], as addpackage{.backtick} will then go on to throw a KeyError{.backtick} exception by attempting to use the None{.backtick} value still in known_paths{.backtick} as a dictionary-type container. The indicated fix is to copy the known_paths = _init_pathinfo(){.backtick} line in addsitedir{.backtick} over the _init_pathinfo(){.backtick} line in addpackage{.backtick}. I also recommend that the known_paths{.backtick} argument be made to default to None{.backtick} as it does in addsitedir{.backtick}, and appears [from the body of the fuction] to have been intended.

As this bug was discovered through visual inspection and I am not registered at any of the usual Python development sites, would someone please verify this bug and bring it to the attention of the appropriate individuals and/or groups? Thanks!

Whew! Third time`s the charm, I hope! Also, each time brought forth a somewhat-improved version of the above text [‘least I think so ;)“) ].

Attention, please: I am interested in the possibility of de-linting some of the documentation. How do I go about signing up?

FredDrake sez: See the Documentation Development page.

lwickjr 2026-02-14 16:15:21: Done, which I noted on your page some time ago. :)“) [I find myself wondering if anyone found the delinted pages.]

lwickjr 2026-02-14 16:15:21: LionKimbro: “Parnassus”. ;)“)

Welcome to my page.

After reading RealNamesPlease, RealNamesPleaseDiscussion, and OneNamePlease,

I respectfully decline to change my login ID.

This is the ID I use exclusively online, it is derived from my “RL” name, and it is the ID under which I receive my e-mail.

In accordance with OneNamePlease and RealNamesPleaseDiscussion, I conclude that while “lwickjr” is not “exactly” in accordance with RealNamesPlease, it IS “close enough”.

Please, no flames; no offense intended.

If anyone with GOOD American-English spelling skills would care to proofread this page and correct any spelling errors that I can’t find, feel free. I’ve been adding known-correctly-spelled words to the online spelling checker, but I’m a tad unsure of a few of my spellings.

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 mechanics of how to PACKAGE modules [somewhat over-kill, I think, for simple drop-in single-file modules], and nearly nonexistent on how to PUBLISH them.

Could someone [please] write a page on PublishingPythonModules that is understandable by someone with significant *computer* experience but minimal *Internet* experience?