8000 Tags · tclmonster/tohil · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Tags: tclmonster/tohil

Tags

v4.4.2

Toggle v4.4.2's commit message
Bump version for release

v4.4.1

Toggle v4.4.1's commit message

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
Merge pull request flightaware#79 from NasaGeek/properly-indicate-ver…

…sion

Properly bump version in configure.ac

v4.4.0

Toggle v4.4.0's commit message

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
Merge pull request flightaware#78 from NasaGeek/remove-duplicate-dire…

…ctory

Remove unintentionally duplicated docs directory

v4.3.0

Toggle v4.3.0's commit message
release notes for 4.3

v4.2.0

Toggle v4.2.0's commit message
update docs for 4.2 release

v4.1.2

Toggle v4.1.2's commit message
version bump to 4.1.2

v4.1.1

Toggle v4.1.1's commit message
tag 4.1.1

v4.0.3

Toggle v4.0.3's commit message
version bump to 4.0.3

v4.0.2

Toggle v4.0.2's commit message
Revert "tweak test"

This reverts commit 87d7b68.

v4.0.1

Toggle v4.0.1's commit message
Don't error on tohil namespace creation failure

There's a report from FlightAware hitting this error, but it's elusive,
happens only in the rivet apache module and not very often.

But the error can be caused simply by doing a

```tcl
    namespace eval ::tohil {}
    package require tohil
```

That ought to not be an error.  In fact, from high-level Tcl itself there's no
explicit way to cause a namespace-already-exists error because `namespace eval` creates the namespace
if it doesn't exist and is ok with it if it does.

The concern here is that there is some underlying problem with the
multiple tcl interpreter / python subinterpreter stuff.  But in any case
the above shouldn't be a traceback.
0