🤝 synchronize the organisational meta data

This commit is contained in:
chfw 2020-06-08 22:46:03 +01:00
parent 711dc8d1b5
commit 8e39448d98
8 changed files with 102 additions and 57 deletions

View File

@ -2,6 +2,8 @@ With your PR, here is a check list:
- [ ] Has Test cases written
- [ ] Has all code lines tested
- [ ] Has `make format` been run?
- [ ] Has `moban` been run?
- [ ] Passes all Travis CI builds
- [ ] Has fair amount of documentation if your change is complex
- [ ] run 'make format' so as to confirm the pyexcel organisation's coding style

46
.gitignore vendored
View File

@ -25,7 +25,6 @@ parts/
sdist/
var/
wheels/
pip-wheel-metadata/
share/python-wheels/
*.egg-info/
.installed.cfg
@ -52,8 +51,10 @@ htmlcov/
nosetests.xml
coverage.xml
*.cover
*.py,cover
.hypothesis/
.pytest_cache/
cover/
# Translations
*.mo
@ -63,6 +64,7 @@ coverage.xml
*.log
local_settings.py
db.sqlite3
db.sqlite3-journal
# Flask stuff:
instance/
@ -75,6 +77,7 @@ instance/
docs/_build/
# PyBuilder
.pybuilder/
target/
# Jupyter Notebook
@ -85,17 +88,23 @@ profile_default/
ipython_config.py
# pyenv
.python-version
# For a library or package, you might want to ignore these files since the code is
# intended to run in multiple environments; otherwise, check them in:
# .python-version
# pipenv
# According to pypa/pipenv#598, it is recommended to include Pipfile.lock in version control.
# However, in case of collaboration, if having platform-specific dependencies or dependencies
# having no cross-platform support, pipenv may install dependencies that dont work, or not
# having no cross-platform support, pipenv may install dependencies that don't work, or not
# install all needed dependencies.
#Pipfile.lock
# celery beat schedule file
# PEP 582; used by e.g. github.com/David-OConnor/pyflow
__pypackages__/
# Celery stuff
celerybeat-schedule
celerybeat.pid
# SageMath parsed files
*.sage.py
@ -127,6 +136,12 @@ dmypy.json
# Pyre type checker
.pyre/
# pytype static type analyzer
.pytype/
# Cython debug symbols
cython_debug/
# VirtualEnv rules
# Virtualenv
# http://iamzed.com/2009/05/07/a-primer-on-virtualenv/
@ -159,6 +174,7 @@ pip-selfcheck.json
# Windows rules
# Windows thumbnail cache files
Thumbs.db
Thumbs.db:encryptable
ehthumbs.db
ehthumbs_vista.db
@ -264,6 +280,7 @@ flycheck_*.el
# Vim rules
# Swap
[._]*.s[a-v][a-z]
!*.svg # comment out if you don't need vector files
[._]*.sw[a-p]
[._]s[a-rt-v][a-z]
[._]ss[a-gi-z]
@ -271,6 +288,7 @@ flycheck_*.el
# Session
Session.vim
Sessionx.vim
# Temporary
.netrwhist
@ -281,7 +299,7 @@ tags
[._]*.un~
# JetBrains rules
# Covers JetBrains IDEs: IntelliJ, RubyMine, PhpStorm, AppCode, PyCharm, CLion, Android Studio and WebStorm
# Covers JetBrains IDEs: IntelliJ, RubyMine, PhpStorm, AppCode, PyCharm, CLion, Android Studio, WebStorm and Rider
# Reference: https://intellij-support.jetbrains.com/hc/en-us/articles/206544839
# User-specific stuff
@ -311,9 +329,14 @@ tags
# When using Gradle or Maven with auto-import, you should exclude module files,
# since they will be recreated, and may cause churn. Uncomment if using
# auto-import.
# .idea/artifacts
# .idea/compiler.xml
# .idea/jarRepositories.xml
# .idea/modules.xml
# .idea/*.iml
# .idea/modules
# *.iml
# *.ipr
# CMake
cmake-build-*/
@ -363,6 +386,7 @@ fabric.properties
# SFTP configuration file
sftp-config.json
sftp-config-alt*.json
# Package control specific files
Package Control.last-run
@ -400,6 +424,10 @@ tmtags
!.vscode/tasks.json
!.vscode/launch.json
!.vscode/extensions.json
*.code-workspace
# Local History for Visual Studio Code
.history/
# Xcode rules
# Xcode
@ -426,6 +454,9 @@ DerivedData/
*.perspectivev3
!default.perspectivev3
## Gcc Patch
/*.gcno
# Eclipse rules
.metadata
bin/
@ -477,12 +508,17 @@ local.properties
# Annotation Processing
.apt_generated/
.apt_generated_test/
# Scala IDE specific (Scala & Java development for Eclipse)
.cache-main
.scala_dependencies
.worksheet
# Uncomment this line if you wish to ignore the project description file.
# Typically, this file would be tracked if it contains build/dependency configurations:
#.project
# TortoiseGit rules
# Project-level settings
/.tgitconfig

View File

@ -15,33 +15,22 @@ stages:
- moban
- test
.disable_global: &disable_global
addons: false
cache: false
env: {}
python: false
before_install: false
install: false
before_script: false
script: false
after_success: false
after_failure: false
before_deploy: false
deploy: false
.lint: &lint
<<: *disable_global
git:
submodules: false
python: 3.6
env:
- MINREQ=0
stage: lint
script: make lint
.moban: &moban
<<: *disable_global
python: 3.6
env:
- MINREQ=0
stage: moban
install: pip install moban>=0.0.4
install: pip install moban>=0.0.4 gitfs2 pypifs
script:
- moban
- git diff --exit-code

View File

@ -1,4 +1,4 @@
Copyright (c) 2015-2019 by Onni Software Ltd. and its contributors
Copyright (c) 2015-2020 by Onni Software Ltd. and its contributors
All rights reserved.
Redistribution and use in source and binary forms of the software as well

View File

@ -5,6 +5,9 @@ pyexcel-ods - Let you focus on data, instead of ods format
.. image:: https://raw.githubusercontent.com/pyexcel/pyexcel.github.io/master/images/patreon.png
:target: https://www.patreon.com/chfw
.. image:: https://cdn.rawgit.com/sindresorhus/awesome/d7305f38d29fed78fa85652e3a63e154dd8e8829/media/badge.svg
:target: https://awesome-python.com/#specific-formats-processing
.. image:: https://travis-ci.org/pyexcel/pyexcel-ods.svg?branch=master
:target: http://travis-ci.org/pyexcel/pyexcel-ods
@ -30,6 +33,24 @@ ods format using python 2.6 and python 2.7. You are likely to use it with
depends on ezodf and lxml. `pyexcel-odsr <https://github.com/pyexcel/pyexcel-odsr>`_
is the other sister library that has no external dependency but do ods reading only
Support the project
================================================================================
If your company has embedded pyexcel and its components into a revenue generating
product, please support me on github, `patreon <https://www.patreon.com/bePatron?u=5537627>`_
or `bounty source <https://salt.bountysource.com/teams/chfw-pyexcel>`_ to maintain
the project and develop it further.
If you are an individual, you are welcome to support me too and for however long
you feel like. As my backer, you will receive
`early access to pyexcel related contents <https://www.patreon.com/pyexcel/posts>`_.
And your issues will get prioritized if you would like to become my patreon as `pyexcel pro user`.
With your financial support, I will be able to invest
a little bit more time in coding, documentation and writing interesting posts.
Known constraints
==================
@ -54,24 +75,6 @@ or clone it and install it:
$ cd pyexcel-ods
$ python setup.py install
Support the project
================================================================================
If your company has embedded pyexcel and its components into a revenue generating
product, please support me on `github <https://github.com/sponsors/chfw>`_, `patreon <https://www.patreon.com/bePatron?u=5537627>`_
or `bounty source <https://salt.bountysource.com/teams/chfw-pyexcel>`_ to maintain
the project and develop it further.
If you are an individual, you are welcome to support me too and for however long
you feel like. As my backer, you will receive
`early access to pyexcel related contents <https://www.patreon.com/pyexcel/posts>`_.
And your issues will get prioritized if you would like to become my patreon as `pyexcel pro user`.
With your financial support, I will be able to invest
a little bit more time in coding, documentation and writing interesting posts.
Usage
================================================================================
@ -353,18 +356,27 @@ On Windows systems, please issue this command::
> test.bat
How to update test environment and update documentation
Before you commit
------------------------------
Please run::
$ make format
so as to beautify your code otherwise travis-ci may fail your unit test.
And make sure you would have run moban command
---------------------------------------------------------
Additional steps are required:
#. pip install moban
#. make your changes in `.moban.d` directory, then issue command `moban`
#. moban
What is pyexcel-commons
---------------------------------
Many information that are shared across pyexcel projects, such as: this developer guide, license info, etc. are stored in `pyexcel-commons` project.
otherwise travis-ci may also fail your unit test.
What is .moban.d
---------------------------------

View File

@ -22,7 +22,7 @@ DESCRIPTION = (
# -- Project information -----------------------------------------------------
project = 'pyexcel-ods'
copyright = '2015-2019 Onni Software Ltd.'
copyright = '2015-2020 Onni Software Ltd.'
author = 'C.W.'
# The short X.Y version
version = '0.5.6'

View File

@ -4,9 +4,11 @@ nick_name: ods
version: 0.5.6
current_version: 0.5.6
release: 0.5.6
copyright_year: 2015-2019
copyright_year: 2015-2020
file_type: ods
dependencies:
- pyexcel-io>=0.5.16
- odfpy>=1.3.5
description: A wrapper library to read, manipulate and write data in ods format
python_requires: ">=3.6"
min_python_version: "3.6"

View File

@ -1,8 +1,11 @@
#!/usr/bin/env python3
"""
Template by pypi-mobans
"""
import os
import sys
# Template by pypi-mobans
import codecs
import locale
import platform
@ -10,6 +13,7 @@ from shutil import rmtree
from setuptools import Command, setup, find_packages
# Work around mbcs bug in distutils.
# http://bugs.python.org/issue10945
# This work around is only if a project supports Python < 3.4
@ -42,27 +46,26 @@ CLASSIFIERS = [
"Topic :: Software Development :: Libraries",
"Programming Language :: Python",
"Intended Audience :: Developers",
"Programming Language :: Python :: 2.6",
"Programming Language :: Python :: 2.7",
"Programming Language :: Python :: 3.3",
"Programming Language :: Python :: 3.4",
"Programming Language :: Python :: 3.5",
"Programming Language :: Python :: 3 :: Only",
"Programming Language :: Python :: 3.6",
"Programming Language :: Python :: 3.7",
"Programming Language :: Python :: 3.8",
]
PYTHON_REQUIRES = ">=3.6"
INSTALL_REQUIRES = [
"pyexcel-io>=0.5.16",
"odfpy>=1.3.5",
]
SETUP_COMMANDS = {}
PACKAGES = find_packages(exclude=["ez_setup", "examples", "tests"])
PACKAGES = find_packages(exclude=["ez_setup", "examples", "tests", "tests.*"])
EXTRAS_REQUIRE = {
}
# You do not need to read beyond this line
@ -188,6 +191,7 @@ if __name__ == "__main__":
long_description=read_files(*FILES),
license=LICENSE,
keywords=KEYWORDS,
python_requires=PYTHON_REQUIRES,
extras_require=EXTRAS_REQUIRE,
tests_require=["nose"],
install_requires=INSTALL_REQUIRES,