kgio RubyGem user+dev discussion/patches/pulls/bugs/help
 help / color / mirror / code / Atom feed
From: Eric Wong <>
Subject: [ANN] kgio 2.11.3 - deprecated project moves off deprecated TLD
Date: Wed, 8 Jan 2020 09:29:06 +0000	[thread overview]
Message-ID: <20200108092906.GA23961@dcvr> (raw)

This is a legacy project, do not use it for new projects.  Ruby
2.3 and later should make this obsolete.  kgio provides
non-blocking I/O methods for Ruby without raising exceptions on

Note: I do not recommend using kgio for future applications, Ruby 2.x
has a lot of the functionality of kgio and Ruby 2.3+ has even more.

* homepage:
* public mailing list:
* git clone
* Atom feed
* mail archives:


    Some doc and warning fixes for newer Rubies.

    We're no longer on since it's due
    for expiry and I can't pay extortionists for a .org, so
    s/ for now, and be prepared to move again
    when extortionists move onto the .net TLD.

 use --local to "gem install"
 use dark216 theme for Earth Day 2019
          test: fix warnings with RUBYOPT=-w
          tests: fix unused variable warnings from newer Rubies
          test_connect_fd_leak: do not close socket if non-existent
          test_syssend: avoid warning on cleanup
          build: remove olddoc from the gemspec
          doc: remove private email and outdated gmane archives
          doc: move from to

Again, using kgio for new projects is strongly discouraged.
Use Ruby 2.3+ instead.

                 reply	other threads:[~2020-01-08  9:29 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

  List information:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20200108092906.GA23961@dcvr \ \ \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).