site-packages folder. Once this is done, fire up a hex editor and edit each of the DLLs that are installed in the libsvn package and replace all instances of the string python23.dll with the string python24.dll. That's all there is to it.
typecheck v0.2.0 released
typecheck module to the Python Package Index. The module's website has been updated to reflect the new version number and link to the newest build but has not yet been modified to document the changed interface after the merge with Collin's code. He tagged the 0.2.0 version yesterday so we still need to catch up on a couple of minor documentation points.typecheck
and and or). Look for version 0.2.0 in your local Cheeseshop RSS Feed.
html2text right now but a lot of entries with embedded HTML come out looking pretty weird. I'll post the script once I clean up the text generation.vTodo objects to a vCalendar stream and it works just fine.rdate property is what controls repeating tasks/events - not any of the other ones that purportedly serve the same purpose.
Could you eliminate the need for the text member variable by usingstr(elt)instead? Or would that interfere with usingstrto return the XML representation for the whole element?
str and repr so that the former would be a shortcut to return the text property and the latter would return the XML representation of the element.print or interpolate the element its string value will be used. There is also a nice parallel with the way nodes are handled in XPath.text property in order to continue to support the oodles of screaming fans who have already shipped billion-dollar projects based on my little library.mystic yesterday. We wanted to install Python 2.4 with subversion, trac and apache 2. It took a fair bit of wrangling (i.e. building from source) to get everything working together after which Justin realised that we hadn't upgraded to Sarge (duh!). He rebuilt everything using the latest packages and it looks OK so far.sites-available/sites-enabled organization is nicely architected, it does make for some pretty painful contortions when performing wholesale changes on a group of virtual hosts. For example, we started off testing the new installation of Apache 2.x on port 81 (which required that we split out the vhost declarations into files of their own) and then proceeded to switch it to port 80 (which ended up requiring a quick cat/sed/re-direct combination). Without a good knowledge of shell scripts or some scripting language this would have been really painful.dumped it and loaded it onto mystic. It seems that I did something wrong because it loaded in Berkeley DB mode. All that is fixed now and taken care of.root.title as opposed to root('title'). More complex queries, however, reveal the power of XPath: compare [x for x in root.head.children if x.localname == 'style'] to root('head//style') to retrieve all style elements of an HTML document. Or even root('//p') to retrieve all the paragraphs.parse function until I add a try/except for that exception.
startElementNS method on a SAX ContentHandler is not necessarily passed the QName of the element. The name is passed as a URI/element name tuple, but the QName is not mandatory unless the feature_namespace_prefixes feature is enabled. The following code shows how to do this:
from xml.sax.handler import feature_namespaces, feature_namespace_prefixes
from xml.sax import make_parser
contentHandler = MyContentHandler()
parser = make_parser()
# Perform namespace processing
parser.setFeature(feature_namespaces, True)
# Report original prefixed names (i.e. qname is passed to startElementNS)
parser.setFeature(feature_namespace_prefixes, True)
parser.setContentHandler(contentHandler)
parser.parse(inputSource)
children attribute should not contain descendants. It never really did but since YAXL Elements are represented as XML fragments, it may have seemed that way.
>>> import yaxl
>>> x = yaxl.Element('x')
>>> x.append('y').append('z').append('w')
<w />
>>> x.children
[<y><z><w /></z></y>]
z and w elements are returned as part of children but they are just part of the XML fragment that y outputs.child::* and get back a list of immediate children.
Element objects. Currently only attribute-value and node/node-set selections are supported. Also, only the following axes are allowed in queries: self, parent, ancestor, ancestor-or-self, child, descendant, descendant-or-selfselect on an instance of Element or you can call an instance of Element and supply the XPath as the only parameter.
doctest tests within typechecked functions.func_globals object is the same object as the function's module's __dict__ property. This is not true of any decorated function where the decorator is defined outside the module the function is defined in.typecheck.doctest module allows you to bypass the check that doctest usually uses and replaces it with a much more liberal one that just verifies that a function's __module__ property is the same as the name of the module in which the function is defined.
What does it take to make someone so dissatisfied, so unable to bear the life they lead, that they can walk away and start a new, better life, a different way, elsewhere? And what does it take before we realize that the prisons in which each of us live, societally and metaphorically, are prisons without locks, just waiting for us to let ourselves out?
setuptools script for building eggs and so forth. I moved a huge amount of code around and consolidated a number of dangling modules at the wodfs.* level into the wodfs package.wodfs.SimpleSystem class that can be easily used whenever you want to hack with the WOD programmatically (i.e. not through the filesystem). I also shifted the code from wodfs.server so you can call wodfs.start(port=9000) to get a self-documenting XMLRPC server backed by the WOD.typecheck, a type-checking module for Python. It is registered at the Python Package Index and everything.setuptools which I am now convinced kicks some pretty major ass. It was really easy to package everything up and upload it to PyPI. setuptools can even do special tricks like allowing you to deploy a "development" version of your package that you can edit from your checkout directory but that still gets included in sys.path - really neat stuff.
The whole spread of the Web happened not because of a decision and a mandate from any authority, but because a whole bunch of people across the 'Net picked it up and brought up Web clients and servers, it actually happened.
distutils called setuptools. One of the included scripts, easy_install.py is a shot at duplicating CPAN/apt-get and other package management tools.setuptools also works with Python Eggs, a package format that extends the distutils format.setuptools package (which incidentally comes with a bootstrap script that downloads and installs the package automatically). Everything ran straight out of the box and I was able to install and upgrade several packages already installed on my system very easily. Great work! This is something Python has sorely needed for a while.
foxy6969 was in the channel but it's not the same. Wikis are always now.myprojects where you put all your code, you can open (either by creating it in Windows or by cd'ing to it in UNIX) a folder called myprojects@2004-01-01 and you will see that folder's contents exactly as they were on the first of January, 2004. This works with any folder (even the root) in your filesystem. Individual files track every single saved modification and allow you to browse through the history of the file using dates (as explained above) or by appending @ and a negative number representing the number of steps backwards to take.
1 class t:
2 [tab]def f():
3 [tab][tab]x = 5
4 [space][space]print x
5
6 [tab]def x():
7 [tab][tab]pass
8
9 t()
<img src="data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAAFAAAAAMCAIAA
AB6P612AAAAmklEQVR42uWWSw6AIAxE7VXg/keqV8FPE12AdUYgamDREFomfVBIJaU0jTSEA
xbZbI8zaqXs6OwuUdVbkRDjamfVY4IEUzHILmQ4OubygHPOzwIjGV4CO5y4bkNgSpAApjiR/
CgGZwVxEcD2ulnO/06gT6uylp5dbE1W5SoIoQFwZaL9gAvkgwCfygb8cqeV9wn9ehuTH621X
AArWx8EprTSmAAAAABJRU5ErkJggg==">
exec. This principle shows up in inheritance too if you're not careful (or you come from Java):
>>> class A:
... def __init__(self):
... self.__x = 5
... def getx(self):
... return self.__x
...
>>> class B(A):
... def getx(self):
... return self.__x + 5
...
>>> b = B()
>>> b.getx()
Traceback (most recent call last):
File "", line 1, in ?
File "", line 3, in getx
AttributeError: B instance has no attribute '_B__x'
read and readline. This interface is obviously a little hard to code to since in order to implement it you need to read the specific requirements of the method/function you're calling.NotImplementedException from your methods. Note that in Python this class wouldn't even need to be bundled with the base distribution since Duck Typing works whether you like it or not.fileobject parameter is. It will work fine with a file from the open or file functions as well as with any other iterable object.
def line_count(fileobject):
count = 0
for i in fileobject:
count += 1
return count
def line_count(iterable_object):
count = 0
for i in iterable_object:
count += 1
return count
class Iterable(object):
def next(self):
raise NotImplementedException
def __iter__(self):
return self
def line_count(itobj):
"""Pass me an instance of Iterable, please."""
count = 0
for i in itobj:
count += 1
return count
net time /setsntp:pool.ntp.org
raise 'Not Implemented' statements for all the method implementations. Anybody subclassing the class would be forced to implement the methods. We could even have a meta-class for it that checks that all the methods are implemented - again, no need for extended syntax.map, filter and reduce. I applaud this since the list comp syntax neatly handles these functions' roles.
So let's take a look at these items one by one.
- Concerns about security (getting better, but reports of major academic institutions being hacked don't help. Regardless, EMRs are still inherently more secure than paper records)
- Cost (big issue-a small practice just doesn't have $20k to blow on a new system)
- Startup: How to input thousands of paper-based records into an EMR fast and inexpensively
This is pretty annoying since the WOD uses SHA-1 to calculate the fingerprints of the blocks in the system. We pretty much depend on the fact that the SHA-1 algorithm requires 280 comparisons in order to generate a data block whose fingerprint collides with another block's. The reduction in the overall namespace for fingerprints is a real pain. I'm already starting to look for another option that will fit in 160 bits and will have the original unrestricted namespace.SHA-1 has been broken. Not a reduced-round version. Not a simplified version. The real thing.
The research team of Xiaoyun Wang, Yiqun Lisa Yin, and Hongbo Yu (mostly from Shandong University in China) have been quietly circulating a paper describing their results:
- collisions in the the full SHA-1 in 2**69 hash operations, much less than the brute-force attack of 2**80 operations based on the hash length.
- collisions in SHA-0 in 2**39 operations.
- collisions in 58-round SHA-1 in 2**33 operations.
This attack builds on previous attacks on SHA-0 and SHA-1, and is a major, major cryptanalytic result. It pretty much puts a bullet into SHA-1 as a hash function for digital signatures (although it doesn't affect applications such as HMAC where collisions aren't important).
