Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > comp.lang.python > #94830 > unrolled thread

Re: debugging during package development

Started bydieter <dieter@handshake.de>
First post2015-08-01 07:56 +0200
Last post2015-08-01 07:56 +0200
Articles 1 — 1 participant

Back to article view | Back to comp.lang.python

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.


Contents

  Re: debugging during package development dieter <dieter@handshake.de> - 2015-08-01 07:56 +0200

#94830 — Re: debugging during package development

Fromdieter <dieter@handshake.de>
Date2015-08-01 07:56 +0200
SubjectRe: debugging during package development
Message-ID<mailman.1124.1438408608.3674.python-list@python.org>
Seb <spluque@gmail.com> writes:

> It seems too cumbersome to have to update `sys.path` to include the
> development tree of a package (and sub-packages) that's still very
> young.  With lots of debugging to do, the last thing I'd want is to
> worry about the search path.  So I've been searching for better ways to
> work, but I can't seem hit the right keywords and come with all sorts of
> tangentially related stuff.  I'm sure there must be some tool that sets
> up the development environment when the package source is not on
> `sys.path`.  Any advice on this topic would be appreciated.

On "*nix" like systems, you can set "sys.path" via the envvar
"PYTHONPATH".

Note that "sys.path" needs only contain the top level packages - subpackages
are found automatically.

[toc] | [standalone]


Back to top | Article view | comp.lang.python


csiph-web