Home  >  Article  >  Backend Development  >  5 recommended articles about packaging and publishing

5 recommended articles about packaging and publishing

黄舟
黄舟Original
2017-06-14 10:53:341660browse

Preface Yesterday I packaged my VASP file processing library and uploaded it to PyPI. Now you can install VASPy directly through pip and easy_install (at the same time, children who use VASP to do computational chemistry are welcome to star and participate), VASPy GotHub address: https://github.com/PytLab/VASPyVASPy’s PyPI address: https://pypi.python.org/pypi/vaspy/ Since my memory is really bad, I am afraid that I will forget it after a long time. So here I will strike while the iron is hot and use my own VASPy program as an example to summarize the packaging and uploading of Python. VASPy package file structure First write and paste the entire file structure of the VASPy package. The following content will be explained using this example: VASPy/ ├── LICENSE ├── MANIFEST ├── MANIFEST.in ├── README.rst ├── require

1. Detailed explanation of how to package and publish Python modules

5 recommended articles about packaging and publishing

Introduction: In this article, we will learn the basic knowledge and methods of packaging and publishing your Python module. It is very simple and practical. So don’t waste time, let’s get started!

2. javascript - Begging the master: How to best cooperate with the front and back ends

Introduction: Produce dynamic php and jsp pages with data. The front-end and back-end packaging and release are completely independent. The advantage of this is the performance of the front-end layer. The data is completely controlled by the front-end. Any problems can be solved independently by the front-end and packaged and released separately. The packaging and release of front-end and back-end are completely independent. The meaning and understanding of this game

3. Use Phar to package and release PHP programs

Introduction: Using Phar Let’s package and publish PHP programs. Simply put, Phar transplants the jar concept from the Java world to the PHP world. Phar can package a set of PHP files, and can also create a stub (or bootstrap loader) that is executed by default. Phar can choose whether to compress it, and the gzip and bzip2 formats are optional. The following is an example of how to create and use Phar: Assume that our project name is user and contains three files

4. MongoDB C++ Driver is independently forked

Introduction: The MongoDB c++ driver version 2.6 was previously extracted from the server code, packaged and released. Now it has been independently forked and this version will be officially maintained in the future. Comment: If you have used the c++ driver code before, it is recommended to use this independent version. More Original address: MongoDB C++ Driver has been independently forked. Thanks to the original author for sharing.

5. Ask a question about the packaging and release of the Winform+Access project

Introduction: Description: The access database contains In a folder within the project. Originally I wrote a relative path, but after debugging to add the membership function, I found that the data was added successfully. When I opened Access, there was no data in it. Now I panicked. After repeated checks, I found that there was no error in the program, so I finally couldn't help but search online. Others say it is written in an absolute way

[Related Q&A recommendations]:

javascript - Begging the master: How to best cooperate with the front and back ends

javascript - vue-cli's official webpack template resource loading problem

node.js - electon packaging and publishing problem

javascript - How does webpack publish individual .css files to other folders?

ios - bundle id is occupied by a free account

The above is the detailed content of 5 recommended articles about packaging and publishing. For more information, please follow other related articles on the PHP Chinese website!

Statement:
The content of this article is voluntarily contributed by netizens, and the copyright belongs to the original author. This site does not assume corresponding legal responsibility. If you find any content suspected of plagiarism or infringement, please contact admin@php.cn