text:
Q: Upon clicking on links the view is unable to load? I am trying to learn web development using react but am stuck in this situation where I am unable to find why the view is not being loaded. Please, someone, guide me.
App.js
import React, {Component} from 'react';

import {BrowserRouter, Route, Link, Routes} from 'react-router-dom';

import Buyer from './Container/Buyer/Buyer';
import Seller from './Container/Seller/Seller';

import classes from './App.css';

class App extends Component{
  render(){
    return(
      <BrowserRouter>

Shop

               <Link to='/buyer'>I want to Buy</Link>
               <Link to='/seller'>I want to Sell</Link>

           <Routes>
             <Route path="/buyer" exact render={Buyer} />
             <Route path="/seller" exact component={Seller} />
           </Routes>

      </BrowserRouter>

    )
  }
}

export default App;

Buyer.js
import React, {Component} from 'react';

import classes from './Buyer.css';

class Buyer extends Component{
    render(){

        return(

I want to buy groceries

        );
    }
}

export default Buyer;

Seller.js
import React, {Component} from 'react';

class Seller extends Component{
    render(){
        return(

I want to sell groceries

        );
    }
}

export default Seller;

After clicking the link "I want to buy" the view showing "I want to buy groceries" should have appeared but nothing is appearing.

A: In react-router-dom v6 the Route components no longer take exact, render, and component props, they now only take path and element. The element prop is passed a JSX literal.
Example:
<Route path="/buyer" element={<Buyer />} />

App
class App extends Component {
  render() {
    return (
      <BrowserRouter>

Shop

          <Link to="/buyer">I want to Buy</Link>
          <Link to="/seller">I want to Sell</Link>

          <Routes>
            <Route path="/buyer" element={<Buyer />} />
            <Route path="/seller" element={<Seller />} />
          </Routes>

      </BrowserRouter>
    );
  }
}


Michael and Erinn's Wedding Video Finally!
Thought I would do a catch up post on what has been up.
David and Erinn are full on in their studies. Which means I see very little of David. I will be as glad has him when this year is over and-God willing-he will have that little diploma in his hand!
And just because my husband CANNOT sit still he thought he would go for a 20 mile run up in the woods on Sunday.
Actually when he started talking about it I thought he was kidding since he is still nursing his sore calf.
Then Sunday morning he told Caleb to get his bike ready---I was like seriously!!
He was. Caleb had a football game after church on Sunday and I was thinking he, at 10 will be too tired to bike 20 miles with his dad on these dirt roads.
I who have just started working out a little after mostly a year off with this bum foot. I have been biking a whole 20 minutes about 3 times a week!
I biked 20 miles all uphill on the way out on dirt roads.
I must admit I was not always thinking pleasant thoughts on this wonderful ride!
We both survived--sore legs and all!
Caleb is enjoying his football (20)!
I really loved the looks his coaches were giving each other the other day.
Caleb had just relayed some information to me and I went to them to check if the information was correct.
I have wrote some on Caleb's listening issues, so you understand WHY I check up on most things he tells me, but his coaches did not know this, so I told them about Caleb having a hard time listening if there is background noise. That he can not tune it out and listen to what is being said.
All three of them looked at each other and grinned!!
Yep, it answered a lot of their questions too!
And, yes, it was very obvious to them everyday.
Drew was in Indiana this last weekend running at Pre-Nationals for NCAA cross country.
He is learning a lot about running in a big crowd.
He ran about mid pack, was 5th man for his team (2 dropped out). He was not overly happy with his race, but it was a great experience.
They flew in late Saturday night and he was up very early Sunday morning throwing up. Which he proceeded to do all day.
I am very thankful for another mom who was there and picked him up some medicine at the store.
He is feeling a little better and looking forward to Pac 10's in Seattle on October 30th. We are planning on heading up if anyone else will be in the area on that weekend.
Our 'little bit' is slowly moving along in her school. As you can see her it takes MANY, MANY times of showing the same concept for her to pick it up.
She was not able to visually use the ruler on the top of the page.
The actual ruler was better, but the concept of measuring from the side of the object and not the side of the paper was not sinking in. Today we will try measuring actual objects. This should make it easier for her.
We have finally found a clinic that will be doing a thorough evaluation for us on Hannah.
I called the clinic late Tuesday evening and left a message. At 8am the next morning they were calling me back and let me know I needed a referral from our doctor. I called and left a message for the doctor at 9am. They called me back at 11am that they would send in the referral. I got a call from the clinic a 3pm, they had the referral and were sending me paperwork to get started.
Now I don't know about you, but this is absolutely unheard of for us. I just figure it must me a 'God thing' and praise Him!
So at this clinic she will work with various doctors and therapist, who will then get together and discuss what they have found and come to me with a comprehensive evaluation.
The hope is that we can get to the bottom of some of the learning and emotional issues and find out how much is permanent delays, most likely due to her malnutrition and how much is just that she needs extra help or time to navigate through.
We are excited for at least some forward motion in this area.


Our annual conference gathered current and new members alike as we focused on subsea technology, new markets and on-going as well as potential projects for the future.
During the first day of our conference "Of Course on Course", current projects and potential markets were in focus. Several representatives from our member Sigma Energy & Marine presented two on-going projects financially supported by OffshoreVäst, which concerned offshore fish farming and power transmission systems for wave power plants respectively.
Our annual conference was summarized by our current process leader Erik Bunis and our former one – Kerstin Hindrum. She suggested that despite what the Swedish innovation agency initially thought, one of the strengths of OffshoreVäst is and always has been our broad competence as knowledge is transferred between different segments and sectors.


text:
Neil L. Whitehead: An Obituary by Peter Hulme
Noted anthropologist and Caribbeanist Neil L. Whitehead died March 22 following an illness. Peter Hulme, his long-time friend and collaborator, has written the tribute that follows.
It's nearly a month now since I heard that Neil Whitehead had died. Only his family knew of his illness, so his death came as a shock to his many friends. He had just had his 56th birthday, which is no age at all to be ending a career.
My first memory of Neil is a phone call from him around 1988, after he'd heard that I was working for Oxford University Press on an anthology about encounters with indigenous cultures of the Caribbean. I soon invited him to join me as co-editor and we spent the next three years locating and translating texts, each working on different sections but then meeting up periodically for intensive two-day sessions either at his house in Oxford or mine in Ardleigh. We made a good team. He was a historical anthropologist with an interest in textual complexity, I was a literary critic with an interest in how historical texts were interpreted. We both had strong ideas. Fortunately, most of the time they coincided. When they didn't, we worked through them amicably. The Introduction was finalised, I remember, during a few days in Dominica—Neil's first visit to the island. Wild Majesty: Encounters with Caribs From Columbus to the Present Day came out in 1992 and we both remained proud of the book.
Just after Wild Majesty was published, Neil got his first 'proper' job, at the University of Wisconsin Madison (previously he had a series of research fellowships), so we subsequently saw each other less frequently—maybe every couple of years, often at conferences or visiting talks. Our geographical frames had always been slightly different: my centres of gravity were very much Dominica, then Cuba, while his was Guyana—glancing northwards to the islands but drawn also south to the Amazon: his first book (Lords of the Tiger Spirit) had been a ground-breaking study of the development of the Carib polity in the two centuries after contact. But another common interest was travel writing—Neil owned a copy of just about every travel book about Guyana, even the trashiest (in fact the trashier the better)—so a logical next step for him was the critical edition he produced in 1997 of Walter Ralegh's The Discoverie of the Large, Rich and Bewtiful Empyre of Guiana. These critical editions of primary texts—two more were to follow—show Neil's scholarship at its most powerful. He never took these colonial-era writers at their word, but he had a sympathetic understanding of how they were interpreting their encounters with indigenous cultures, based on his knowledge of the relevant historical anthropology—which in turn was bolstered by his experiences on the ground. His introduction to the Discoverie was almost book-length, and its second chapter, "The Discoverie as ethnological text", has been vindicated by recent archaeological work in Guayana and the wider Amazon region.
As an early career researcher Neil hadn't had the resources to do much fieldwork. Now at Madison he could undertake extensive visits to South America, out of which came Dark Shamans: Kanaimà and the Poetics of Violent Death, published in 2002, which cemented his reputation as an ethnographer. The second of his great textual editions (made with Michael Harbsmeier) was of Hans Staden's True Captivity (2008). Geographically this took him further south, but of course its centrality to discussions of cannibalism kept it relevant to Caribbean debates. Again, an introduction of more than 100 pages, along with extensive notes, will make this a definitive edition for many years to come. Neil's final textual work came on the ur-text of Caribbean ethnography, Fray Román Pané's Antiquities of the Indies (the edition published last year as Of Cannibals and Kings: Primal Anthropology in the Americas). Pané's is the first extended account of any Caribbean culture, but its linguistic and textual complexity (it was only ever published in an Italian translation and no original manuscript survives) has made it exceptionally difficult to interpret. Once again, Neil's edition is now the one to which every scholar will turn.
The last time I saw Neil was in July 2009 when I invited him over to the American Tropics conference at Essex. His lecture, entitled, with typical flair, "Golden Kings, Cocaine Lords, and the Madness of El Dorado: Guayana as Native and Colonial Imaginary", was a real tour-de force which thrilled, informed, and entertained in equal measures. The last time I heard from him was just a few months ago when he sent me a copy of the Pané edition which will now have to remain the final achievement of a remarkable career. Cultural anthropology is certainly mourning one of its leading lights, but Neil was also a great Caribbeanist. Many of us working in the region have lost an open-hearted and generous friend as well as a valued colleague.
Posted in NewsTagged Neil Whitehead, Peter HulmeBy lisaparavisiniLeave a comment
← THIS WEEK IN FICTION: A NEW SHORT STORY BY JUNOT DÍAZ
Final Call for submissions for tt film festival 2012 →

redpajama_set_name: RedPajamaCommonCrawl


