semvec/pypi-packages huggingface dataset:
taup 0.1.1
The TauP Toolkit, via Python
Requires Python: >=3.10
Keywords: seismology, traveltime

# taup_python

Access to the TauP Toolkit from Python via an HTTP server.

The problem is that lots of seismologists like writing Python scripts, but
calling a Java library from Python seems somewhere
between hard and impossible. But interaction doesn't require direct
interoperation. The
basic idea of this solution (or bandaid)
is that this python library will spin up an instance of `taup web`,
and then use that to answer many queries via http, avoiding the startup time of Java.

You will also need to have an instance of the
[TauP Toolkit](https://taup.readthedocs.io/en/latest/)
installed. This can be done manually by
downloading from [Zenodo](https://doi.org/10.5281/zenodo.10794857)
or from [Homebrew](https://brew.sh) via
```
brew tap crotwell/crotwell
brew install taup
```

The Python classes representing each tool's query parameters are based off
off the command line arguments of the same name. For example, this Python
code:

```
with taup.TauPServer() as timeserver:
    timeParams = taup.TimeQuery()
    timeParams.phase(["P", "S"])
    timeParams.model('ak135')
    timeParams.degree(35)
    results = timeParams.calc(timeserver)
```

roughly corresponds to this command line:
```
bin/taup time --ph P,S --mod ak135 --deg 35 --json
```

Note that if you have many calculations in a loop, you want to have the loop
on the inside of the `with taup.TauPServer() as timeserver:` line so that
the server is only started up once.

See `example_times.py` and `example_text.py`  in the examples directory for a couple of more detailed examples.

Documentation available at readthedocs for
[TauP_python](https://taup_python.readthedocs.io/en/latest/)
maya-stubs 0.4.2
Type Annotated Stubs for Autodesk Maya's python APIs
Requires Python: >=3.7

# Maya Stubs

Type Annotated Stubs for Autodesk Maya's python APIs

## Goals

Provide fully type annotated stubs for maya.cmds and OpenMaya 1.0 & 2.0


## Status

Note that is very much in progress and it is unlikely that the stubs will ever be perfect.  
At this point, even if some of the `maya.cmds` annotations are wrong/misleading, I would consider it a better experience than using the stubs from the devkit.
The stubs from OpenMaya 1.0 and 2.0 are very minimal and only have `*args, **kwargs` signatures, which should be pretty close to the devkit stubs.

- 🚧 maya.cmds: In Progress
  - [x] Stubs for all commands.
  - [x] Accurate Arguments signatures for most commands.
    Parsed from the HTML Docs or the synopsys from `cmds.help("command")`
  - [x] Accurate Positional Only Arguments for most command.
  - [x] Accurate Return types on most commands
  - [x] Docstrings.
  - [ ] Accurate Arguments signatures all commands.
  - [ ] Accurate Return types all most commands
- 🚧 OpenMaya 1.0: Incomplete
  - [x] Stubs for all members
  - [ ] Accurate Argument Signatures
  - [ ] Return Types
  - [ ] Docstrings.
- 🚧 OpenMaya 2.0: Incomplete
  - [x] Stubs for all members
  - [ ] Accurate Argument Signatures
  - [ ] Return Types
  - [x] Docstrings.


## Installation

You can get the stubs with one of two ways:

1. Run `pip install maya-stubs` from the python executable used by your IDE.
2. Download them manually from the [Github releases](https://github.com/Muream/maya-stubs/releases) and let your IDE know of their location.

## Notes

### PyCharm maya.cmds completion

PyCharm users may not see code completion for `maya.cmds` as the editor limits code insight features by default on files over 2.5 MB for performance reasons. Currently the cmds stub is over this limit.

This value can be increased in [PyCharm's properties](https://www.jetbrains.com/help/pycharm/file-idea-properties.html), accessible via the `Help > Edit Custom Properties` menu.

Code completion should work after adding the line below to the properties file and restarting PyCharm. This example overrides the default value from 2.5 MB to 10 MB. The value may be customized as needed, but keep in mind it can affect editor performance.

```
idea.max.intellisense.filesize = 10000
```