mirror of
https://github.com/tokio-rs/tokio.git
synced 2026-08-29 00:00:11 +02:00
chore: prepare for v0.2.0-alpha.1 release (#1410)
This commit is contained in:
committed by
Carl Lerche
parent
2e69f2a7fd
commit
50e5d401df
@@ -1,3 +1,8 @@
|
||||
# 0.3.0-alpha.1 (August 8, 2019)
|
||||
|
||||
### Changed
|
||||
- Switch to `async`, `await`, and `std::future`.
|
||||
|
||||
## 0.2.4 - 2019-06-21
|
||||
### Fixed
|
||||
* Proccesses "leaked" via `Child::forget` now reaped rather than left as zombies
|
||||
|
||||
+12
-10
@@ -1,11 +1,13 @@
|
||||
[package]
|
||||
name = "tokio-process"
|
||||
# When releasing to crates.io:
|
||||
# - Remove path dependencies
|
||||
# - Update html_root_url.
|
||||
# - Update doc url
|
||||
# - Cargo.toml
|
||||
# - Update CHANGELOG.md.
|
||||
# - Create "X.Y.Z" git tag.
|
||||
version = "0.3.0"
|
||||
publish = false
|
||||
# - Create "v0.1.x" git tag.
|
||||
version = "0.3.0-alpha.1"
|
||||
edition = "2018"
|
||||
authors = ["Tokio Contributors <[email protected]>"]
|
||||
license = "MIT"
|
||||
@@ -18,21 +20,21 @@ An implementation of an asynchronous process management backed futures.
|
||||
categories = ["asynchronous"]
|
||||
|
||||
[dependencies]
|
||||
futures-core-preview = { version = "0.3.0-alpha.17" }
|
||||
futures-util-preview = { version = "0.3.0-alpha.17" }
|
||||
futures-core-preview = "=0.3.0-alpha.17"
|
||||
futures-util-preview = "=0.3.0-alpha.17"
|
||||
log = "0.4"
|
||||
tokio-io = { version = "0.2.0", path = "../tokio-io", features = ["util"] }
|
||||
tokio-reactor = { version = "0.2.0", path = "../tokio-reactor" }
|
||||
tokio-io = { version = "=0.2.0-alpha.1", path = "../tokio-io", features = ["util"] }
|
||||
tokio-reactor = { version = "=0.2.0-alpha.1", path = "../tokio-reactor" }
|
||||
|
||||
[dev-dependencies.tokio]
|
||||
version = "0.2.0"
|
||||
version = "=0.2.0-alpha.1"
|
||||
path = "../tokio"
|
||||
default-features = false
|
||||
features = ["codec", "rt-full"]
|
||||
|
||||
[target.'cfg(windows)'.dependencies]
|
||||
mio-named-pipes = "0.1"
|
||||
tokio-sync = { version = "0.2.0", path = "../tokio-sync" }
|
||||
tokio-sync = { version = "=0.2.0-alpha.1", path = "../tokio-sync" }
|
||||
|
||||
[target.'cfg(windows)'.dependencies.winapi]
|
||||
version = "0.3"
|
||||
@@ -53,4 +55,4 @@ lazy_static = "1.3"
|
||||
libc = "0.2"
|
||||
log = "0.4"
|
||||
mio = "0.6.5"
|
||||
tokio-signal = { version = "0.3.0", path = "../tokio-signal" }
|
||||
tokio-signal = { version = "=0.3.0-alpha.1", path = "../tokio-signal" }
|
||||
|
||||
@@ -2,41 +2,6 @@
|
||||
|
||||
An implementation of process management for Tokio
|
||||
|
||||
[Documentation](https://docs.rs/tokio-process/0.2.4/tokio_process)
|
||||
|
||||
## Usage
|
||||
|
||||
First, add this to your `Cargo.toml`:
|
||||
|
||||
```toml
|
||||
[dependencies]
|
||||
tokio-process = "0.2"
|
||||
```
|
||||
|
||||
Next you can use this in conjunction with the `tokio` and `futures` crates:
|
||||
|
||||
```rust,no_run
|
||||
use std::process::Command;
|
||||
|
||||
use futures::Future;
|
||||
use tokio_process::CommandExt;
|
||||
|
||||
fn main() {
|
||||
// Use the standard library's `Command` type to build a process and
|
||||
// then execute it via the `CommandExt` trait.
|
||||
let child = Command::new("echo").arg("hello").arg("world").spawn_async();
|
||||
|
||||
// Make sure our child succeeded in spawning and process the result
|
||||
let future = child
|
||||
.expect("failed to spawn")
|
||||
.map(|status| println!("exit status: {}", status))
|
||||
.map_err(|e| panic!("failed to wait for exit: {}", e));
|
||||
|
||||
// Send the future to the tokio runtime for execution
|
||||
tokio::run(future)
|
||||
}
|
||||
```
|
||||
|
||||
## License
|
||||
|
||||
This project is licensed under the [MIT license](./LICENSE).
|
||||
|
||||
@@ -1,3 +1,5 @@
|
||||
#![doc(html_root_url = "https://docs.rs/tokio-process/0.3.0-alpha.1")]
|
||||
|
||||
//! An implementation of asynchronous process management for Tokio.
|
||||
//!
|
||||
//! This crate provides a `CommandExt` trait to enhance the functionality of the
|
||||
|
||||
Reference in New Issue
Block a user