text:
NewsNewsFinanceAustraliaWA NewsBusiness
$60m farm aid months away as Ludwig quits
Brad ThompsonThe West Australian
Thu, 27 June 2013 8:22AM
Beleaguered WA farmers are still months away from seeing a single dollar from the Labor Government's $60 million concessional loan package despite high-level negotiations between State and Commonwealth authorities.
The loan scheme remains the subject of claim and counterclaim by State and Federal politicians and bureaucrats two months after it was announced by former treasurer Wayne Swan and former agriculture minister Joe Ludwig.
Senator Ludwig and Mr Swan, both Julia Gillard supporters, quit their Cabinet posts last night after she was dumped as prime minister.
Funding for the scheme was allocated in the May Budget and will remain in place despite the chaos in Canberra. Shadow agriculture minister John Cobb has committed the coalition to rolling out the loans if it wins the Federal election.
Officials met in WA again this week and made some progress on a deal to deliver the loans but key issues remain unresolved.
There is speculation among WA officials that the loan scheme is fundamentally flawed because the Commonwealth cannot collect on bad debts without taking out a form of security on farms known as a lien, but is powerless to do this without legislative change.
Senator Ludwig's office denied the claim earlier yesterday, saying: "We can absolutely confirm that no legislation is needed to collect bad debts."
The Commonwealth has agreed to cover bad debts after negotiations with the State. It has also agreed to cut the maximum loan from $650,000 to $200,000 and the life of the loans from up to 20 years to five years at the request of the State.
Canberra has also agreed to set the eligibility criteria for the loans at the insistence of the State. The remaining sticking points concern administration costs and the mechanism to deliver the loans.
The State estimates administration costs of about $5 million over the life of the loans, which have the potential to help about 300 WA farmers. It has suggested the Commonwealth could cover the administration costs by upping the interest rate on the concessional loans from 4.5 per cent to 5 per cent.
With no agreement pending on the administration costs, no sign of eligibility criteria and no application process in place, there is little prospect of loans flowing through to farmers before September.
Senator Ludwig said he wanted to see the loans delivered and there had been progress. "I've sent senior officials to go and work directly with WA to resolve the outstanding issues," he said.
A total of $420 million over two years is available under the loans component of the finance package - $60 million for each State and the Northern Territory.
The Commonwealth remains bogged down in talks with the States and the NT.
A separate WA Government farm aid package has seen 128 farmers receive operational grants of $25,000 from a $5 million pool.
16yo boy among seven charged over Scarborough fightsPremium


text:
La Iglesia de San Damián (en italiano, Chiesa di San Damiano) es una iglesia con un monasterio cerca de Asís (Italia). Fue el primer monasterio de la Orden de Santa Clara, donde Santa Clara construyó su comunidad. Quizá el aspecto más significativo en relación con la iglesia fue el encuentro que, según el catolicismo, se produjo entre San Francisco con Cristo. Estaba rezando en San Damián que por entonces era un edificio muy arruinado. San Francisco vio la figura de Cristo crucificado revivir y decirle: «Francisco, ¿no ves que mi casa se está derrumbando? Ve, entonces, y restaurala». Después san Francisco emprendió la reparación de San Damián, aunque con el tiempo pasó a entender que el mensaje divino se refería a la restauración de la Iglesia en su conjunto más que literalmente la reparación de iglesias como la de San Damián. La cruz desde la que Cristo habló a San Francisco es conocida como el Cristo de San Damián. Actualmente cuelga de la Basílica de Santa Clara (Asís).

La iglesia de San Damián, junto a otros lugares franciscanos de Asís, fue declarada Patrimonio de la Humanidad por la Unesco en 2000. se refería  a la  iglesia San Damián.

El lugar se convirtió en el hogar de Santa Clara de Asís y sus seguidores en 1212. Se trabajó en la dotación de edificios para esta comunidad religiosa. Las Hermanas se quedaron hasta la muerte de Clara en 1253 cuando se pensó que era demasiado peligroso quedarse y se cambió con los Canónigos de San Rufino por la capilla de San Giorgio. El convento está abierto al público de forma gratuita. En la planta baja del claustro se encuentra el refectorio en su estado original. Un fresco en el refectorio recuerda la visita del Papa Gregorio IX cuando le pidió a Clara que bendijera los panes, lo que se dice que dio lugar a que aparecieran cruces en los panes. Arriba está el Oratorio de Santa Clara, donde se guardaba el Santísimo Sacramento , y al lado está el dormitorio.  Una cruz marca el lugar donde Clara murió el 11 de agosto de 1253.

Referencias

Enlaces externos

Damian
Asís, la Basílica de San Francisco y otros sitios franciscanos
Asis

redpajama_set_name: RedPajamaWikipedia


