Nox Sessions Sample Clauses

Nox Sessions. ‌ The following sessions execute unit tests and regression tests: unit Runs the unit tests. regression Runs integration/regression tests. Each of these tests render a tiny document (often a single page) focusing on a specific feature, which means they also execute quickly. Their PDF output is compared to a reference PDF that is known to be good. This requires ImageMagick and either MuPDF’s mutool or poppler’s pdftoppm to be available from the search path. These sessions are parametrized in order to run the tests against both the source and wheel distributions, and against all supported Python versions. Executing e.g. nox --session unit will run all of these combinations. Run nox --list to display these. You can run a single session like this: nox --session "<session name>". unit_sphinx, regression_docutils, regression_sphinx These are variations on the unit and regression sessions that run the (relevant) tests against several versions of the principal rinohtype dependencies, docutils and Sphinx (respecting version constraints specified in pyproject.toml). Note that for development purposes, it generally suffices to run the default set of sessions. Section 9.3 will run all session to catch regressions. The other environments run checks, build documentation and build “binary” distributions for Mac and Windows: check Performs basic checks; just poetry check at this point. check_docs Perform checks on the documentation source files using doc8 and sphinx-doctest. restview can be useful when fixing syntax errors in README.rst, CHANGES.rst, … build_docs Build the rinohtype documentation using Sphinx, both in HTML and PDF formats. xxxxxx (not maintained, broken?) Build a stand-alone macOS application bundle using briefcase. This task can only be run on macOS. wininst (not maintained, broken?) Build a stand-alone rinohtype installer for the Windows platform with the help of pynsist. This task also can be run on other platforms than Windows. Customization settings for doc8 and pytest are stored in setup.cfg.
Sample 1
AutoNDA by SimpleDocs

Related to Nox Sessions

  • UNDERGROUND LOCATIONS Prior to the Company commencing any work the Customer must advise the Company of the precise location of all underground services on the site and clearly xxxx the location. The underground mains and services the Customer must identify include, but are not limited to, telephone cables, fibre optic cables, electrical services, gas services, sewer services, pumping services, sewer connections, sewer sludge mains, water mains, irrigations pipes, oil pumping mains and any other services that may be on site. Whilst the Company will take all care to avoid damage to any underground services the Customer agrees to indemnify the Company in respect of all any liability claims, loss, damage, cost and fines as a result of damage to services not precisely located and notified pursuant to this clause.

  • Prohibition Against Selecting and Installing Products Containing Hazardous Materials The Contractor shall not select, install or otherwise incorporate any products or materials containing Hazardous Materials within the boundaries of the Site. Should the Contractor or any Subcontractors have knowledge that, or believe that, an item, component, material, substance, or accessory within a product or assembly selected by the Contractor or any Subcontractor may contain Hazardous Materials it is the Contractor’s responsibility to secure a written certification from the manufacturer of any suspected material which identifies the specific Hazardous Material(s) contained, together with the Material Safety Data Sheets (MSDS) for such materials which shall be submitted to the Owner and Design Professional.

  • Developer’s Attachment Facilities (“DAF”). Developer shall, at its expense, design, procure, construct, own and install the DAF, as set forth in Appendix A hereto.

  • Underground Facilities All underground pipelines, conduits, ducts, cables, wires, manholes, vaults, tanks, tunnels, or other such facilities or attachments, and any encasements containing such facilities, including without limitation those that convey electricity, gases, steam, liquid petroleum products, telephone or other communications, cable television, water, wastewater, storm water, other liquids or chemicals, or traffic or other control systems.

  • Access Toll Connecting Trunk Group Architecture 9.2.1 If CBB chooses to subtend a Verizon access Tandem, CBB’s NPA/NXX must be assigned by CBB to subtend the same Verizon access Tandem that a Verizon NPA/NXX serving the same Rate Center Area subtends as identified in the LERG.

  • Technical Specifications The Technical Specifications furnished on the CD are intended to establish the standards for quality, performance and technical requirements for all labor, workmanship, material, methods and equipment necessary to complete the Work. When specifications and drawings are provided or referenced by the County, these are to be considered part of the Scope of Work, and to be specifically documented in the Detailed Scope of Work. For convenience, the County supplied specifications, if any, and the Technical Specifications furnished on the CD.

  • Dangerous Materials Tenant shall not keep or have on the Premises any article or thing of a dangerous, flammable, or explosive character that might substantially increase the danger of fire on the Premises, or that might be considered hazardous by a responsible insurance company, unless the prior written consent of Landlord is obtained and proof of adequate insurance protection is provided by Tenant to Landlord.

  • ROAD DIMENSIONS Purchaser shall perform road work in accordance with the dimensions shown on the TYPICAL SECTION SHEET and the specifications within this road plan.

  • Service Locations X.X. Xxxxxx maintains various operational/service centers and locations through the United States and foreign jurisdictions. The services provided under this Agreement may be provided from one or more such locations. X.X. Xxxxxx may change the operational/service centers and locations as it deems necessary or appropriate for its business concerns.

  • Commingling of Resold Services with Unbundled Network Elements and Combinations of Unbundled Network Elements 6.7.1 To the extent it is Technically Feasible and pursuant to the terms of Section 9.1, CLEC may Commingle Telecommunications Services purchased on a resale basis with an Unbundled Network Element or combination of Unbundled Network Elements.

Time is Money Join Law Insider Premium to draft better contracts faster.