/dports/astro/py-spacetrack/spacetrack-0.16.0/docs/ |
H A D | changelog.rst | 26 - When ``parse_types`` is used, dates are parsed using an ISO 8601 parser, 123 requires ``install_requires`` in ``setup.py`` to be ordered. 141 - Predicates with the enum type are parsed correctly. Previously, 221 level ``spacetrack`` module, since this would cause an error if
|
/dports/www/p5-HTML-Mason/HTML-Mason-1.59/samples/ |
H A D | dump-request | 20 $r-><a href="#requires">requires</a> = <% $r->requires %><BR> 65 module. Passing an argument will set the method_number, mainly used 132 returned. When called in a list context, a list of parsed key => value 166 of parsed key => value pairs are returned. *NOTE*: you can only ask 260 the Net::Ident module, but the author is planning on adding it soon. 318 <a name="requires"> 319 $r->requires 368 run a perl script. The Apache::Options module provides the constants
|
/dports/sysutils/istio/istio-1.6.7/vendor/github.com/antlr/antlr4/doc/ |
H A D | swift-target.md | 5 ANTLR 4.7.2 requires Swift 4.2. It works on Swift 4.2.1 also. 7 ANTLR 4.7.1 requires Swift 4.0, and does not work on Swift 4.2. (The status of 31 "gnu" message format to have any error messages parsed by Xcode. You may 147 python boot.py --gen-spm-module 198 own and keep the ANTLR-generated parser internal to your module. You 200 the parser directly as part of your own module's API.
|
/dports/www/p5-WebService-Pushover/WebService-Pushover-v1.0.0/ |
H A D | README.mkdn | 27 This module provides a Perl wrapper around the Pushover 30 before you'll be able to do anything with this module. 46 If specified, will be used as a default in any call that requires a user token. 51 If specified, will be used as a default in any call that requires an API token. 189 parsed from the JSON or XML response returned by the Pushover API. 216 This module is free software; you can redistribute it and/or
|
/dports/devel/R-cran-optparse/optparse/ |
H A D | NEWS.md | 39 * Increment ``getopt`` requirement so that empty strings are parsed correctly. 96 to match more closely what the Python module does 98 * Now requires package getopt (>= 1.19) which has also been moved to
|
/dports/devel/luabind/luabind-0.9.1/doc/ |
H A D | docs.rst | 438 .. parsed-literal:: 521 .. parsed-literal:: 583 This requires the first lookup (on ``a``) to return a reference to ``A``, and 660 .. parsed-literal:: 675 .. parsed-literal:: 685 .. parsed-literal:: 714 .. parsed-literal:: 724 .. parsed-literal:: 740 .. parsed-literal:: 1825 C++ to Lua. This policy requires that the parameter type has a copy [all …]
|
/dports/archivers/rpm4/rpm-4.16.1.3/doc/manual/ |
H A D | dependencies | 114 "Requires: " lines then the package requires all packages mentioned on 119 Prereqs are different from requires only in that a PreReq is guaranteed 186 discovered dependencies are parsed exactly as if they were found after 206 %__find_requires /usr/lib/rpm/find-requires 215 interpreter may have its own find-provides and find-requires. To prevent 216 module name collisions between interpreters, module names are enclosed within 227 The output of a per-interpreter find-requires (notice in this example the 242 The per-interpreter automatic module detectors will normally be located in 244 /usr/lib/rpm/{perl,tcl}/find-{provides,requires} 247 /usr/lib/rpm/find-{provides,requires} [all …]
|
/dports/math/ogdf/OGDF/doc/examples/layout/ |
H A D | layout.dox | 15 * reader function for .gml files) any attribute enabled in <tt>GA</tt> will be parsed from 20 * -# A ranking module that will determine the layering of the graph 21 * -# A module that handles the minimization of two-layer crossing 22 * -# The main module that computes the actual graph layout 33 * by an optimization module but instead is specified in advance. 39 * In this case the ranking optimization module has no effect. Note that we also disable the 40 * separate layout and arranging of connected components by the default packing module using 56 * low-level options (requires good knowledge of the algorithm). For this example we will use 75 * it to our needs by passing dynamically allocated module instances. 76 * -# The first module we specify is the ogdf::CrossingMinimizationModule for which we choose [all …]
|
/dports/devel/p5-Date-Manip/Date-Manip-6.85/lib/Date/Manip/ |
H A D | Changes5to6.pod | 45 Date::Manip 5.xx was written as a functional module, not an OO module, 80 Date::Manip module has been broken up from one huge module into a 93 the full Date::Manip module. 270 now parsed in the order they are listed, so the following: 357 to occur in the alternate time zone), parsed results may be different 383 Dates are now parsed according to the spec (though a couple extensions 424 In Date::Manip 6.00, the date will now be parsed as the 3rd day of the 512 parsed a date from the "Less common formats" section, the default time 515 So running a program on Jun 5, 2009 at noon that parsed the following 539 In Date::Manip 5.xx, a parsed delta could be written in the delta style [all …]
|
/dports/net/inlets/inlets-3.0.2/vendor/github.com/prometheus/procfs/ |
H A D | CONTRIBUTING.md | 49 …e_versions__and_more) to manage dependencies on external packages. This requires a working Go envi… 57 go get example.com/some/module/pkg 60 go get example.com/some/module/pkg@vX.Y.Z 80 …and structs should normally be named according to the file(s) being read and parsed. For example, 91 in a directory needs to be parsed, then a `path` string parameter to the parse function can be used…
|
/dports/net/inlets/inlets-3.0.2/vendor/github.com/prometheus/procfs/procfs-0.0.10/ |
H A D | CONTRIBUTING.md | 49 …e_versions__and_more) to manage dependencies on external packages. This requires a working Go envi… 57 go get example.com/some/module/pkg 60 go get example.com/some/module/pkg@vX.Y.Z 80 …and structs should normally be named according to the file(s) being read and parsed. For example, 91 in a directory needs to be parsed, then a `path` string parameter to the parse function can be used…
|
/dports/net-mgmt/bind_exporter/bind_exporter-0.4.0/vendor/github.com/prometheus/procfs/ |
H A D | CONTRIBUTING.md | 49 …e_versions__and_more) to manage dependencies on external packages. This requires a working Go envi… 57 go get example.com/some/module/pkg 60 go get example.com/some/module/pkg@vX.Y.Z 80 …and structs should normally be named according to the file(s) being read and parsed. For example, 91 in a directory needs to be parsed, then a `path` string parameter to the parse function can be used…
|
/dports/net-mgmt/blackbox_exporter/blackbox_exporter-0.17.0/vendor/github.com/prometheus/procfs/ |
H A D | CONTRIBUTING.md | 49 …e_versions__and_more) to manage dependencies on external packages. This requires a working Go envi… 57 go get example.com/some/module/pkg 60 go get example.com/some/module/pkg@vX.Y.Z 80 …and structs should normally be named according to the file(s) being read and parsed. For example, 91 in a directory needs to be parsed, then a `path` string parameter to the parse function can be used…
|
/dports/net/rclone/rclone-1.57.0/vendor/github.com/prometheus/procfs/ |
H A D | CONTRIBUTING.md | 49 …e_versions__and_more) to manage dependencies on external packages. This requires a working Go envi… 57 go get example.com/some/module/pkg 60 go get example.com/some/module/pkg@vX.Y.Z 80 …and structs should normally be named according to the file(s) being read and parsed. For example, 91 in a directory needs to be parsed, then a `path` string parameter to the parse function can be used…
|
/dports/net-mgmt/promscale/promscale-0.6.2/vendor/github.com/prometheus/procfs/ |
H A D | CONTRIBUTING.md | 49 …e_versions__and_more) to manage dependencies on external packages. This requires a working Go envi… 57 go get example.com/some/module/pkg 60 go get example.com/some/module/pkg@vX.Y.Z 80 …and structs should normally be named according to the file(s) being read and parsed. For example, 91 in a directory needs to be parsed, then a `path` string parameter to the parse function can be used…
|
/dports/security/vault/vault-1.8.2/vendor/github.com/prometheus/procfs/ |
H A D | CONTRIBUTING.md | 49 …e_versions__and_more) to manage dependencies on external packages. This requires a working Go envi… 57 go get example.com/some/module/pkg 60 go get example.com/some/module/pkg@vX.Y.Z 80 …and structs should normally be named according to the file(s) being read and parsed. For example, 91 in a directory needs to be parsed, then a `path` string parameter to the parse function can be used…
|
/dports/databases/redis_exporter/redis_exporter-1.33.0/vendor/github.com/prometheus/procfs/ |
H A D | CONTRIBUTING.md | 49 …e_versions__and_more) to manage dependencies on external packages. This requires a working Go envi… 57 go get example.com/some/module/pkg 60 go get example.com/some/module/pkg@vX.Y.Z 80 …and structs should normally be named according to the file(s) being read and parsed. For example, 91 in a directory needs to be parsed, then a `path` string parameter to the parse function can be used…
|
/dports/www/gitlab-workhorse/gitlab-foss-0a901d60f8ae4a60c04ae82e6e9c3a03e9321417/workhorse/vendor/github.com/prometheus/procfs/ |
H A D | CONTRIBUTING.md | 49 …e_versions__and_more) to manage dependencies on external packages. This requires a working Go envi… 57 go get example.com/some/module/pkg 60 go get example.com/some/module/pkg@vX.Y.Z 80 …and structs should normally be named according to the file(s) being read and parsed. For example, 91 in a directory needs to be parsed, then a `path` string parameter to the parse function can be used…
|
/dports/sysutils/helmfile/vault-f6547fa8e820/vendor/github.com/prometheus/procfs/ |
H A D | CONTRIBUTING.md | 49 …e_versions__and_more) to manage dependencies on external packages. This requires a working Go envi… 57 go get example.com/some/module/pkg 60 go get example.com/some/module/pkg@vX.Y.Z 80 …and structs should normally be named according to the file(s) being read and parsed. For example, 91 in a directory needs to be parsed, then a `path` string parameter to the parse function can be used…
|
/dports/security/snowflake-tor/snowflake-ead5a960d7fa19dc890ccbfc0765c5ab6629eaa9/vendor/github.com/prometheus/procfs/ |
H A D | CONTRIBUTING.md | 49 …e_versions__and_more) to manage dependencies on external packages. This requires a working Go envi… 57 go get example.com/some/module/pkg 60 go get example.com/some/module/pkg@vX.Y.Z 80 …and structs should normally be named according to the file(s) being read and parsed. For example, 91 in a directory needs to be parsed, then a `path` string parameter to the parse function can be used…
|
/dports/net-im/dendrite/dendrite-0.5.1/vendor/github.com/prometheus/procfs/ |
H A D | CONTRIBUTING.md | 49 …e_versions__and_more) to manage dependencies on external packages. This requires a working Go envi… 57 go get example.com/some/module/pkg 60 go get example.com/some/module/pkg@vX.Y.Z 80 …and structs should normally be named according to the file(s) being read and parsed. For example, 91 in a directory needs to be parsed, then a `path` string parameter to the parse function can be used…
|
/dports/www/gitlab-pages/gitlab-pages-f8512edbec4ec83b426c8ca2dda467de424685e4/vendor/github.com/prometheus/procfs/ |
H A D | CONTRIBUTING.md | 49 …e_versions__and_more) to manage dependencies on external packages. This requires a working Go envi… 57 go get example.com/some/module/pkg 60 go get example.com/some/module/pkg@vX.Y.Z 80 …and structs should normally be named according to the file(s) being read and parsed. For example, 91 in a directory needs to be parsed, then a `path` string parameter to the parse function can be used…
|
/dports/net-im/dendrite/dendrite-0.5.1/vendor/github.com/containerd/containerd/vendor/github.com/prometheus/procfs/ |
H A D | CONTRIBUTING.md | 49 …e_versions__and_more) to manage dependencies on external packages. This requires a working Go envi… 57 go get example.com/some/module/pkg 60 go get example.com/some/module/pkg@vX.Y.Z 80 …and structs should normally be named according to the file(s) being read and parsed. For example, 91 in a directory needs to be parsed, then a `path` string parameter to the parse function can be used…
|
/dports/dns/blocky/blocky-0.17/vendor/github.com/prometheus/procfs/ |
H A D | CONTRIBUTING.md | 49 …e_versions__and_more) to manage dependencies on external packages. This requires a working Go envi… 57 go get example.com/some/module/pkg 60 go get example.com/some/module/pkg@vX.Y.Z 80 …and structs should normally be named according to the file(s) being read and parsed. For example, 91 in a directory needs to be parsed, then a `path` string parameter to the parse function can be used…
|
/dports/sysutils/consul/consul-1.10.3/vendor/github.com/prometheus/procfs/ |
H A D | CONTRIBUTING.md | 49 …e_versions__and_more) to manage dependencies on external packages. This requires a working Go envi… 57 go get example.com/some/module/pkg 60 go get example.com/some/module/pkg@vX.Y.Z 80 …and structs should normally be named according to the file(s) being read and parsed. For example, 91 in a directory needs to be parsed, then a `path` string parameter to the parse function can be used…
|