text:
larned
[url=http://wordincontext.com/en/larned]larned[/url]
1 - 10 from 100
"Altercation will do no good, my lord and my lady," said the attorney; "let me suggest the propriety of your writing an engagement at once;" and the little man pushed pen, ink, and paper towards Andy. "I can't, I tell you!" cried Andy. "You must!" roared Shan More. "Bad luck to you, how can I when I never larned?" "Your lordship can make your mark," said the attorney.
Samuel Lover - Handy Andy, Volume 2 — a Tale of Irish Life
The General was surprised to see me, and still more so when I told him of the time I had made in riding to Fort Dodge, and that I had taken dispatches from Fort Dodge to Fort Larned; and when, in addition to this, I mentioned my journey of the night previous, General Sheridan thought my ride from post to post, taken as a whole, was a remarkable one, and he said that he did not know of its equal.
Buffalo Bill - The Life of Hon. William F. Cody
Known as Buffalo Bill the Famous Hunter, Scout and Guide
"General, how about this mule, anyhow?" I asked, at last. "Cody, you have a better vehicle than I thought you had," was his reply. From that time on to Fort Larned I had no trouble in keeping ahead of the party. We rode into the fort at four o'clock in the afternoon with about half the escort only, the rest having lagged far behind.
I gratefully accepted his offer, and after four or five hours' rest he mounted a fresh horse and hastened on his journey, halting but once to rest on the way, and then only for an hour, the stop being made at Coon Creek, where he got another mount from a troop of cavalry. At Dodge he took six hours' sleep, and then continued on to his own post Fort Larned with more despatches.
Philip Henry Sheridan - Personal Memoirs of P. H. Sheridan, General, United States Army — Volume 2
After dinner, the general proposed to go on to Fort Harker, forty-one miles away, without any escort, leaving orders for Cody to return to Fort Larned the next day, with the soldiers. But Cody, ever impatient of delay when there was work to do, notified the sergeant in charge of the men that he was going back that very afternoon.
Henry Inman - The old Santa Fe trail
The Story of a Great Highway
The Cold Weather Pinches Passengers Going Across the Plains. On one of my wintry trips across the plains, I took a passenger by the name of Miller who was going to Santa Fe to buy wool for Mr. Hammerslaugh. That was one of the most extreme cold winters I ever experienced. When we reached the long route, that is from Ft. Larned a distance of 240 miles to Ft.
W. H. (William Henry) Ryus - The Second William Penn
A true account of incidents that happened along the
old Santa Fe Trail
Ah, it's fine for you to ask how we does, and the days shortening, and the air sharpening." "Well, Dame, shall I send to for a warm cloak for you?" said Madeline. "Ho! thankye, young leddy thankye kindly, and I'll wear it at your widding, for they says you be going to git married to the larned man yander. Wish ye well, ma'am, wish ye well."
Baron Edward Bulwer Lytton Lytton - Eugene Aram — Volume 04
"Cuff," said he, patting the shaggy head of his humble friend, "many a strange thing crops up in this here koorious world, but it never did occur to my mind before, that while a larned man like a missionary might state the truth, the likes o' me should have the chance an' the power to prove it. That's a wery koorious fact, so you an' I shall go to sleep on it, my doggie good-night."
R. M. (Robert Michael) Ballantyne - Jarwin and Cuffy
Colonel Thomas Swords, quartermaster, arrived on the 13th; Paymaster Larned on the 14th; and Lieutenant Smyzer, Fifth Artillery, acting ordnance-officer, on the 20th; Captain Symonds was already on duty as the commissary of subsistence; Captain O. D. Greene was the adjutant-general, and completed a good working staff.
- Memoirs of the Union's Three Great Civil War Generals
John Hobbs, scout, trapper, and veteran plainsman, happened to be hunting buffalo on Pawnee Fork, on the ground where Larned is now situated, with a party from Bent's Fort. They were just on the point of crossing the Trail at the mouth of the Pawnee when the soldiers from Fort Leavenworth came along, and from them Hobbs and his companions first learned of the murder of Chavez on Cow Creek.
First Previous 1 2 3 4 5 6 7 8 9 10 Next Last


If you found 6 Things You Can Do To Make Your Work Day More Meaningful, here are six more things that you can do today to turning your work day around.
Learn to say no to extra commitments and recognize that your time is valuable. If you don't respect your time as an asset, no one else will, and they will try to throw tasks your way. Identify what you can realistically accomplish in a day and make sure that others respect your time.
Urgent tasks need to be dealt with immediately while important tasks contribute to long-term goals.
Some items can be urgent but not important, important but not urgent, and important and urgent. For obvious reasons, you should be doing tasks that are both urgent and important first. Your future success will rely heavily on being able to define the difference.
Identify what works and what doesn't. Determine what you're doing wrong and what you can do to avoid making the same mistakes. Always be on the lookout on how you can improve your process. Put aside some time every week to evaluate your performance. Reward yourself when you start to see improvements in efficiency.
Do you ever find yourself staring blankly at the bobbleheads, fake plants, or last Christmas's photo booth party print-out on your desk? Yes, there may be items in your workspace such as a mini vision board that is meant to inspire you. However, some of these elements can actually steal your attention rather than motivate you.
It's amazing how much more productive you can be by just clearing your desk. Removing stacks of paper that are unnecessary to your current project and putting aside other distracting items can increase your concentration.
Studies have proven that listening music can dramatically boost your mood and reduce stress. Create a playlist that helps you concentrate on work. However, to increase your productivity, it may be best to listen to instrumentals rather than the latest pop songs which may cause you to want to sing along, thus pulling you away from the task at hand.
To sustain your concentration, short breaks throughout the day are recommended. Use these breaks to relax or even raise your energy levels. Get your blood pumping by taking a walk around the office or outdoors for some fresh air. You may even want to use your break for a power nap which has also been proven to boost memory, creativity, and energy levels.
These six small actions added to the first six items mentioned in 6 Things You Can Do To Make Your Work Day More Meaningful (part 1) will give your day direction and purpose. Take control of your work day to contribute to a goal that is greater and more meaningful.


text:
4 of the Most Popular Cryptocurrencies (Other Than Bitcoin)
1 1. Ethereum
1.1 History of Ethereum
1.2 What Makes It Popular
2 2. Litecoin
2.1 History of Litecoin
3 3. Cardano
3.2 History of Cardano
4 4. Polkadot
4.1 History of Polkadot
4.2 What Makes It Unique
4.3 What Makes It So Popular
Cryptocurrencies are a new form of currency that relies on cryptography to secure transactions, generate new units, and verify payments. Bitcoin is the most popular cryptocurrency, but there are many others available. Here's an overview of four other cryptocurrencies you may not have heard of before.
1. Ethereum
Ethereum is similar to Bitcoin in that it can be both mined and traded on cryptocurrency exchanges. The creators of Ethereum have significant backgrounds in blockchain technology, cryptography, and computer science. Because of this extensive experience in coding for blockchains, they designed an open-source platform that features smart contracts.
Smart contracts are simply applications programmed to self-execute tasks when certain conditions are met. This system of having applications that run on the blockchain network has many uses, both inside and outside of finance.
History of Ethereum
Ethereum has been in development since 2013 and launched on July 30, 2015. The first phase of the project was funded with a pre-sale of ETH tokens to those interested in supporting this new platform. There were approximately 72 million Ethers created for the first investors, with an estimated value of $18.40 per token at that time.
From there, Ethereum continued with a successful crowdfunding campaign that allowed the platform to expand significantly by 2016. Their website has received nearly $15 million from more than 3,700 supporters, including several big names in the tech industry.
The development team behind Ethereum has not only been transparent and public about their goals and progress, but they have also included a page dedicated to their published documents and source code.
One of the advantages that Ethereum has over other cryptocurrencies is that it can be used in smart contracts with existing laws rather than trying to change the law itself. This allows for easier regulatory compliance worldwide while still allowing individuals and entities access to more efficient blockchain technology.
What Makes It Popular
Ethereum is famous for both its value and ability to process transactions without charging high fees. Including Ethereum in your cryptocurrency portfolio can be beneficial for diversification while still having the potential to generate significant returns.
In 2021, Ethereum will switch from proof-of-work to proof-of-stake consensus. This change will allow Ethereum's network to run on far less energy while improving transaction speed. Staking ether to the network is possible with proof-of-stake. This process aids in the protection and processing of transactions. Those who complete this task are given ether, similar to a savings account. This is a different sort of proof-of-work algorithm than Bitcoin's, in which miners are rewarded more Bitcoin for doing work.
2. Litecoin
Litecoin has solidified itself as one of the most popular cryptocurrencies other than Bitcoin because it has stayed true to Satoshi Nakamoto's vision of a decentralized, peer-to-peer currency. As an open-source project, Litecoin has attracted developers interested in creating applications across various industries using blockchain technology.
Litecoin is one of the oldest and most recognized cryptocurrencies worldwide and was released via an open-source client on GitHub in October of 2011. Since its launch, Litecoin (LTC) has experienced steady growth and is currently the sixth-largest cryptocurrency by market capitalization.
The price of Litecoin rose significantly in 2017 to reach highs nearing $400 at several points during the year. Although it did see a decline along with other cryptocurrencies in 2018, Litecoin still has a price of well over $50 and a market capitalization of around $10 billion.
History of Litecoin
As with all cryptocurrencies, the history of Litecoin is an interesting one. The creator behind this cryptocurrency was not known for several years but was revealed as former Google employee Charlie Lee in 2013. Before working for Google, Lee worked as a software engineer at Guidewire Software for six years.
Lee released Litecoin on GitHub in October 2011, and it has been traded since April of the following year. One of the key differences between Bitcoin and Litecoin is that Lee wanted to create a cryptocurrency mined using regular computers. Bitcoin requires specialized hardware for effective mining.
3. Cardano
Cardano (capitalized as ADA) is another popular cryptocurrency that has had significant growth in 2018. Like many other major cryptocurrencies, it has experienced its ups and downs throughout the year. Currently, it sits at over $0.30 per token with a market capitalization of more than $9 billion.
While Bitcoin was created as a digital currency, the Daedalus wallet for this cryptocurrency is not just a storage space for your tokens. It can also be used to create and manage decentralized applications. There are currently 45 cryptocurrencies on the market that use the Cardano system and more than a dozen projects in development.
Cardano has several benefits over other cryptocurrencies, including its method of storing information. It uses a hierarchical wallet system that allows users to store and manage multiple wallets at once effortlessly.
While Bitcoin is popular, it does have some drawbacks when compared to Cardano. For example, the need for miners in the Bitcoin network has led it down an environmentally destructive path to secure the network. With Cardano, users can stake their tokens to carry out the verification process for transactions on the network.
History of Cardano
Cardano was created by Charles Hoskinson, the former CEO of Ethereum. He left that project over disagreements about how much control he should have in its development. Instead, He decided to create his cryptocurrency called Bitshares. After leaving that venture, Hoskinson eventually started IOHK, a blockchain technology company focused on developing cryptocurrencies in consultation with groups of expert academics.
Cardano was formally released by IOHK in September 2017 after almost a year of development work. It is built on the Haskell programming language, which is more secure than some other languages that are used for blockchain projects. The ADA cryptocurrency runs on the Cardano Settlement Layer (CSL), which is a unique platform that separates accounting of value from the actual transactions being made.
4. Polkadot
Polkadot is an interesting cryptocurrency that has garnered significant attention over the past few months. It was originally announced back in January 2018 and had $145 million in private investments within 24 hours of its launch. Its ICO was originally only supposed to be available to strategic investors, but this changed due to its popularity among investors.
The developers behind Polkadot saw a problem with blockchain technology that was limiting its effectiveness in real world applications, mainly that it did not have the ability to connect with other blockchains. This is what led to the development of Polkadot and ultimately made it one of the more popular cryptocurrencies available today.
History of Polkadot
Polkadot was created by Gavin Wood, who is also the co-founder of Parity Technologies and Ethereum. He came up with the idea for Polkadot after working on Ethereum as a way to solve its scaling issues and interoperability problems associated with blockchains.
Wood worked with the Web3 Foundation to develop Polkadot and its ICO was set to launch on October 21, 2017. It ended up selling out in a matter of hours, and there was a total of 294,756 ether created by the sale.
What Makes It Unique
Polkadot is not only unique because of its interoperability – it also provides an interesting way to connect blockchains together through what is known as parachains. There are two types of parachains available through Polkadot, public and private ones. Public parachains can be used by anyone to move their data across systems, while private ones are for use by businesses that might want to keep some of their information confidential.
What Makes It So Popular
There are several reasons why Polkadot is so popular, including its interoperability between blockchains, its scalability solutions, and ability to connect other chains together. But perhaps the biggest reason it has gained so much popularity is because of its strategic investors.
PrevPreviousA Short Primer on NFTs: What You Need to Know
Next8 Reasons to Accept Cryptocurrency Payments on Your E-Commerce StoreNext


The Intermodal is located in the Iowa River Landing, with easy access from Interstate 80 Exit 242.
The Coralville Transit Intermodal Facility serves autos, buses, taxis, and bikes, and is planned to accommodate the future possibility of light rail.
A Windstar Lines terminal is located in the Coralville Intermodal Facility. Windstar Lines offers express bus service on its daily route from Omaha to Chicago. Tickets are available at www.megabus.com.
The park-and-ride commuter program features 265 covered, access-controlled parking spaces on the first two levels. Park at the Intermodal, and take another way to travel to your final destination.
Contact. Coralville Transit at 319.248.1790 for more information or to purchase a Park & Ride pass.
The third level for retail/district public parking features 159 parking spaces. This level is flush with grade like a surface parking lot.
Secured bike lockers, restrooms, and showers are available.
Bike lockers are available to rent. For more information, contact the Coralville Transit Intermodal Facility at 319.248.1790.
The Iowa Bicycle Coalition offers bike rentals, bike education, and cycling resources at the Intermodal. For more information, visit www.iowabicyclecoalition.org.
Construction of the Coralville Transit Intermodal Facility was funded in part by federal grant funds from the Federal Transit Administration; the second phase will develop pending additional grant funding. Park-and-ride program revenue funds the facility's operational costs, and additional revenue is dedicated to the operation and capital needs of Coralville Transit.


Cocoon meditation in the middle of the day is especially designed to elevate stress, put perspective on your day, help create solutions for the afternoon. Cocoon yourself in the aerial hammock to treat your mind, body and soul.
There are no upcoming "Cocoon Meditation" classes on this day.
It was nice and different way of a meditation class. Feels great to relax in the hammock, there was just a noisy class going on next door so you don't get the full tranquil experience.
Great class - room was freezing and I had a therma and hiking socks on and a blanket!


text:
package lstring

import (
	"github.com/stretchr/testify/assert"
	"testing"
)

func Test_largeGroupPositions(t *testing.T) {
	assert := assert.New(t)

	assert.Equal([][]int{{3, 6}}, largeGroupPositions("abbxxxxzzy"))
	assert.Equal([][]int{}, largeGroupPositions("abc"))
	assert.Equal([][]int{{3, 5}, {6, 9}, {12, 14}}, largeGroupPositions("abcdddeeeeaabbbcd"))
	assert.Equal([][]int{{3, 6}}, largeGroupPositions("abbxxxx"))
}

redpajama_set_name: RedPajamaGithub


text:
Saturday's Concert: Easy Access from Florida's Hot Spots
Wed., Apr. 20. 2005 1:31am EDT
Come join us for our concert in Port St. Lucie FL this Saturday, April 23, at 7 p.m. -- just 1.5 hours from Ft. Lauderdale, 2 hours from Miami or Orlando, 3 hours from Tampa and 3.5 hours from Jacksonville.
The ApologetiX concert is the last part of the Generation Alive Youth Conference, which also features praise and worship with Jeff Deyo, former lead singer for Sonic Flood, at 5:30 p.m., followed by a message by Jimmy Lloyd and comedy by Christian comedian Cleto Rodriguez.
For more information, see the left column of this week's newsletter or go to:
http://www.apologetix.com/concerts/concerts.php


text:
<!doctype html>

    <meta charset="utf-8">
    <meta http-equiv="X-UA-Compatible" content="IE=edge">

    <link rel="prefetch" href="../../../../ajax.googleapis.com/ajax/libs/jquery/1.8.2/jquery.min.js">

    <meta name="application-name" content="Python.org">
    <meta name="msapplication-tooltip" content="The official home of the Python Programming Language">
    <meta name="apple-mobile-web-app-title" content="Python.org">
    <meta name="apple-mobile-web-app-capable" content="yes">
    <meta name="apple-mobile-web-app-status-bar-style" content="black">

    <meta name="viewport" content="width=device-width, initial-scale=1.0">
    <meta name="HandheldFriendly" content="True">
    <meta name="format-detection" content="telephone=no">
    <meta http-equiv="cleartype" content="on">
    <meta http-equiv="imagetoolbar" content="false">

    <link href="../../../static/stylesheets/style.css" rel="stylesheet" type="text/css" title="default" />
    <link href="../../../static/stylesheets/mq.css" rel="stylesheet" type="text/css" media="not print, braille, embossed, speech, tty" />

    <link rel="icon" type="image/x-icon" href="https://www.python.org/static/favicon.ico">
    <link rel="apple-touch-icon-precomposed" sizes="144x144" href="../../../static/apple-touch-icon-144x144-precomposed.png">
    <link rel="apple-touch-icon-precomposed" sizes="114x114" href="../../../static/apple-touch-icon-114x114-precomposed.png">
    <link rel="apple-touch-icon-precomposed" sizes="72x72" href="../../../static/apple-touch-icon-72x72-precomposed.png">
    <link rel="apple-touch-icon-precomposed" href="../../../static/apple-touch-icon-precomposed.png">
    <link rel="apple-touch-icon" href="../../../static/apple-touch-icon-precomposed.png">

    <meta name="msapplication-TileImage" content="/static/metro-icon-144x144-precomposed.png">
    <meta name="msapplication-TileColor" content="#3673a5">
    <meta name="msapplication-navbutton-color" content="#3673a5">

    <meta property="og:site_name" content="Python.org">
    <meta property="og:type" content="website">

    <title>PEP 0435 -- Adding an Enum type to the Python standard library | Python.org</title>
    <meta property="og:title" content="Welcome to Python.org">

    <meta name="description" content="The official home of the Python Programming Language">
    <meta name="og:description" content="The official home of the Python Programming Language">
    <meta name="keywords" content="Python programming language object oriented web free open source software license documentation download community">
    <meta property="og:tag" content="Python programming language object oriented web free open source software license documentation download community">
    <meta property="og:published_time" content="">
    <meta property="og:modified_time" content="">
    <meta property="og:author" content="">
    <meta property="og:section" content="">
    <meta property="og:url" content="">
    <meta property="og:image" content="">
    <meta property="og:video" content="">

    <link rel="author" href="https://www.python.org/static/humans.txt">

Notice: While Javascript is not essential for this website, your interaction with the content will be limited. Please turn Javascript on for the full experience.

                    Skip to content

                    ▼ Close

        Python

        PSF

        Docs

        PyPI

        Jobs

        Community

                    ▲ The Python Network

                    ≡ Menu<form class="search-the-site" action="https://www.python.org/search/" method="get">
                        <fieldset title="Search Python.org">

                            Search This Site
                            <input id="id-search-field" name="q" type="search" role="textbox" class="search-field" placeholder="Search" value="" tabindex="1">

                            <button type="submit" name="submit" id="submit" class="search-button" title="Submit this Search" tabindex="3">
                                GO
                            </button>

                        </fieldset>
                    </form>

                                A A

Smaller

Larger

Reset

                                Socialize

Google+

Facebook

Twitter

Chat on IRC

                                Sign In

Sign Up / Register

Sign In

        About

Applications

Quotes

Getting Started

Help

        Downloads

All releases

Source code

Windows

Mac OS X

Other Platforms

License

Alternative Implementations

        Documentation

Docs

Audio/Visual Talks

Beginner's Guide

Developer's Guide

FAQ

Non-English Docs

PEP Index

Python Books

        Community

Diversity

IRC

Mailing Lists

Python Conferences

Special Interest Groups

Python Wiki

Python Logo

Merchandise

Community Awards

        Success Stories

Arts

Business

Education

Engineering

Government

Scientific

Software Development

        News

Python News

Community News

PSF News

PyCon News

        Events

Python Events

User Group Events

Python Events Archive

User Group Events Archive

Submit an Event

        Python>>>

        Python Developer's Guide>>>

        PEP Index>>>

PEP 0435 -- Adding an Enum type to the Python standard library

PEP 0435 -- Adding an Enum type to the Python standard library

   <col class="field-name">
   </col>
   <col class="field-body">
   </col>

      PEP:

      435

      Title:

      Adding an Enum type to the Python standard library

      Author:

      Barry Warsaw <barry at python.org>,
Eli Bendersky <eliben at gmail.com>,
Ethan Furman <ethan at stoneleaf.us>

      Status:

      Final

      Type:

      Standards Track

      Created:

      2013-02-23

      Python-Version:

      3.4

      Post-History:

      2013-02-23, 2013-05-02

      Resolution:

       http://mail.python.org/pipermail/python-dev/2013-May/126112.html

    Contents

      Abstract

      Status of discussions

      Motivation

      Module and type name

      Proposed semantics for the new enumeration type

        Creating an Enum

        Programmatic access to enumeration members

        Duplicating enum members and values

        Comparisons

        Allowed members and attributes of enumerations

        Restricted subclassing of enumerations

        IntEnum

        Other derived enumerations

        Pickling

        Functional API

      Proposed variations

        flufl.enum

        Not having to specify values for enums

        Using special names or forms to auto-assign enum values

      Use-cases in the standard library

      Acknowledgments

      References

      Copyright

     Abstract

    This PEP proposes adding an enumeration type to the Python standard library.

    An enumeration is a set of symbolic names bound to unique, constant values.
Within an enumeration, the values can be compared by identity, and the
enumeration itself can be iterated over.

     Status of discussions

    The idea of adding an enum type to Python is not new -

     PEP 354

     [2]

    is a
previous attempt that was rejected in 2005.  Recently a new set of discussions
was initiated

     [3]

    on the
    <tt class="docutils literal">

      python-ideas

    </tt>
    mailing list.  Many new ideas were
proposed in several threads; after a lengthy discussion Guido proposed adding
    <tt class="docutils literal">
     flufl.enum
    </tt>
    to the standard library

     [4]

    .  During the PyCon 2013 language
summit the issue was discussed further.  It became clear that many developers
want to see an enum that subclasses
    <tt class="docutils literal">
     int
    </tt>
    , which can allow us to replace
many integer constants in the standard library by enums with friendly string
representations, without ceding backwards compatibility.  An additional
discussion among several interested core developers led to the proposal of
having
    <tt class="docutils literal">
     IntEnum
    </tt>
    as a special case of
    <tt class="docutils literal">
     Enum
    </tt>
    .

    The key dividing issue between
    <tt class="docutils literal">
     Enum
    </tt>
    and
    <tt class="docutils literal">
     IntEnum
    </tt>
    is whether comparing
to integers is semantically meaningful.  For most uses of enumerations, it's
a

     feature

    to reject comparison to integers; enums that compare to integers
lead, through transitivity, to comparisons between enums of unrelated types,
which isn't desirable in most cases.  For some uses, however, greater
interoperatiliby with integers is desired. For instance, this is the case for
replacing existing standard library constants (such as
    <tt class="docutils literal">
     socket.AF_INET
    </tt>
    )
with enumerations.

    Further discussion in late April 2013 led to the conclusion that enumeration
members should belong to the type of their enum:
    <tt class="docutils literal">
     type(Color.red) == Color
    </tt>
    .
Guido has pronounced a decision on this issue

     [5]

    , as well as related issues
of not allowing to subclass enums

     [6]

    , unless they define no enumeration
members

     [7]

    .

    The PEP was accepted by Guido on May 10th, 2013

     [1]

    .

     Motivation

     [Based partly on the Motivation stated in PEP 354]

    The properties of an enumeration are useful for defining an immutable, related
set of constant values that may or may not have a semantic meaning.  Classic
examples are days of the week (Sunday through Saturday) and school assessment
grades ('A' through 'D', and 'F').  Other examples include error status values
and states within a defined process.

    It is possible to simply define a sequence of values of some other basic type,
such as
    <tt class="docutils literal">
     int
    </tt>
    or
    <tt class="docutils literal">
     str
    </tt>
    , to represent discrete arbitrary values.  However,
an enumeration ensures that such values are distinct from any others including,
importantly, values within other enumerations, and that operations without
meaning ("Wednesday times two") are not defined for these values.  It also
provides a convenient printable representation of enum values without requiring
tedious repetition while defining them (i.e. no
    <tt class="docutils literal">
     GREEN = 'green'
    </tt>
    ).

     Module and type name

    We propose to add a module named
    <tt class="docutils literal">
     enum
    </tt>
    to the standard library.  The main
type exposed by this module is
    <tt class="docutils literal">
     Enum
    </tt>
    .  Hence, to import the
    <tt class="docutils literal">
     Enum
    </tt>
    type
user code will run:

>>> from enum import Enum

     Proposed semantics for the new enumeration type

      Creating an Enum

     Enumerations are created using the class syntax, which makes them easy to read
and write.  An alternative creation method is described in

      Functional API

     .
To define an enumeration, subclass
     <tt class="docutils literal">
      Enum
     </tt>
     as follows:

>>> from enum import Enum
>>> class Color(Enum):
...     red = 1
...     green = 2
...     blue = 3

      A note on nomenclature

     : we call
     <tt class="docutils literal">
      Color
     </tt>
     an

      enumeration

     (or

      enum

     )
and
     <tt class="docutils literal">
      Color.red
     </tt>
     ,
     <tt class="docutils literal">
      Color.green
     </tt>
     are

      enumeration members

     (or

      enum members

     ).  Enumeration members also have

      values

     (the value of
     <tt class="docutils literal">
      Color.red
     </tt>
     is
     <tt class="docutils literal">
      1
     </tt>
     , etc.)

     Enumeration members have human readable string representations:

>>> print(Color.red)
Color.red

     ...while their
     <tt class="docutils literal">
      repr
     </tt>
     has more information:

>>> print(repr(Color.red))
<Color.red: 1>

     The

      type

     of an enumeration member is the enumeration it belongs to:

>>> type(Color.red)
<Enum 'Color'>
>>> isinstance(Color.green, Color)
True
>>>

     Enums also have a property that contains just their item name:

>>> print(Color.red.name)
red

     Enumerations support iteration, in definition order:

>>> class Shake(Enum):
...   vanilla = 7
...   chocolate = 4
...   cookies = 9
...   mint = 3
...
>>> for shake in Shake:
...   print(shake)
...
Shake.vanilla
Shake.chocolate
Shake.cookies
Shake.mint

     Enumeration members are hashable, so they can be used in dictionaries and sets:

>>> apples = {}
>>> apples[Color.red] = 'red delicious'
>>> apples[Color.green] = 'granny smith'
>>> apples
{<Color.red: 1>: 'red delicious', <Color.green: 2>: 'granny smith'}

      Programmatic access to enumeration members

     Sometimes it's useful to access members in enumerations programmatically (i.e.
situations where
     <tt class="docutils literal">
      Color.red
     </tt>
     won't do because the exact color is not known
at program-writing time).
     <tt class="docutils literal">
      Enum
     </tt>
     allows such access:

