seen from Malaysia
seen from China
seen from Singapore
seen from Philippines
seen from United States
seen from Sweden
seen from Hong Kong SAR China
seen from United Kingdom
seen from Italy
seen from China
seen from Italy
seen from United States
seen from Maldives
seen from Sweden
seen from Italy
seen from Latvia
seen from Malaysia
seen from United States
seen from Latvia
seen from United States
Create and distribute your python package
This is a quick guide for create and generate distribution package of your python project so that others can install, import and use in their projects.
Prerequisites:
You will need the following tools installed in your computer:
Python (2.x/3.x)
Pip
API key for uploading your package to distribution platform, such as test.pypi.org.
After install python, you can install pip by using:
cu…
View On WordPress
python setuptools 문제 ㎒
python setuptools 문제 ㎒
python setuptools 문제 python setuptools 문제 설치파일입니다. 아래 첨부파일을 클릭하셔서 다운로드 받으세요~ python setuptools 문제 첨부파일 setuptools-0.6c11.tar.gz (250.84 KB) 운영체제 : WinXP/WinVista/Win7/Win8/Win10 지원언어 : 한글 언인스톨여부 : 지원함 #setuptools
View On WordPress
Python: SWIG で C 言語拡張モジュールを作ってみる
SWIG は C/C++ を使ったライブラリのスクリプト言語のバインディングを作りやすくするためのツール。 本来は Python/C API を使って自分でチマチマ書かなきゃいけない C/C++ とスクリプト言語のグルー部分を自動生成してくれる。 まずは SWIG をインストールする。 今回使った環境は OS X なので Homebrew から。
$ brew install swig
次に C/C++ のソースファイルを用意していく。 今回はシンプルに C 言語で、呼び出す関数もごく単純なものにした。 以下はヘッダファイル。 greet.h という名前で保存しておく。
void greet(void);
次にソースファイル。 greet.c という名前で保存する。
#include <stdio.h> void greet(void) { printf("Hello, World!\n"); }
次に SWIG の設定ファイルを用意する。 使用するヘッダや、バインディングを作成する関数を記述する。 greet.i という名前で保存する。
%module greet %{ #include "greet.h" #include <stdio.h> %} extern void greet(void);
設定ファイルを元に SWIG でグルーコードを自動生成する。
$ swig -python greet.i
ここまでで、以下のファイルが準備できているはず。
$ ls greet.c greet.h greet.i greet.py greet_wrap.c
早速ビルドして試してみよう。
$ gcc -c greet.c $ gcc -c greet_wrap.c -I /usr/include/python2.7 $ gcc -shared greet.o greet_wrap.o -o _greet.so -l python
上手いこと共有ライブラリができたら成功。
$ file _greet.so _greet.so: Mach-O 64-bit dynamically linked shared library x86_64
同じディレクトリで Python の REPL を起動して動作確認してみる。
$ python >>> import greet >>> greet.greet() Hello, World!
ばっちり。 これだけだと使い勝手がイマイチなんで、次は setup.py を書いてパッケージングできるようにする。
#!/usr/bin/env python # -*- coding: utf-8 -*- from setuptools import setup from setuptools import Extension ext_greet = Extension( '_greet', sources=['greet_wrap.c', 'greet.c'], ) if __name__ == '__main__': setup( name='greet', version='0.0.1', description='SWIG Example package', ext_modules=[ext_greet], py_modules=['greet'], )
Setuptools 経由で拡張モジュールをビルドしてみる。
$ python setup.py build_ext $ ls build/lib.macosx-10.10-x86_64-2.7 _greet.so
よさげ。 インストールして動作確認してみる。
$ python setup.py install $ pip list | grep greet greet (0.0.1)
上手く動くかな？
$ python >>> import greet >>> greet.greet() Hello, World!
今度もばっちりだね。 めでたしめでたし。
Fixed What's the proper way to install pip, virtualenv, and distribute for Python? #dev #it #asnwer
Fixed What's the proper way to install pip, virtualenv, and distribute for Python? #dev #it #asnwer
What’s the proper way to install pip, virtualenv, and distribute for Python? Short Question
What is the proper way to install pip, virtualenv, and distribute?
Background
In my answer to SO question 4314376, I recommended using ez_setup so that you could then install pip and virtualenv as follows:
curl -O http://peak.telecommunity.com/dist/ez_setup.pysudo python ez_setup.py sudo easy_install pip…
View On WordPress
Fixed No module named pkg_resources #dev #it #asnwer
Fixed No module named pkg_resources #dev #it #asnwer
No module named pkg_resources
I’m deploying a Django app to a dev server and am hitting this error when i run pip install requirements.txt:
Traceback (most recent call last): File "/var/www/mydir/virtualenvs/dev/bin/pip", line 5, in <module> from pkg_resources import load_entry_point ImportError: No module named pkg_resources
pkg_resources appears to be distributed with setuptools. Initially I…
View On WordPress
Fixed Differences between distribute, distutils, setuptools and distutils2? #dev #it #asnwer
Fixed Differences between distribute, distutils, setuptools and distutils2? #dev #it #asnwer
Differences between distribute, distutils, setuptools and distutils2? The Situation
I’m trying to port an open-source library to Python 3. (SymPy, if anyone is wondering.)
So, I need to run 2to3 automatically when building for Python 3. To do that, I need to use distribute. Therefore, I need to port the current system, which (according to the doctest) is distutils.
The Problem
Unfortunately, I’m…
View On WordPress
Fixed How do I remove packages installed with Python's easy_install? #dev #it #asnwer
Fixed How do I remove packages installed with Python's easy_install? #dev #it #asnwer
How do I remove packages installed with Python’s easy_install?
Python’s easy_install makes installing new packages extremely convenient. However, as far as I can tell, it doesn’t implement the other common features of a dependency manager – listing and removing installed packages.
What is the best way of finding out what’s installed, and what is the preferred way of removing installed packages?…
View On WordPress
Fixed Why use pip over easy_install? #dev #it #asnwer
Fixed Why use pip over easy_install? #dev #it #asnwer
Why use pip over easy_install?
A tweet reads:
Don’t use easy_install, unless you like stabbing yourself in the face. Use pip.
Why use pip over easy_install? Doesn’t the fault lie with PyPI and package authors mostly? If an author uploads crap source tarball (eg: missing files, no setup.py) to PyPI, then both pip and easy_install will fail. Other than cosmetic differences, why do Python people…
View On WordPress
