[ANN] New article:

2013-08-12 Thread mauricel...@acm.org
Dear all

The following article had been peer-reviewed and accepted by The Python Papers.

Title: A Python Module for FITS Files with full C Level Programming 
Functionality

Abstract: A Python module for manipulating files in the FITS format is 
described. The module was constructed using the capabilites of ctypes to 
dynamically create foreign function interfaces from a C library. Here this was 
used to import the CFITSIO library into Python. I describe how this module can 
be used to call the functions from the C library in their near native form, and 
how one to manipulate FITS files in a style that Python programmers are 
accustomed. The ctypes and ctypeslib modules allows one to import all routines 
and data structures from the C library and avoids the need to manually write 
language bindings for each routine. Moreover, these modules allow the Python 
programmer to enjoy the full functionality of the the underlying C library.

http://ojs.pythonpapers.org/index.php/tpp/article/view/250

Maurice Ling
Co-EIC, The Python Papers
-- 
http://mail.python.org/mailman/listinfo/python-list


[ANN] New article in The Python Papers Source Codes - COPADS III (Compendium of Distributions II): Cauchy, Cosine, Exponential, Hypergeometric, Logarithmic, Semicircular, Triangular, and Weibull

2013-07-25 Thread mauricel...@acm.org
Hi everyone

We have a new article in The Python Papers Source Codes.

Title: COPADS III (Compendium of Distributions II): Cauchy, Cosine, 
Exponential, Hypergeometric, Logarithmic, Semicircular, Triangular, and Weibull