>>> Color(1)
<Color.red: 1>
>>> Color(3)
<Color.blue: 3>

     If you want to access enum members by

      name

     , use item access:

>>> Color['red']
<Color.red: 1>
>>> Color['green']
<Color.green: 2>

      Duplicating enum members and values

     Having two enum members with the same name is invalid:

>>> class Shape(Enum):
...   square = 2
...   square = 3
...
Traceback (most recent call last):
...
TypeError: Attempted to reuse key: square

     However, two enum members are allowed to have the same value.  Given two members
A and B with the same value (and A defined first), B is an alias to A.  By-value
lookup of the value of A and B will return A.  By-name lookup of B will also
return A:

>>> class Shape(Enum):
...   square = 2
...   diamond = 1
...   circle = 3
...   alias_for_square = 2
...
>>> Shape.square
<Shape.square: 2>
>>> Shape.alias_for_square
<Shape.square: 2>
>>> Shape(2)
<Shape.square: 2>

     Iterating over the members of an enum does not provide the aliases:

>>> list(Shape)
[<Shape.square: 2>, <Shape.diamond: 1>, <Shape.circle: 3>]

     The special attribute
     <tt class="docutils literal">
      __members__
     </tt>
     is an ordered dictionary mapping names
to members.  It includes all names defined in the enumeration, including the
aliases:

>>> for name, member in Shape.__members__.items():
...   name, member
...
('square', <Shape.square: 2>)
('diamond', <Shape.diamond: 1>)
('circle', <Shape.circle: 3>)
('alias_for_square', <Shape.square: 2>)

     The
     <tt class="docutils literal">
      __members__
     </tt>
     attribute can be used for detailed programmatic access to
the enumeration members.  For example, finding all the aliases:

>>> [name for name, member in Shape.__members__.items() if member.name != name]
['alias_for_square']

      Comparisons

     Enumeration members are compared by identity:

>>> Color.red is Color.red
True
>>> Color.red is Color.blue
False
>>> Color.red is not Color.blue
True

     Ordered comparisons between enumeration values are

      not

     supported.  Enums are
not integers (but see

      IntEnum

     below):

>>> Color.red < Color.blue
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
TypeError: unorderable types: Color() < Color()

     Equality comparisons are defined though:

>>> Color.blue == Color.red
False
>>> Color.blue != Color.red
True
>>> Color.blue == Color.blue
True

     Comparisons against non-enumeration values will always compare not equal
(again,
     <tt class="docutils literal">
      IntEnum
     </tt>
     was explicitly designed to behave differently, see
below):

>>> Color.blue == 2
False

      Allowed members and attributes of enumerations

     The examples above use integers for enumeration values.  Using integers is
short and handy (and provided by default by the

      Functional API

     ), but not
strictly enforced.  In the vast majority of use-cases, one doesn't care what
the actual value of an enumeration is.  But if the value

      is

     important,
enumerations can have arbitrary values.

     Enumerations are Python classes, and can have methods and special methods as
usual.  If we have this enumeration:

class Mood(Enum):
  funky = 1
  happy = 3

  def describe(self):
    # self is the member here
    return self.name, self.value

  def __str__(self):
    return 'my custom str! {0}'.format(self.value)

  @classmethod
  def favorite_mood(cls):
    # cls here is the enumeration
    return cls.happy

     Then:

>>> Mood.favorite_mood()
<Mood.happy: 3>
>>> Mood.happy.describe()
('happy', 3)
>>> str(Mood.funky)
'my custom str! 1'

     The rules for what is allowed are as follows: all attributes defined within an
enumeration will become members of this enumeration, with the exception of

      __dunder__

     names and descriptors

      [9]

     ; methods are descriptors too.

      Restricted subclassing of enumerations

     Subclassing an enumeration is allowed only if the enumeration does not define
any members.  So this is forbidden:

>>> class MoreColor(Color):
...   pink = 17
...
TypeError: Cannot extend enumerations

     But this is allowed:

>>> class Foo(Enum):
...   def some_behavior(self):
...     pass
...
>>> class Bar(Foo):
...   happy = 1
...   sad = 2
...

     The rationale for this decision was given by Guido in

      [6]

     .  Allowing to
subclass enums that define members would lead to a violation of some
important invariants of types and instances.  On the other hand, it
makes sense to allow sharing some common behavior between a group of
enumerations, and subclassing empty enumerations is also used to implement
     <tt class="docutils literal">
      IntEnum
     </tt>
     .

      IntEnum

     A variation of
     <tt class="docutils literal">
      Enum
     </tt>
     is proposed which is also a subclass of
     <tt class="docutils literal">
      int
     </tt>
     .
Members of an
     <tt class="docutils literal">
      IntEnum
     </tt>
     can be compared to integers; by extension,
integer enumerations of different types can also be compared to each other:

>>> from enum import IntEnum
>>> class Shape(IntEnum):
...   circle = 1
...   square = 2
...
>>> class Request(IntEnum):
...   post = 1
...   get = 2
...
>>> Shape == 1
False
>>> Shape.circle == 1
True
>>> Shape.circle == Request.post
True

     However they still can't be compared to
     <tt class="docutils literal">
      Enum
     </tt>
     :

>>> class Shape(IntEnum):
...   circle = 1
...   square = 2
...
>>> class Color(Enum):
...   red = 1
...   green = 2
...
>>> Shape.circle == Color.red
False

     <tt class="docutils literal">
      IntEnum
     </tt>
     values behave like integers in other ways you'd expect:

>>> int(Shape.circle)
1
>>> ['a', 'b', 'c'][Shape.circle]
'b'
>>> [i for i in range(Shape.square)]
[0, 1]

     For the vast majority of code,
     <tt class="docutils literal">
      Enum
     </tt>
     is strongly recommended,
since
     <tt class="docutils literal">
      IntEnum
     </tt>
     breaks some semantic promises of an enumeration (by
being comparable to integers, and thus by transitivity to other
unrelated enumerations). It should be used only in special cases where
there's no other choice; for example, when integer constants are
replaced with enumerations and backwards compatibility is required
with code that still expects integers.

      Other derived enumerations

     <tt class="docutils literal">
      IntEnum
     </tt>
     will be part of the
     <tt class="docutils literal">
      enum
     </tt>
     module.  However, it would be very
simple to implement independently:

class IntEnum(int, Enum):
    pass

     This demonstrates how similar derived enumerations can be defined, for example
a
     <tt class="docutils literal">
      StrEnum
     </tt>
     that mixes in
     <tt class="docutils literal">
      str
     </tt>
     instead of
     <tt class="docutils literal">
      int
     </tt>
     .

     Some rules:

      When subclassing Enum, mix-in types must appear before Enum itself in the
sequence of bases, as in the
      <tt class="docutils literal">
       IntEnum
      </tt>
      example above.

      While Enum can have members of any type, once you mix in an additional
type, all the members must have values of that type, e.g.
      <tt class="docutils literal">
       int
      </tt>
      above.
This restriction does not apply to mix-ins which only add methods
and don't specify another data type such as
      <tt class="docutils literal">
       int
      </tt>
      or
      <tt class="docutils literal">
       str
      </tt>
      .

      Pickling

     Enumerations can be pickled and unpickled:

>>> from enum.tests.fruit import Fruit
>>> from pickle import dumps, loads
>>> Fruit.tomato is loads(dumps(Fruit.tomato))
True

     The usual restrictions for pickling apply: picklable enums must be defined in
the top level of a module, since unpickling requires them to be importable
from that module.

      Functional API

     The
     <tt class="docutils literal">
      Enum
     </tt>
     class is callable, providing the following functional API:

>>> Animal = Enum('Animal', 'ant bee cat dog')
>>> Animal
<Enum 'Animal'>
>>> Animal.ant
<Animal.ant: 1>
>>> Animal.ant.value
1
>>> list(Animal)
[<Animal.ant: 1>, <Animal.bee: 2>, <Animal.cat: 3>, <Animal.dog: 4>]

     The semantics of this API resemble
     <tt class="docutils literal">
      namedtuple
     </tt>
     . The first argument
of the call to
     <tt class="docutils literal">
      Enum
     </tt>
     is the name of the enumeration.  Pickling enums
created with the functional API will work on CPython and PyPy, but for
IronPython and Jython you may need to specify the module name explicitly
as follows:

>>> Animals = Enum('Animals', 'ant bee cat dog', module=__name__)

     The second argument is the

      source

     of enumeration member names.  It can be a
whitespace-separated string of names, a sequence of names, a sequence of
2-tuples with key/value pairs, or a mapping (e.g. dictionary) of names to
values.  The last two options enable assigning arbitrary values to
enumerations; the others auto-assign increasing integers starting with 1.  A
new class derived from
     <tt class="docutils literal">
      Enum
     </tt>
     is returned.  In other words, the above
assignment to
     <tt class="docutils literal">
      Animal
     </tt>
     is equivalent to:

>>> class Animals(Enum):
...   ant = 1
...   bee = 2
...   cat = 3
...   dog = 4

     The reason for defaulting to
     <tt class="docutils literal">
      1
     </tt>
     as the starting number and not
     <tt class="docutils literal">
      0
     </tt>
     is
that
     <tt class="docutils literal">
      0
     </tt>
     is
     <tt class="docutils literal">
      False
     </tt>
     in a boolean sense, but enum members all evaluate
to
     <tt class="docutils literal">
      True
     </tt>
     .

     Proposed variations

    Some variations were proposed during the discussions in the mailing list.
Here's some of the more popular ones.

      flufl.enum

     <tt class="docutils literal">
      flufl.enum
     </tt>
     was the reference implementation upon which this PEP was
originally based.  Eventually, it was decided against the inclusion of
     <tt class="docutils literal">
      flufl.enum
     </tt>
     because its design separated enumeration members from
enumerations, so the former are not instances of the latter.  Its design
also explicitly permits subclassing enumerations for extending them with
more members (due to the member/enum separation, the type invariants are not
violated in
     <tt class="docutils literal">
      flufl.enum
     </tt>
     with such a scheme).

      Not having to specify values for enums

     Michael Foord proposed (and Tim Delaney provided a proof-of-concept
implementation) to use metaclass magic that makes this possible:

class Color(Enum):
    red, green, blue

     The values get actually assigned only when first looked up.

     Pros: cleaner syntax that requires less typing for a very common task (just
listing enumeration names without caring about the values).

     Cons: involves much magic in the implementation, which makes even the
definition of such enums baffling when first seen.  Besides, explicit is
better than implicit.

      Using special names or forms to auto-assign enum values

     A different approach to avoid specifying enum values is to use a special name
or form to auto assign them.  For example:

class Color(Enum):
    red = None          # auto-assigned to 0
    green = None        # auto-assigned to 1
    blue = None         # auto-assigned to 2

     More flexibly:

class Color(Enum):
    red = 7
    green = None        # auto-assigned to 8
    blue = 19
    purple = None       # auto-assigned to 20

     Some variations on this theme:

      A special name
      <tt class="docutils literal">
       auto
      </tt>
      imported from the enum package.

      Georg Brandl proposed ellipsis (
      <tt class="docutils literal">
       ...
      </tt>
      ) instead of
      <tt class="docutils literal">
       None
      </tt>
      to achieve the
same effect.

     Pros: no need to manually enter values. Makes it easier to change the enum and
extend it, especially for large enumerations.

     Cons: actually longer to type in many simple cases.  The argument of explicit
vs. implicit applies here as well.

     Use-cases in the standard library

    The Python standard library has many places where the usage of enums would be
beneficial to replace other idioms currently used to represent them.  Such
usages can be divided to two categories: user-code facing constants, and
internal constants.

    User-code facing constants like
    <tt class="docutils literal">
     os.SEEK_*
    </tt>
    ,
    <tt class="docutils literal">
     socket
    </tt>
    module constants,
decimal rounding modes and HTML error codes could require backwards
compatibility since user code may expect integers.
    <tt class="docutils literal">
     IntEnum
    </tt>
    as described
above provides the required semantics; being a subclass of
    <tt class="docutils literal">
     int
    </tt>
    , it does not
affect user code that expects integers, while on the other hand allowing
printable representations for enumeration values:

>>> import socket
>>> family = socket.AF_INET
>>> family == 2
True
>>> print(family)
SocketFamily.AF_INET

    Internal constants are not seen by user code but are employed internally by
stdlib modules.  These can be implemented with
    <tt class="docutils literal">
     Enum
    </tt>
    .  Some examples
uncovered by a very partial skim through the stdlib:
    <tt class="docutils literal">
     binhex
    </tt>
    ,
    <tt class="docutils literal">
     imaplib
    </tt>
    ,
    <tt class="docutils literal">
     http/client
    </tt>
    ,
    <tt class="docutils literal">
     urllib/robotparser
    </tt>
    ,
    <tt class="docutils literal">
     idlelib
    </tt>
    ,
    <tt class="docutils literal">
     concurrent.futures
    </tt>
    ,
    <tt class="docutils literal">
     turtledemo
    </tt>
    .

    In addition, looking at the code of the Twisted library, there are many use
cases for replacing internal state constants with enums.  The same can be said
about a lot of networking code (especially implementation of protocols) and
can be seen in test protocols written with the Tulip library as well.

     Acknowledgments

    This PEP was initially proposing including the
    <tt class="docutils literal">
     flufl.enum
    </tt>
    package

     [8]

    by Barry Warsaw into the stdlib, and is inspired in large parts by it.
Ben Finney is the author of the earlier enumeration

     PEP 354

    .

     References

    <colgroup>
     <col class="label">
     </col>
     <col>
     </col>
    </colgroup>

        [1]

        http://mail.python.org/pipermail/python-dev/2013-May/126112.html

    <colgroup>
     <col class="label">
     </col>
     <col>
     </col>
    </colgroup>

        [2]

        http://www.python.org/dev/peps/pep-0354/

    <colgroup>
     <col class="label">
     </col>
     <col>
     </col>
    </colgroup>

        [3]

        http://mail.python.org/pipermail/python-ideas/2013-January/019003.html

    <colgroup>
     <col class="label">
     </col>
     <col>
     </col>
    </colgroup>

        [4]

        http://mail.python.org/pipermail/python-ideas/2013-February/019373.html

    <colgroup>
     <col class="label">
     </col>
     <col>
     </col>
    </colgroup>

        [5]

       To make enums behave similarly to Python classes like bool, and
behave in a more intuitive way.  It would be surprising if the type of
       <tt class="docutils literal">
        Color.red
       </tt>
       would not be
       <tt class="docutils literal">
        Color
       </tt>
       . (Discussion in

        http://mail.python.org/pipermail/python-dev/2013-April/125687.html

       )

    <colgroup>
     <col class="label">
     </col>
     <col>
     </col>
    </colgroup>

       [6]

        (

         1

        ,

         2

        ,

         3

        )

       Subclassing enums and adding new members creates an unresolvable
situation; on one hand
       <tt class="docutils literal">
        MoreColor.red
       </tt>
       and
       <tt class="docutils literal">
        Color.red
       </tt>
       should
not be the same object, and on the other
       <tt class="docutils literal">
        isinstance
       </tt>
       checks become
confusing if they are not.  The discussion also links to Stack Overflow
discussions that make additional arguments.
(

        http://mail.python.org/pipermail/python-dev/2013-April/125716.html

       )

    <colgroup>
     <col class="label">
     </col>
     <col>
     </col>
    </colgroup>

        [7]

       It may be useful to have a class defining some behavior (methods, with
no actual enumeration members) mixed into an enum, and this would not
create the problem discussed in

        [6]

       .  (Discussion in

        http://mail.python.org/pipermail/python-dev/2013-May/125859.html

       )

    <colgroup>
     <col class="label">
     </col>
     <col>
     </col>
    </colgroup>

        [8]

        http://pythonhosted.org/flufl.enum/

    <colgroup>
     <col class="label">
     </col>
     <col>
     </col>
    </colgroup>

        [9]

        http://docs.python.org/3/howto/descriptor.html

     Copyright

    This document has been placed in the public domain.

Source: https://hg.python.org/peps/file/tip/pep-0435.txt

        Tweets by @ThePSF

The PSF

The Python Software Foundation is the organization behind Python. Become a member of the PSF and help advance the software and our mission.

                    ▲ Back to Top

        About

Applications

Quotes

Getting Started

Help

        Downloads

All releases

Source code

Windows

Mac OS X

Other Platforms

License

Alternative Implementations

        Documentation

Docs

Audio/Visual Talks

Beginner's Guide

Developer's Guide

FAQ

Non-English Docs

PEP Index

Python Books

        Community

Diversity

IRC

Mailing Lists

Python Conferences

Special Interest Groups

Python Wiki

Python Logo

Merchandise

Community Awards

        Success Stories

Arts

Business

Education

Engineering

Government

Scientific

Software Development

        News

Python News

Community News

PSF News

PyCon News

        Events

Python Events

User Group Events

Python Events Archive

User Group Events Archive

Submit an Event

        Contributing

Developer's Guide

Issue Tracker

python-dev list

Core Mentorship

                    ▲ Back to Top

Help & General Contact

Diversity Initiatives

Submit Website Bug

                            Copyright ©2001-2015.
                             Python Software Foundation
                             Legal Statements
                             Privacy Policy


This book is about so much. It's so much to wrap your head around and before you know it, it's just finished. It took me some hours to really wrap my head around the fact that I was done with this 7 book long series, which was equally as draining as Harry Potter the first time around. And now that I'm done, I have so many issues with it, as well as praise. Like I don't even know where to start.
This book is huge, and I wasn't really sure how Maas was going to wrap this whole thing after Tower of Dawn and how that one ended. But as you got through chapters upon chapters it all started angling towards that epic ending that everyone had been waiting for, including me. I was ready to be mindblown, which I was, but at the same time wasn't.
The ending was kind of bittersweet, but not bittersweet enough. I wanted it to end with some epic death that was so sad, but at the same time made sense, and it didn't and that disappointed me. It also disappointed me that it all kind of "worked out" in the end. I was expecting this to be that epic finale where I was crying my eyes out and asking "WHY MAAS; WHYYYY", but instead I felt kind of "WAS THAT ALL?".
Of course, I was happy that it had a happy ending. One that I can live with. One that kind of made sense after everything our main characters has been through. But it's still that feeling of; was that really all? And that is why I gave it four stars rather than five.
This will, all though, continue to be one of my favorite series of all time. It's such a good series, and with that small point towards ACOTAR, that made me shooketh when I realized it.


