in Forwarded: line.
* add newline to override file.
* change name to python-swisseph
* rebuild pydoc from source.
* create a documentation package
* create a python3 version of this extension
- using recommendations in:
- http://wiki.debian.org/Python/LibraryStyleGuide
Regards,
Paul
?
--
Paul Elliott 1(512)837-1096
pelli...@blackpatchpanel.com PMB 181, 11900 Metric Blvd Suite J
http://www.free.blackpatchpanel.com/pme/ Austin TX 78758-3117
signature.asc
Description: This is a digitally signed message part.
On Tuesday, May 01, 2012 03:14:13 PM Paul Elliott wrote:
On Tuesday, May 01, 2012 04:15:41 AM Stefano Rivera wrote:
Hi Ben (2012.05.01_05:08:17_+0200)
What is the best *method* to do this, though? How to best use existing
tools so as not to re-implement this boilerplate task every time
On Monday, April 30, 2012 03:45:35 AM Piotr Ożarowski wrote:
[Ben Finney, 2012-04-30]
Paul Elliott pelli...@blackpatchpanel.com writes:
My package uses a package that it makes public. What is the standard,
established way to take that package private?
In the absence of better
are talking about?
Yes and I also want to do this in the standard way. Can this be done by
altering the package_dir parameter in the call to setup in setup.py?
--
Paul Elliott 1(512)837-1096
pelli...@blackpatchpanel.com PMB 181, 11900 Metric Blvd
On Saturday, April 28, 2012 06:46:39 AM Michelle Konzack wrote:
Hello Paul Elliott,
Am 2012-04-27 20:03:44, hacktest Du folgendes herunter:
My package uses a package that it makes public. What is the standard,
established way to take that package private?
???
What do you mean
?
Or should I drop a bug on the upstream and turn it into a private python
package, installed in a non public place?
If I should do this, what is the standard, established, way of altering the
various python path type variables so that import still finds this moved
package?
--
Paul Elliott
On Thursday, April 12, 2012 08:30:41 AM Barry Warsaw wrote:
Hi Paul,
On Apr 12, 2012, at 02:09 AM, Paul Elliott wrote:
A recent review of my package asked me to consider making a python3
version.
Excellent! One more down the road to Python 3 world domination. :)
But the response below
On Wednesday, April 18, 2012 10:12:24 AM Barry Warsaw wrote:
On Apr 18, 2012, at 03:09 AM, Paul Elliott wrote:
I am not a expert python packager. I am dubious about a bunch of cargo
cult packagers all writing seperate but similar debian/rules
complications.
That's why I wrote the style
into.
Scott K
I think you have just put your finger on another problem then.
Nobody thinks python3 is important enough to have a debhelper infrastructure?
My upstream tells me he does not know of any python3 programs using his
module.
Maybe I should delay python3 support then.
--
Paul Elliott
this extension module. So I can
check that the python 2 extension works. But I don't have any python 3
programs that use the python3 extension module.
Under these conditions should I create a python 3 extension, without knowing
if it works?
Cheers,
-Barry
--
Paul Elliott
,
a python program that is also being RFSed:
http://mentors.debian.net/package/openastro.org
Changes since the last upload:
* ephe_path should be /usr/share/libswe/ephe2:/usr/share/libswe/ephe
* upgrade to Standards-Version: 3.9.3
Regards,
Paul Elliott
-- System Information:
Debian
Regards,
Paul Elliott
-- System Information:
Debian Release: wheezy/sid
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'stable')
Architecture: i386 (i686)
Kernel: Linux 3.2.0-1-686-pae (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell
I created a package with py2dsc. After some tweeks, it works correctly. The
upstream says package also works with python 3. How do I alter my source
package to also produce a python 3 version?
Thank You.
--
Paul Elliott 1(512)837-1096
pelli
On Wednesday, October 19, 2011 04:35:15 AM you wrote:
On Wed, Oct 19, 2011 at 04:27:36 -0500, Paul Elliott wrote:
Can someone please give me an alternate way to contact
Python-modules-team mailing list. I am subscribed to this list. But my
messages to the list bouce because of blacklist. I
On Wednesday, October 19, 2011 04:58:55 AM David Paleino wrote:
On Wed, 19 Oct 2011 02:36:57 -0500, Paul Elliott wrote:
Is there a standard for watch files for extensions in python3 package
index like this one?
http://pypi.python.org/pypi/pyswisseph
Why not the usual:
http
I created a package using py2dsc. Upstream says package supports python3. How
do I add python3 package(s)?
Thank You.
--
Paul Elliott 1(512)837-1096
pelli...@blackpatchpanel.com PMB 181, 11900 Metric Blvd Suite J
http://www.free.blackpatchpanel.com
Sorry if this is a faq, but are there any hellow world
debian sample packages that could be used as a starting point?
--
Paul Elliott 1(512)837-1096
pelli...@blackpatchpanel.com PMB 181, 11900 Metric Blvd Suite J
http://www.free.blackpatchpanel.com/pme
18 matches
Mail list logo