Abstract: This manuscript illustrates the implementation and testing of eight 
statistical distributions, namely Cauchy, Cosine, Exponential, Hypergeometric, 
Logarithmic, Semicircular, Triangular, and Weibull distribution, where each 
distribution consists of three common functions – Probability Density Function 
(PDF), Cumulative Density Function (CDF) and the inverse of CDF (inverseCDF). 
These codes had been incorporated into COPADS codebase 
(https://github.com/copads/ copads) are licensed under Lesser General Public 
Licence version 3.

URL: http://ojs.pythonpapers.org/index.php/tppsc/article/view/253

Maurice Ling
Co-EIC, The Python Papers Source Codes
-- 
http://mail.python.org/mailman/listinfo/python-list


[ANN] TPPA is listed in DRJI

2013-02-25 Thread mauricel...@acm.org
Dear All,

I am pleased to announce that all 3 periodicals under The Python Papers 
Anthology (http://ojs.pythonpapers.org) are listed in Directory of Research 
Journal Indexing (http://www.drji.org/FullStatistics.aspx).

Thank you for your continued support and we wish to see more 
contributions/submissions.

Warm regards
Maurice Ling
Co-Editor-in-Chief
The Python Papers Anthology
-- 
http://mail.python.org/mailman/listinfo/python-list


[ANN] New article published: TMSTAF – The Extended Use of STAF on Test Automation

2012-11-29 Thread mauricel...@acm.org
http://ojs.pythonpapers.org/index.php/tpp/article/view/247

Abstract

As software packages becomes increasingly large and complex, the time required 
for testing them, throughout the development lifecycle, has also increased. 
Because testing activities consume the majority of software Quality Assurance 
(QA) resources, a test platform was needed to speed up test cycles without any 
decrease in test result accuracy. The use of Python 2.6 scripting language to 
create a faster, automated testing platform is reported here. Trend Micro 
Software Testing Automation Framework (TMSTAF) was developed using Python 2.6, 
based on Software Testing Automation Framework (STAF), to improve automated 
testing. We found that TMSTAF not only decreased testing time, it provided 
faster process integration, test feedback, and improved overall software 
quality. Using the TMSTAF automation environment for development and execution 
is simple to set up. Test cases can be created for use in both manual and 
automated tasks, converted to automated scripts, and implemented with structur
 al and flexible mechanisms. Automation script pre-runs and debugging make 
troubleshooting more efficiently; TMSTAF test report data can be used to 
identify quality issues quickly. TMSTAF can be seamlessly integrated into the 
build release process, making it a smart option for software QA engineers.
-- 
http://mail.python.org/mailman/listinfo/python-list


[ANN] 2 new articles in The Python Papers

2012-10-29 Thread mauricel...@acm.org
Hi all

I'm pleased to announce 2 newly published articles in The Python Papers 
(ojs.pythonpapers.org).

FUSE’ing Python for Development of Storage Efficient Filesystem
(http://ojs.pythonpapers.org/index.php/tpp/article/view/244)

Abstract: Filesystem is a core component of a functional operating system. 
Traditional Filesystem development has been confined to the kernel space. A 
customized, purpose-built, and user-driven Filesystem development involves 
extensive knowledge of kernel internals, tools and processes. Alternatively, 
user-space Filesystems are preferred over the kernel space Filesystem, for ease 
of development, portability and developing prototypes Filesystems, particularly 
for intuitive abstraction of “non-file” objects.

This paper proposes usage of FUSE kernel module to develop a functional 
Filesystem in user-space, titled “seFS”. Apart from offering convenience of 
user-space development, FUSE allows on-par features and functionality of a 
kernel space Filesystem. We demonstrate development of a Filesystem in Python 
on Ubuntu 11.04 system with Python-Fuse bindings.

seFS Filesystem abstracts a SQLite database to store files data and metadata. 
By developing a Filesystem with Python-FUSE, we quickly solved the problem of 
efficient data management with online de-duplication and data compression. We 
discuss the internals of FUSE, its operation and implementation in this paper.


An Artificial Life Simulation Library Based on Genetic Algorithm, 3-Character 
Genetic Code and Biological Hierarchy
(http://ojs.pythonpapers.org/index.php/tpp/article/view/245)

Abstract: Genetic algorithm (GA) is inspired by biological evolution of genetic 
organisms by optimizing the genotypic combinations encoded within each 
individual with the help of evolutionary operators, suggesting that GA may be a 
suitable model for studying real-life evolutionary processes. This paper 
describes the design of a Python library for artificial life simulation, 
Digital Organism Simulation Environment (DOSE), based on GA and biological 
hierarchy starting from genetic sequence to population. A 3-character 
instruction set that does not take any operand is introduced as genetic code 
for digital organism. This mimics the 3-nucleotide codon structure in naturally 
occurring DNA. In addition, the context of a 3-dimensional world composing of 
ecological cells is introduced to simulate a physical ecosystem. Using DOSE, an 
experiment to examine the changes in genetic sequences with respect to mutation 
rates is presented.

Maurice Ling
Co-EIC, The Python Papers
-- 
http://mail.python.org/mailman/listinfo/python-list


[ANN] The Python Papers Anthology IndexCopernicus Value for 2011

2012-10-24 Thread mauricel...@acm.org
Dear all

On behalf of the editorial committee of The Python Papers (overseeing The 
Python Papers, The Python Papers Monograph, and The Python Papers Source 
Codes), it is my pleasure to announce our first IndexCopernicus Value.

Title   ISSNINDEX COPERNICUS 2011
The Python Papers   1834-3147   5.09
The Python Papers Source Codes  1836-621X   5.09
The Python Papers Monograph 1837-7092   5.09


In terms of PDF views, for TPP, we have 89 articles in total (not including 
frontmatters and editorials). Total of 103,335 gallery views (of which, 103,035 
are PDF views), averaging 1161 views per article. The top view article 
"Implementation of Kalman Filter with Python Language", clocks up 8874 views.

For TPPM, we have 49 articles. Totaling 75,239 gallery views (of which, 73,536 
are PDF views). The top article "Introduction to Computer Vision in Python", 
clocks up 11,458 views.

For TPPSC, we have only 11 articles but even then, the total gallery views is 
17,259 (of which, 13,752 are PDF views).

Thank you everyone for your continued support.

Warm regards
Maurice Ling
Co-EIC, The Python Papers Anthology
-- 
http://mail.python.org/mailman/listinfo/python-list


[ANN] New paper published (Volume 7 of The Python Papers) - Designing and Testing PyZMQ Applications

2012-07-30 Thread mauricel...@acm.org
Link: http://ojs.pythonpapers.org/index.php/tpp/article/view/242

Abstract

PyZMQ is a powerful and easy-to-use network layer. While ZeroMQ and PyZMQ are 
quite well documented and good introductory tutorials exist, no best-practice 
guide on how to design and especially to test larger or more complex PyZMQ 
applications could be found. This article shows a possible way to design, 
document and test real-world applications. The approach presented in this 
article was used for the development of a distributed simulation framework and 
proved to work quite well in this scenario. 
-- 
http://mail.python.org/mailman/listinfo/python-list


[ANN] New paper published (Volume 7 of The Python Papers) - High-Speed Data Shredding using Python

2012-07-30 Thread mauricel...@acm.org
Link: http://ojs.pythonpapers.org/index.php/tpp/article/view/243

Abstract

In recent years, backup and restore is a common topic in data storage. However, 
there’s hardly anybody mention about safe data deletion. Common data 
destruction methodology requires the wipe operation to fill the disk with 
zeros, then with random data, and then with zeros again. Three passes are 
normally sufficient for ordinary home users. On the down side, such algorithms 
will take many hours to delete a 2TB hard disk. Although current Linux utility 
tools gives most users more than enough security and data protections, we had 
developed a cross-platform standalone application that could expunge all 
confidential data stored in flash drive or hard disk. The data shredding 
software is written in Python, and it could overwrite existing data using 
user-defined wipe algorithm. This software project also explores the technical 
approaches to digital data destruction using various methodologies defined in 
different standards, which includes a selection of military-grade procedures 
proposed by information security specialists. The application operates with no 
limitations to the capacity of the storage media connected to the computer 
system, it can rapidly and securely erase any magnetic mediums, optical disks 
or solid-state memories found in the computer or embedded system. Not only does 
the software comply with the IEEE T10/T13 specifications, it also binds to the 
number of connectivity limited by the SAS/SATA buses.

-- 
http://mail.python.org/mailman/listinfo/python-list


Re: Regular expressions

2011-12-26 Thread mauricel...@acm.org
On Dec 27, 8:16 am, Jason Friedman  wrote:
> > On Tue, Dec 27, 2011 at 10:45 AM, mauricel...@acm.org
> >  wrote:
> >> Hi
>
> >> I am trying to change  to .
>
> >> Can anyone help me with the regular expressions needed?
>
> > A regular expression defines a string based on rules. Without seeing a
> > lot more strings, we can't know what possibilities there are for each
> > part of the string. You probably know your data better than we ever
> > will, even eyeballing the entire set of strings; just write down, in
> > order, what the pieces ought to be - for instance, the first token
> > might be a literal @ sign, followed by three upper-case letters, then
> > a hyphen, then any number of alphanumerics followed by a colon, etc.
> > Once you have that, it's fairly straightforward to translate that into
> > regex syntax.
>
> > ChrisA
> > --
> >http://mail.python.org/mailman/listinfo/python-list
>
> The OP told me, off list, that my guess was true:
>
> > Can we say that your string:
> > 1) Contains 7 colon-delimited fields, followed by
> > 2) whitespace, followed by
> > 3) 3 colon-delimited fields (A, B, C), followed by
> > 4) a colon?
> > The transformation needed is that the whitespace is replaced by a
> > slash, the "A" characters are taken as is, and the colons and fields
> > following the "A" characters are eliminated?
>
> Doubtful that my guess was 100% accurate, but nevertheless:
>
> >>> import re
> >>> string1 = "@HWI-ST115:568:B08LLABXX:1:1105:6465:151103 1:N:0:"
> >>> re.sub(r"(\S+)\s+(\S+?):.+", "\g<1>/\g<2>", string1)
>
> '@HWI-ST115:568:B08LLABXX:1:1105:6465:151103/1'

Thanks a lot everyone.

Can anyone suggest a good place to learn REs?

ML
-- 
http://mail.python.org/mailman/listinfo/python-list


Re: Regular expressions

2011-12-26 Thread mauricel...@acm.org
On Dec 27, 8:00 am, Chris Angelico  wrote:
> On Tue, Dec 27, 2011 at 10:45 AM, mauricel...@acm.org
>
>  wrote:
> > Hi
>
> > I am trying to change  to .
>
> > Can anyone help me with the regular expressions needed?
>
> A regular expression defines a string based on rules. Without seeing a
> lot more strings, we can't know what possibilities there are for each
> part of the string. You probably know your data better than we ever
> will, even eyeballing the entire set of strings; just write down, in
> order, what the pieces ought to be - for instance, the first token
> might be a literal @ sign, followed by three upper-case letters, then
> a hyphen, then any number of alphanumerics followed by a colon, etc.
> Once you have that, it's fairly straightforward to translate that into
> regex syntax.
>
> ChrisA

I've tried

re.sub('@\S\s[1-9]:[A-N]:[0-9]', '@\S\s', '@HWI-ST115:568:B08LLABXX:
1:1105:6465:151103 1:N:0:')

but it does not seems to work.
-- 
http://mail.python.org/mailman/listinfo/python-list


Regular expressions

2011-12-26 Thread mauricel...@acm.org
Hi

I am trying to change "@HWI-ST115:568:B08LLABXX:1:1105:6465:151103 1:N:
0:" to "@HWI-ST115:568:B08LLABXX:1:1105:6465:151103/1".

Can anyone help me with the regular expressions needed?

Thanks in advance.

Maurice
-- 
http://mail.python.org/mailman/listinfo/python-list


Call for Papers - PyCon Asia Pacific 2010

2009-08-18 Thread mauricel...@acm.org
Dear fellow friends and colleagues,

I apologize if you had received multiple copies of this Call for
Papers.
Maurice
==

Call for Papers - PyCon Asia Pacific 2010


PyCon Asia Pacific 2010 represents a major development for the Python
community in the Asia Pacific region. In Asia Pacific, we are
encouraged by the country-level initiatives of Python conferences in
India and New Zealand. We fully expect that PyCon Asia Pacific will be
hosted by different APAC countries as the momentum of Python develops
in the region.

Quote : “…Python development in the Asia Pacific region is proceeding
rapidly… I would very much like to highlight the special nature of
this conference…. I hope that my presence will help to further
international cooperation on Python development”
Steven Holden, Chairman, Python Software Foundation (PSF)
Keynote, PyCon Asia Pacific 2010

PyCon Asia Pacific 2010’s is looking for proposals from the Python
community to fill its formal presentation tracks. The Conference Days
will be June 10-11, 2010 in Singapore, preceded by a Tutorial Day
(June 9). (http://apac.pycon.org)

Important Dates
---
•   Call for Papers: August 15, 2009
•   Deadline for Paper Submissions: February 1, 2010
•   Notification of Paper Acceptance: March 15, 2010
•   Conference Registration Open: March 15, 2010
•   Submission of Camera-Ready Paper: April 15, 2010
•   Conference Days: June 10 - 11, 2010 (preceded by tutorials on the
June 9, 2010)

PyCon Topics

PyCon conferences worldwide have had a broad range of presentations,
ranging from reports on academic and commercial projects to tutorials
and case studies. We hope to continue that tradition here at PyCon
Asia Pacific in Singapore. As long as the presentation is interesting
and potentially useful to the Python community, it will be considered
for inclusion in the program. We are especially interested in short
presentations that will teach conference-goers something new and
useful.

Suitable topics for PyCon Asia Pacific 2010 presentations include, but
are not limited to:
•   Core Python and other implementations: IronPython, Jython, PyPy and
Stackless.
•   Python libraries and extensions
•   Business Applications
•   Databases
•   Embedding and Extending Python
•   Game Programming
•   GUI Programming
•   Network Programming
•   Python in IT Security
•   Open Source Python projects
•   Packaging Issues
•   Programming Tools
•   Project Best Practices
•   Python in Education, Science and Math
•   System Administration
•   Web Programming (Django, Zope, TurboGears, WSGI)

Talk Format
-
The preferred length for talks is 30 minutes. Session lengths include
time for audience questions. You should budget at least five minutes
for questions; for example, a 30-minute talk will be 25 minutes of
presentation and 5 minutes of questions. Open Space rooms will also be
available for follow-up sessions.

Proposal Submission
---
The primary author should submit a proposal, after which additional
authors can be added. This is to help us make arrangements for
reviewers and draft the conference programme. The proposal must
include the following:
•   Talk title.
•   Choice of one or more category tag.
•   Level. Indicate the intended audience difficulty level i.e.
beginner, intermediate or advanced.
•   Summary (max 100 words) for the website.
•   Description : Detailed outline for review; notes for reviewers and
permission for your talk to be recorded.

Your proposal will be reviewed by the programme committee. If your
proposal is accepted, you should thereafter include:
•   a companion paper (up to 30 pages) OR
•   an extended abstract (up to 3 pages)

along with your presentation. Go to 
http://us.pycon.org/2008/conference/proposals/
example1/ for an example of a conference talk proposal.

Please send your proposal (and any questions) to
confere...@pugs.org.sg.

Companion Paper or Extended Abstract Submission

All presenters should submit a paper by the deadline above, with or
without prior proposal submission.

This submission is to be your full paper (companion paper or extended
abstract), not a draft. It should contain all of the usual aspects of
a paper such as an abstract, introduction, body and conclusion. Please
ensure that this submission has had its grammar and spelling corrected
and that code snippets work.

Your paper will be peer-reviewed by the programme committee and a
notice of paper acceptance with review comments will be sent to the
author(s) on March 15, 2010.

Accepted papers can be amended by the author(s), takin

[ANN] Completion of The Python Papers Volume 4 Issue 1

2009-05-06 Thread mauricel...@acm.org
Welcome to Issue 4 Volume 1 of The Python Papers. This marks our 4th
year in business. It is my pleasure to announce 4 improvements made to
The Python Papers Anthology.

Firstly, we had created a class of editorial members in our team – the
Editorial Reviewers (ER). This is in addition to the existing Editors-
in-Chief (EIC) and Associate Editors (AE). In the words of our revised
editorial policy, “ER is a tier of editors deemed to have in-depth
expertise knowledge in specialized areas. As members of the editorial
board, ERs are accorded editorial status but are generally not
involved in the strategic and routine operations of the periodicals
although their
expert opinions may be sought at the discretion of EIC.” To this
aspect, we are glad to have Jacob Kaplan-Moss (President, Django
Software Foundation; Partner, Revolution Systems, LLC; Co-BDFL,
Django) as our first ER. Welcome aboard.

Secondly, we had adopted a fast publication scheme. In the past,
accepted manuscripts will only be published on the release date in the
month of April, August and December each year. With the use of Open
Journal System, we are able to publish manuscripts as they are being
accepted. This means that the release date in the month of April,
August and December is now effectively our closing date for the issue.
For example, manuscripts accepted after April 2009 will be routed to
immediate publication in Volume 4 Issue 2. This is to being
information faster to our readers, rather than waiting for a few
months.

Thirdly, we announce a set of manuscript templates for our authors and
contributors for their manuscript preparation. As such, we had
revamped our website (http://www.pythonpapers.org) to reflect these
changes.

Lastly, we are glad to announce the launch of our 2nd publication
under The Python Papers Anthology – The Python Papers Source Codes
(ISSN 1836-621X). TPPSC, for short, is a collection of software and
source codes, usually associated with papers published in The Python
Papers and The Python Papers Monograph. These codes are refereed for
originality, accuracy, completeness, and lasting value. TPPSC will
act as a developers codebook of high-quality, peer-reviewed codes.
TPPSC is an annual publication using the same fast publication scheme.

We thank all our readers and contributors for their continued support.

Happy reading.

Maurice Ling
Co-EIC, TPPA
--
http://mail.python.org/mailman/listinfo/python-list


[ANN] The Python Papers Source Codes (Volume 1)

2009-01-21 Thread mauricel...@acm.org
Hi everyone,

It has been a few months in the cooking and I'm pleased to announce
the publication and ISSN of The Python Papers Source Codes (ISSN
1836-621X). The Python Papers Source Code (TPPSC) will be a collection
of code manuscripts, usually with a longer companion manuscript
published in The Python Papers (TPP) or The Python Papers Monograph
(TPPM).

The purpose of TPPSC is modeled after "Collected Algorithms of the
ACM".

We will consider the following papers for TPPSC:

* Algorithms: Implementation of an algorithm where it should be
possible for a user to incorporate this software into a larger
program, with the exception of standalone software.
* Remarks: Brief report on a previously published algorithm, with the
purpose of correcting / modifying the code. Details arguing for the
modification should be provided with the modified code and patch file
to used with the original implementation.
* Translations: Translation of an algorithm / code from another
programming language to Python, and should only be done if the
algorithm still represents the current state of the art.
* Certifications: Report on performance characteristics or
verification of correctness by specification or from extensive testing
of a previously published an algorithm / code. Certification reports
do not change the original code; hence, a certification report usually
do not contains codes.

Each submission will usually consist of the following sections:

   1. Title and author(s) affiliation
   2. Abstract (usually a terse description of 1 or 2 sentences)
   3. Description (about a page description of the purpose of the
codes, including licence)
   4. Code section (this is where the codes will be listed)
   5. References
   6. A compressed file of the codes files as supplementary materials

For more details or to read our first paper under TPPSC, please go to
http://ojs.pythonpapers.org/index.php/tppsc/issue/current

All manuscripted for the periodicals under The Python Papers Anthology
(http://ojs.pythonpapers.org) will be published once they are
accepted.

We look forward to your continued support.

Cheers
Maurice Ling
Co-EIC, TPPA

Maurice Ling
--
http://mail.python.org/mailman/listinfo/python-list


[ANN] The Python Papers Volume 3 Issue 3

2009-01-12 Thread mauricel...@acm.org
Hi everyone

First of all, let me apologize for the delay of this issue of TPP. I
understand that all of you had been anxiously waiting and I do
sincerely apologize that Christmas and New Year celebrations are
taking a toll on my time.

Finally, here it is... Volume 3 Issue 3... And we are THIRD year in
business.

As usual, the issue can be found at 
http://ojs.pythonpapers.org/index.php/tpp/issue/current

The 1-PDF per issue will be released shortly.

Let me also take this opportunity to show our deep felt appreciation
to all our supporters/readers and contributors. Without you, we will
not have our day to serve the community.

At this moment, I will also like to announce our new publication
schedule - there will not be any!!! Oppss, that did not come out
right...

What I am trying to say is that from Volume 4 Issue 1 onwards, we will
adopt the "fast publishing" method that many journals are using. We
will be releasing each article out to the public as they are being
accepted but each issue will be delimited by our usual “issue release”
date. The “issue release” date is then our cutoff deadline to prepare
the 1-PDF per issue file. This means that we will be serving new
articles to everyone much faster than now and there will not be
anymore meaningful publication schedules.

Hence, let's gear up to another year of exciting Python development
and a recovering economy.

Happy reading
Maurice Ling
Co-EIC, The Python Papers Anthology
--
http://mail.python.org/mailman/listinfo/python-list