text:
using namespace std;

class LocationPinger{
public:
	float x;
	float y;

	float prevX;
	float prevY;

	float distKm;
	float distMiles;

	int map;
	int lastMap;

	LocationPinger();

	void pingLocation(string line);

	void calculateDistance();

};


text:
from distutils.core import setup
from distutils.command.install_data import install_data
from distutils.command.install import INSTALL_SCHEMES
import os
import sys

version = "0.2.150"

class osx_install_data(install_data):
    # On MacOS, the platform-specific lib dir is /System/Library/Framework/Python/.../
    # which is wrong. Python 2.5 supplied with MacOS 10.5 has an Apple-specific fix
    # for this in distutils.command.install_data#306. It fixes install_lib but not
    # install_data, which is why we roll our own install_data class.

    def finalize_options(self):
        # By the time finalize_options is called, install.install_lib is set to the
        # fixed directory, so we set the installdir to install_lib. The
        # install_data class uses ('install_data', 'install_dir') instead.
        self.set_undefined_options('install', ('install_lib', 'install_dir'))
        install_data.finalize_options(self)

if sys.platform == "darwin":
    cmdclasses = {'install_data': osx_install_data}
else:
    cmdclasses = {'install_data': install_data}

def fullsplit(path, result=None):
    """
    Split a pathname into components (the opposite of os.path.join) in a
    platform-neutral way.
    """
    if result is None:
        result = []
    head, tail = os.path.split(path)
    if head == '':
        return [tail] + result
    if head == path:
        return result
    return fullsplit(head, [tail] + result)

# Tell distutils not to put the data_files in platform-specific installation
# locations. See here for an explanation:
# http://groups.google.com/group/comp.lang.python/browse_thread/thread/35ec7b2fed36eaec/2105ee4d9e8042cb
for scheme in INSTALL_SCHEMES.values():
    scheme['data'] = scheme['purelib']

# Compile the list of packages available, because distutils doesn't have
# an easy way to do this.
packages, data_files = [], []
root_dir = os.path.dirname(__file__)
if root_dir != '':
    os.chdir(root_dir)
ueditor_dir = 'editor_md'

for dirpath, dirnames, filenames in os.walk(ueditor_dir):
    # Ignore dirnames that start with '.'
    for i, dirname in enumerate(dirnames):
        if dirname.startswith('.'): del dirnames[i]
    if '__init__.py' in filenames:
        packages.append('.'.join(fullsplit(dirpath)))
    elif filenames:
        data_files.append([dirpath, [os.path.join(dirpath, f) for f in filenames]])

# Small hack for working with bdist_wininst.
# See http://mail.python.org/pipermail/distutils-sig/2004-August/004134.html
if len(sys.argv) > 1 and sys.argv[1] == 'bdist_wininst':
    for file_info in data_files:
        file_info[0] = '\\PURELIB\\%s' % file_info[0]

# Dynamically calculate the version based on django.VERSION.

setup(
    name="django_editor_md",
    version=version,
    url='https://github.com/fcfangcc/django-editor-md',
    author='chao.fang',
    author_email='swjfc22@163.co ',
    description='A Django application for editor.md.',
    download_url='https://github.com/fcfangcc/django-editor-md',
    packages=packages,
    cmdclass=cmdclasses,
    data_files=data_files,
    license="BSD-3-Clause",
    install_requires=["Django>=1.9.6"],
    classifiers=[
        'Development Status :: 5 - Production/Stable',
        'Environment :: Web Environment',
        'Framework :: Django',
        'Intended Audience :: Developers',
        'License :: OSI Approved :: BSD License',
        'Operating System :: OS Independent',
        'Programming Language :: Python',
        'Programming Language :: Python :: 2.7',
        'Programming Language :: Python :: 3.4',
        'Programming Language :: Python :: 3.5',
        'Programming Language :: Python :: 3.6',
        'Topic :: Internet :: WWW/HTTP',
        'Topic :: Internet :: WWW/HTTP :: Dynamic Content',
        'Topic :: Internet :: WWW/HTTP :: WSGI',
        'Topic :: Software Development :: Libraries :: Application Frameworks',
        'Topic :: Software Development :: Libraries :: Python Modules',
    ],
)


text:
Isaac Sweers, gelegentlich auch Isaac Sweerts geschrieben, (* 1. Januar 1622 in Nijmegen; † 21. August 1673 in der Seeschlacht vor Texel) war ein niederländischer Admiral.

Anfangsjahre
Sweers, von dem in seiner Familie autobiographische Aufzeichnungen überliefert wurden, stammte aus keiner Seemannsfamilie. Sein Vater Aernout Sweers war einer der Regenten im Rat (Vroedschap) von Nijmegen. Unter Maurits von Oranien verlor er diesen Posten vorübergehend 1618 wegen eines Gesetzes gegen Remonstranten. Nach dem Tod von Moritz von Oranien war er wieder in seinem Amt und war 1628 bis 1635 Vertreter von Gelderland in der Kammer der Ostindienkompanie in Amsterdam. Danach zog er mit seiner Familie wieder nach Nijmegen. Sweerts verlor 1635 seine Eltern durch die Pest und kam auf eine Französisch-Schule in Hoorn. Auf eigenen Wunsch ging er 1638 zu einem Geschäftspartner seines Onkels nach Sevilla, wo er aber nicht zurechtkam, entlassen wurde und über Plymouth in seine Heimat zurückkehrte. Seine Familie brachte ihn als Gehilfen bei seinem Onkel Salomon Sweers unter, der Schultheiß von Texel war.

1640 ging er als Angestellter der Westindischen Kompanie nach Brasilien (Mauritsstad, heute Recife). Er wurde Notar und Anwalt und sein Geschäft florierte bald dank seiner guten Spanisch-Kenntnisse. Beim Aufstand der Portugiesen gegen die Holländer 1645 kommandierte er eine Einheit im Fort van der Dussen, das durch Verrat des niederländischen Kommandeurs Dirck Hoogstraaten an die Aufständischen fiel. Sweerts wurde gefangen genommen und gefoltert. 1646 wurde er freigelassen und kehrte mittellos in die Heimat zurück. 1647 versuchte er sich mit anderen als Kaufmann auf eigene Rechnung mit einer Handelsreise zu den Jungferninseln, sie erlitten aber Schiffbruch. Nach der Rückkehr war er verschuldet und gab seine Pläne als Kaufmann auf.

Im Dienst der Admiralität
Stattdessen ging er 1649 als Seekadett in die Dienste der Admiralität von Amsterdam. Zunächst nahm er unter dem Kommandeur Jan van Galen an einer Expedition 1650/51 gegen die Barbaresken (Seeräuber im Mittelmeer) teil und wurde bei einem Kampf gegen spanische Räuber schwer verwundet. 1651 wurde er Leutnant und 1652 im Ersten Englisch-Niederländischen Krieg Kapitän auf der Engel Gabriel. In der Seeschlacht bei Portland sank sein Schiff. Er war in Kriegsgefangenschaft, konnte aber bei einem Besuch einer spanischen Delegation im Gefängnis entfliehen, indem er sich ebenfalls als Spanier ausgab. Danach fuhr er Begleitschutz im Mittelmeer. 1655 wurde er Bürger von Amsterdam. 1656 war er in Kämpfen gegen die Schweden bei der Befreiung von Danzig beteiligt und danach an der Überwachung des Friedens mit Schweden, war aber nicht an der Seeschlacht im Öresund (1658) beteiligt. Er wurde zum ordentlichen Kapitän ernannt und nahm 1664 als Kommandant der Middelburg an der Expedition von Michiel de Ruyter nach Westafrika und Amerika teil.

Im Zweiten Englisch-Niederländischen Krieg wurde er Konteradmiral (Schout-bij-nacht). In der Viertageschlacht gelang die Eroberung der auf eine Sandbank gelaufenen Royal Prince, auf der Sweers zum Ärger von Tromp das auch von diesem begehrte Tafelsilber des englischen Admirals George Ayscue für sich in Besitz nahm. Anschließend war er unter dem Kommando von Tromp am St. James's Day Fight beteiligt. Bei der Rückkehr wurde er wie Tromp öffentlich von de Ruyter in Vlissingen getadelt. Im August 1666 wurde er offiziell Vizeadmiral von Holland und Westfriesland, hatte die Position inoffiziell allerdings schon seit der Viertageschlacht. Bei Calais eroberte er 1666 mit Cornelis Evertsen dem Jüngeren die Royal Charles (nicht identisch mit dem Flaggschiff von Karl II., das beim Überfall im Medway verschleppt wurde). Später stritten sich beide über das Prisengeld von 5000 Gulden, das dann Evertsen bekam. Er nahm am Überfall im Medway teil. 1667 bekam er das neue 82 Kanonen Schiff De Witte Oliphant (Weißer Elefant) als Flaggschiff. Nach dem Krieg nahm er mit den Engländern an einer Expedition gegen die Barbaresken teil (wobei es zu einem Zwischenfall kam, da er nicht wie verlangt vor dem englischen Vizeadmiral Thomas Allin die Flagge zur Begrüßung streichen wollte).

Im Dritten Englisch-Niederländischen Krieg kämpfte er in der Seeschlacht in der Solebay unter Leutnant-Admiral Willem Joseph van Ghent und übernahm das Kommando, als dieser in der Schlacht fiel. Als die Franzosen 1672 in den Niederlanden einfielen, was nur durch die Öffnung der Deiche verhindert werden konnte, kommandierte er im Winter 1672/73 Marineeinheiten, die verhindern sollten, dass die Franzosen die Wassergrenze überschritten, die nach der Flutung des Landes zwischen der überlegenen französischen Armee und dem Rest des Landes stand. Im weiteren Verlauf des Jahres 1673 musste er im Kommando hinter Cornelis Tromp zurücktreten und nahm unter diesem an der Zweiten Seeschlacht von Schooneveld teil. Tromp warf ihm danach vor, nicht mit letztem Einsatz gekämpft zu haben, die Untersuchung ergab aber dass sein Schiff durch Kanonaden so schwer beschädigt worden war, dass er zu Reparaturen zurückkehren musste. Sweers war über die Vorwürfe von Tromp so aufgebracht, dass er ihn zum Duell forderte. Der Statthalter Wilhelm III. befahl ihnen aber, dies bis nach dem Krieg zurückzustellen. 1673 wurde er in der Seeschlacht vor Texel auf seinem Flaggschiff Olifant von einer Kanonenkugel getroffen und verlor beide Beine, bekam im Sterben liegend aber noch mit, dass die Niederländer gewonnen hatten. Das Kommando übernahm in der Schlacht Jan den Haen. Sweers liegt in der Oude Keerk in Amsterdam begraben.

Er war mit Constantia Blommaert (1626–1694) verheiratet, deren Vater Samuel Vorsteher (Bewindhebber) der Amsterdamer Kammer der Ostindienkompagnie war. Mit ihr hatte er vier Töchter und einen Sohn Isaac Sweers der Jüngere, der auch Kapitän wurde. Seine Frau war eine der Regentinnen des 1681 gebauten Altenheims Amstelhof. Ein Gemälde des Ehepaars von Ludolf Backhuizen ist im Amsterdamer Schiffahrtsmuseum.

Ein niederländischer Zerstörer im Zweiten Weltkrieg war nach ihm benannt.

Weblinks
 Nieuw Nederlandsch Biografisch Woordenboek NNBW

Marineoffizier (Niederlande)
Niederländer
Geboren 1622
Gestorben 1673
Mann


text:
Journal of Bacteriology and Infectious Diseases
Short Communication - Journal of Bacteriology and Infectious Diseases (2020) Volume 4, Issue 2
Bacteriology and Infectious Diseases 2018- Characterization of antiproliferative red-like pigments produced by actinomycete soil strains identified as streptomyces coelicoflavus
Keywords: Actinomycetes, Metabolites , Osteosarcoma
Actinomycetes are filamentous bacteria, widely distributed in soil, water and plants rhisosphere. They are able to produce secondary metabolites with diverse chemical structures and biological activities. Among these bioactive metabolites, anthracycline antibiotics such as prodigiosin are known to exhibit antitumor, antioxidant, and immunosuppressive activities. In this study, five strains of actinomycetes isolated from soil were revealed to produce red-like pigments. Phenotypic and RNA gene coding sequence analysis allowed identification of the all strains as Streptomyces coelicoflavus, which reported here for the first time to produce an antiproliferative red-like pigment. The pigments are intracellular, hydrophobic and photosensitive. Their extraction could be performed with organic solvent from which, ethanol showed the most effective extracting ability. Like prodigiosin and undecylprodigiosin, UV-Vis absorbance of the pigments present sharp peak at nearby 534 nm at neutral or acid conditions, where the pigment color is red. In basic condition the pigment color turn yellow with a λmax of 458 nm. However, TLC analysis, antibacterial assay and production media suggest highly that these red-like pigments are undecylprodigiosin analogues or probably other similar anthracyclines. Cytotoxicity of crude extract and two fractions (FA, soluble in petroleum ether and FB, soluble in chloroform) of two strains were performed by MTT assay on mice P3 myeloid cancer cells and human osteosarcoma cancer cells (U-2 OS (ATCC HTB-96). Results on mice P3 cell line showed that the crude extract of one from two tested strains have the highest antiproliferative activity at low dose. At 100 µg/ml, both fractions A and B of the two strains showed high antiproliferative effect on mice P3 cell line. In human U2OS osteosarcoma cell line, 3 fractions showed more antiproliferative effect than on mice P3 cell line. FACs analysis suggests a cell phase cycle arrest at G1 and S according to the fractions. Five new strains MFB11, MFB20, MFB21, MFB23 and MFB24 of actinomycetes showed an intracellular hydrophobic pink red-like pigment production. These pigments present similar physico-chemical characteristics with anthracycline antibiotics of prodigiosin family. Nevertheless, negative antibacterial assay, Thin-layer chromatography (TLC) and interaction with organic solvents analysis of these pigments revealed their difference from known anthracycline antibiotics. Morphological, biochemical and gene coding 16S RNA sequence analysis allowed identification of the producer strains as Streptomyces coelicoflavus; known to produce important aminoglycoside antibiotics and other bioactive compounds but not anthracyclines red-like pigments. The identification of the five strains and physico-chemical properties of the produced pink red-like pigments are presented in this report. Five new strains MFB11, MFB20, MFB21, MFB23 and MFB24 of actinomycetes showed an intracellular hydrophobic pink red-like pigment production. These pigments present similar physico-chemical characteristics with anthracycline antibiotics of prodigiosin family. Nevertheless, negative antibacterial assay, Thin-layer chromatography (TLC) and interaction with organic solvents analysis of these pigments revealed their difference from known anthracycline antibiotics. Morphological, biochemical and gene coding 16S RNA sequence analysis allowed identification of the producer strains as Streptomyces coelicoflavus; known to produce important aminoglycoside antibiotics and other bioactive compounds but not anthracyclines red-like pigments. The identification of the five strains and physico-chemical properties of the produced pink red-like pigments are presented in this report. Among 29 soil isolated actinomycetes, five new strains MFB11, MFB20, MFB21, MFB23 and MFB24 showed an intracellular hydrophobic pink red-like pigment production. These pigments present similar physio-chemical characteristics with anthracycline antibiotics of prodigiosin family. Crud extract and prepared fractions were tested by MTT on mice cancer cell line as well on human cancer cell line. The results indicated an important antiproliferative effect of the different strain pigments on the two organism cell types. Human cells were more sensitive to the pigments and presented different antiproliferative effect profiles. FACs analysis of this antiproliferative effect on cancer human cells line showed a cell cycle phase arrests at G1 and S. Nevertheless, negative antibacterial assay, Thin-layer chromatography (TLC) and interaction with organic solvents analysis of these pigments revealed their difference from known anthracycline antibiotics. Morphological, biochemical and gene coding 16S RNA sequence analysis allowed identification of the producer strains as Streptomyces coelicoflavus; known to produce important aminoglycoside antibiotics and other bioactive compounds but not anthracycline red-like pigments. Otherwise, two other strains produced water soluble Gram positive antibiotics and chloroform soluble bioactive compounds with strong and dramatic apoptotic antiproliferative activity as indicated by MTT and their cell cycle phase arrests at G0/G1 and G2. Actinomycetes are Gram-positive, facultative anaerobic fungus-like filamentous bacteria which remain on the top of the natural antibiotic producers. Due to the climatic and geographical diversity of Nepal, a wide range of microorganisms with potent source of antimicrobials are available. The objective of this study was to isolate, identify, and screen the potential antimicrobial-producing actinomycetes from soils covering different altitude range of Nepal. Forty-one isolates of actinomycetes were isolated from 11 soil samples collected from different locations in Nepal with altitude ranging from 1500 to 4380 meters. The isolates were identified on the basis of morphological study, different sugar utilization, protein utilization, and hydrolysis tests. They were also characterized on the basis of temperature and pH. Primary screening for antimicrobial activity was carried out against several test organisms: Staphylococcus aureus (ATCC 25923), Escherichia coli (ATCC 25922), Klebsiella pneumoniae (ATCC 700603), and Pseudomonas aeruginosa (ATCC 27853) by the perpendicular streaking method, and secondary screening was carried out by the agar well diffusion method using ethyl acetate for solvent extraction. 70.7% of the isolates were identified as Streptomyces spp., 19.5% as Nocardia spp., and 9.5% as Micromonospora spp. 43.34% of actinomycete isolates was found to be potent antimicrobial producers from the primary screening among which 46.34% were effective against Gram-positive and 12.19% against Gram-negative test organisms. Isolate C7 (Micromonospora spp.) showed the best broad-spectrum antimicrobial activity during secondary screening. A total of 11 different types of pigments were observed to be produced by different isolates, of which, the yellow pigment was the most prominent. The association between elevation, pH, and pigment with the antimicrobial production was found to be insignificant. This finding can be of importance for further investigation towards obtaining broad-spectrum antibiotics for therapeutic purpose. A highly active actinobacterial strain isolated from untapped areas of Northwestern Himalayas and characterised as Streptomyces puniceus strain AS13 by 16S rRNA gene sequencing was selected for production of bioactive metabolites. The bioassay-guided fractionation of microbial cultured ethyl acetate extract of the strain, led to isolation of macrotetrolide compound 1 (Dinactin) and compound 2 (1-(2,4-dihydroxy-6-methylphenyl)-ethanone). Structures of the isolated compounds were elucidated interpretation of NMR and other spectroscopic data including HR-ESI–MS, FT-IR. These compounds are reported for first time from Streptomyces Puniceus. Compound 1 exhibited strong anti-microbial activity against all tested bacterial pathogens including Mycobacterium tuberculosis. The MIC values of compound 1 against Gram negative and Gram positive bacterial pathogens ranged between 0.019 − 0.156 μg ml−1 and 1 μg ml−1 against Mycobacterium tuberculosis H37Rv. Dinactin exhibited marked anti-tumor potential with IC50 of 1.1- 9.7 μM in various human cancerous cell lines and showed least cytotoxicity (IC50 ∼ 80 μM) in normal cells (HEK-293). Dinactin inhabited cellular proliferation in cancer cells, reduced their clonogenic survival as validated by clonogenic assay and also inhabited cell migration and invasion characteristics in colon cancer (HCT-116) cells. Our results expressed the antimicrobial potential of dinactin and also spotted its prospective as an antitumor antibiotic.
Author(s): Mouslim Assia
Journal of Bacteriology and Infectious Diseases received 17 citations as per Google Scholar report
Journal of Bacteriology and Infectious Diseases peer review process verified by publons
10th International Congress on Infectious Diseases
10th International Conference on Infectious Diseases, Bacteriology and Antibiotics
19th Global Summit on Hematology and Infectious Diseases
35th International Conference on Pediatric Infectious Diseases and Therapy
18th World Conference on Infectious Diseases, Prevention and Control
Tweets by ennajones1